Redo CLI

[jhechtf]

Description

Currently this is a very static tool, and I could definitely see the use case where someone definitely would only want to deal with SCSS / TS tokens and then just use their compiler to change that into CSS / JS. Currently though, there's no way to turn the JS/CSS off.

I would like to add in some kind of plugin-based system, similar to what is done in things like Vite or even in a sister project, Version Bump. This would allow for users to simply include / exclude things such as JS and CSS tokens, and would also allow for users to create their own exportable types (i.e. if we go with one version of SCSS variables, someone who prefers the other method can create it as a plugin themselves).

Exit Criteria

• [ ] Clear plan to something like TSyringe, which was done for version bump.
• [ ] Determine overall direction of the plan. Currently we are using Deno, but an argument for moving over to Node should be considered due to integration with build tools like Vite or Esbuild

[jhechtf]

Rough idea in FigJam

[jhechtf]

Deno v Node

My biggest issue with porting the codebase over to Node is the fact that I hate the Node ecosystem. I'm unsure about porting the code over to node, as I think other than the write file calls, and permission system, the code would largely run in a node package (once compiled) without issue.