@nrwl/nestSee schema

@nrwl/nest:application

Nx Application Options Schema.

Usage

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

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

You can specify the collection explicitly as follows:

nx g @nrwl/nest:application ...

Show what will be generated without writing to disk:

nx g application ... --dry-run

Options

name

Required
string

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.

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.

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

boolean
Default: false

Skip formatting files.

skipPackageJson

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