Jason

@rsms Just a thought, but you could automate creation of language-specific subsets using Github Actions. I wrote a Github Action to do this. You'd just need to add a script...

If it's just Github pages, I think we could make it work. Individual steps within a job run synchronously, so we can put a [Github Pages deploy step](https://github.com/marketplace/actions/github-pages-action) (see snippet...

Incredible! Saved ~170kb. Thanks for creating these @rsms!

We also will have `check` and `fix` commands to help bring a project up to current recommendations. That _might_ be better? TBD.

Good catch. The verification key generation with SnarkyJS is not ideal right now and needs to be reworked when time allows, but it won't be easy. But we should look...

I think we should hesitate to split them apart because it'd be detrimental to the dev experience--creates two steps and the possibility of forgetting it and deploying something old...unless we're...

Note to implementer: it may not be possible to fix this just based on how we use yargs. If that proves to be the case, creating a minimal reproduction and...

- [ ] Add `--fix`or as a separate command to automatically update the user's project to current recommendations for Prettier/Eslint/etc configs, ignore files, etc.

To discuss. We may not take this approach

Ideally, we update the "if" condition [here](https://github.com/o1-labs/snapp-cli/blob/main/.github/workflows/ci.yml#L32), to only run for the first NodeJS version listed in the matrix, if that's possible within Github Actions.