3 posts tagged with "configuration"

nova utility initialize made sense when Nova's guided setup had one obvious job: create the first nova.config.json file.

The command grew. It became the place to return whenever a project changed, whether you needed to add a workspace, revise repository settings, manage environment variables, or inspect GitHub environment status. Calling that ongoing work “initialization” stopped describing what the command actually did.

Nova 0.30.0 gives it a more accurate name: configure.

Environment values become easier to reason about when configuration describes where each value is allowed to travel.

Nova 0.22.0 introduced reach as a required delivery classification for project and workspace environment values.

Most ESLint flat configs start the same way. You spread a popular shared config into your array, add your overrides, and move on.

But as the project grows — more workspaces, more file types, more framework-specific needs — the config grows with it. You end up with a single array where language rules, environment globals, and framework conventions are tangled together, and figuring out which object added which rule means reading the whole thing top to bottom.

Nova's presets are designed to keep that clean. Each preset handles one concern, and you compose them into exactly the combination your workspace needs.