Project state goes a bit strange when navigating away without page reload

[pufferfish101007]

A few things in one issue here:

• navigating away from the project page while a project is running does not stop the project
• navigating away from one project and to another project, without reloading the page, sometimes causes the project runner to crash, often at js/looks/switchcostumeto.ts:5 (TypeError: Cannot read properties of undefined (reading 'data')); this is probably due to the setup function not running when the project is switched, as the module is not reimported.

Essentially, state just needs to be cleaned up when a navigation event occurs.

[waleedahmedwaheed]

I’ve noticed some inconsistent behavior when navigating away from a project without a full page reload, and it seems related to project state not being cleaned up properly.

First, when I navigate away from the project page while a project is still running, the project continues running in the background instead of stopping.

Second, when I navigate from one project directly to another without reloading the page, the project runner sometimes crashes. I’ve most often seen this error at
js/looks/switchcostumeto.ts:5 with:

TypeError: Cannot read properties of undefined (reading 'data')

From what I can tell, this likely happens because the project setup function is not being re-executed when switching projects, since the module isn’t reimported. As a result, the new project ends up running with stale or incomplete state from the previous one.

Overall, I think the core issue is that project state is not being properly cleaned up or reset on navigation events. Ensuring teardown logic runs when leaving a project—and reinitialization runs when entering a new one—should prevent both the background execution and the crash.