Nub 0.7.4 adds a guided config initializer and makes missing-package errors authoritative during installs.

Create a project config

nub config init creates a commented nub.jsonc at the project root with every supported project field visible and disabled:

nub config init

Only the schema URL is active, so initialization does not change runtime or install behavior. Existing files are never replaced.

The global form includes machine-wide settings such as temporary-package consent:

nub config init --global

Config commands now use project scope by default and --global for user scope. The prefix form is equivalent:

nub config set --global envFile false
nub global config set envFile false

The former --location option has been removed. Protected npm credentials still default to the user .npmrc; use --local only when a project credential is intentional.

Missing packages fail first

A missing registry package now returns ERR_NUB_PACKAGE_NOT_FOUND before similarity or package-age checks can produce a reputation warning:

nub add @types/nub

Public unscoped typos can include a non-interactive suggestion in that error. Scoped package names no longer suggest unrelated basenames from another namespace, and private-registry failures never use the public npm suggestion corpus.

The full release notes list every change in this release.