ness new

Creates a Ness application from an official, third-party, or local template.

ness new <project> [options]
ness n <project> [options]

Options

Option	Description	Default
--template <name-or-path>	Official alias, npm package, or local directory	typescript
--no-rsc	Scaffold classic SSR mode instead of the default RSC mode	RSC enabled
--package-override <name=spec>	Install a specific version, tag, or tarball of a framework package	none

Examples

ness new store
ness n prototype --template javascript
ness new service --template api
ness new admin --template dashboard
ness new tiny-app --template minimal
ness new internal-tool --template ../company-template
ness new ssr-app --no-rsc

Project names may contain lowercase letters, numbers, dots, dashes, and underscores. The destination must be empty, apart from .git and .DS_Store.

Official aliases are typescript (ts), javascript (js, and default), minimal, api, and dashboard. See Official templates for their intended use.

default is kept as a third name for the JavaScript starter. It was the alias --template fell back to before TypeScript became the default, so scripts that spell it out keep scaffolding what they always did.

--package-override is repeatable and takes name=spec, where the spec is anything npm accepts — a version, a distribution tag, or a local tarball:

ness new canary-app --package-override @nessframework/core=next --package-override @nessframework/cli=next

It rewrites the install spec of a package the starter already installs; a name the starter never asked for is ignored rather than added, so a build-only package cannot end up in runtime dependencies.

See Custom and local templates for filesystem paths, template.json, and package-style templates.