@nx/nest:application
Nx Application Options Schema.
Nx Application Options Schema.
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
The directory of the new application.
Frontend project that needs to access this application. This sets up proxy configuration.
^[a-zA-Z][^:]*$
The name of the application.
jest
jest
, none
Test runner to use for end to end (e2e) tests
eslint
eslint
, none
The tool to use for running lint checks.
false
Whether or not to configure the ESLint parserOptions.project
option. We do not do this by default for lint performance reasons.
false
Adds strictNullChecks, noImplicitAny, strictBindCallApply, forceConsistentCasingInFileNames and noFallthroughCasesInSwitch to tsconfig.
Add tags to the application (used for linting).
jest
jest
, none
Test runner to use for unit tests.
false
Skip formatting files.
false
Do not add dependencies to package.json
.
true
Split the project configuration into <projectRoot>/project.json
rather than including it inside workspace.json
.
Nx only supports standaloneConfig
Watch the replays of exciting talks on developer tooling and monorepos! Catch all the insightful presentations from the event on our YouTube channel.