Recipes and Run Scripts
Routine project maintenance should read like a policy, not a growing chain of copied shell commands.
Nova 0.14.0 introduced granular recipes, run-recipes, and run-scripts to make that structure explicit.
Routine project maintenance should read like a policy, not a growing chain of copied shell commands.
Nova 0.14.0 introduced granular recipes, run-recipes, and run-scripts to make that structure explicit.
Release notes work best when they are written while a change is still fresh, not reconstructed from a crowded commit history at release time.
Nova 0.13.0 introduced nova utility changelog to make that habit part of the release process.
Historical Article
This article is preserved as a snapshot of Nova when it was published. Nova 0.30.0 replaced nova utility initialize with nova utility configure; read why the command changed or see the current Configure documentation before following its setup instructions.
You know the routine. New repo, new hour of setup.
Copy your ESLint config from the last project, update the deprecated rules, wire up TypeScript, realize the TSConfig options changed again, scaffold the folder structure from memory, forget half the fields in package.json, and finally — an hour later — write your first line of actual code.
Now multiply that by every workspace in a monorepo.
Nova exists because that hour should be zero.