@nx/nest:application

Nx Application Options Schema.

Usage

1nx generate application ... 2
1nx g app ... #same 2

By default, Nx will search for application in the default collection provisioned in workspace.json.

You can specify the collection explicitly as follows:

1nx g @nx/nest:application ... 2

Show what will be generated without writing to disk:

1nx g application ... --dry-run 2

Options

name

Required
string
Pattern: ^[a-zA-Z][^:]*$

The name of the application.

frontendProject

string

Frontend project that needs to access this application. This sets up proxy configuration.

directory

string

The directory of the new application.

e2eTestRunner

string
Default: jest
Accepted values: jest, none

Test runner to use for end to end (e2e) tests

linter

string
Default: eslint
Accepted values: eslint, none

The tool to use for running lint checks.

projectNameAndRootFormat

string
Accepted values: as-provided, derived

Whether to generate the project name and root directory as provided (as-provided) or generate them composing their values and taking the configured layout into account (derived).

setParserOptionsProject

boolean
Default: false

Whether or not to configure the ESLint parserOptions.project option. We do not do this by default for lint performance reasons.

strict

boolean
Default: false

Adds strictNullChecks, noImplicitAny, strictBindCallApply, forceConsistentCasingInFileNames and noFallthroughCasesInSwitch to tsconfig.

tags

string

Add tags to the application (used for linting).

unitTestRunner

string
Default: jest
Accepted values: jest, none

Test runner to use for unit tests.

skipFormat

Internal
boolean
Default: false

Skip formatting files.

skipPackageJson

Internal
boolean
Default: false

Do not add dependencies to package.json.

standaloneConfig

Deprecated
boolean
Default: true

Split the project configuration into <projectRoot>/project.json rather than including it inside workspace.json.

Nx only supports standaloneConfig