Open samreid opened 2 months ago
Much of this issue should probably wait until we finish discussing https://github.com/phetsims/perennial/issues/370.
Good work for this issue is being done over in https://github.com/phetsims/perennial/issues/370.
Take this issue off hold once that issue is closed.
Ready to focus on the TODOs for this issue.
Most of these are now just the "ASK DEVS" TODOs.
I made a form to ask devs about the items we have marked with TODOs. I'll send it out now.
https://docs.google.com/forms/d/1IXJCC33lyDIfDly0rFVsPAIWADkpKztM0NWH4umgfXg/edit
Discovered in https://github.com/phetsims/chipper/issues/1459, there are many tasks in chipper's Gruntfile.js or perennial's Gruntfile.js that:
@zepumph and I recommend reviewing each grunt task to see if it can be deleted or moved to a separately executable script. Things that should remain are: simulation lifecycle events like
grunt --brands=phet
grunt dev
grunt rc
grunt lint
and their dependencies. And for tasks that must remain stable, well-supported, and backward-compatible for maintenance tasks.This work will help us modularize & limit our usage of grunt, which we would like to "abandon" https://github.com/phetsims/chipper/issues/1436
It will also free us up to use other runtimes (such as deno or tsx) or TypeScript as desired.
I will tag suspicious grunt tasks, then bring to Monday's developer meeting. I will make annotations in perennial/main and chipper's typescript_chipper_1459_b branch. (and they can (mostly?) be seen below)