@nx/nest:application
Nx Application Options Schema.
Usage
1nx generate application ...
21nx g app ... #same
2By 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 ...
2Show what will be generated without writing to disk:
1nx g application ... --dry-run
2Options
directory
Required
string
The directory of the new application.
frontendProject
string
Frontend project that needs to access this application. This sets up proxy configuration.
linter
string
Default:
noneAccepted values:
eslint, noneThe tool to use for running lint checks.
name
string
Pattern:
^[a-zA-Z][^:]*$The name of the application.
e2eTestRunner
string
Default:
jestAccepted values:
jest, noneTest runner to use for end to end (e2e) tests
setParserOptionsProject
boolean
Default:
falseWhether or not to configure the ESLint parserOptions.project option. We do not do this by default for lint performance reasons.
strict
boolean
Default:
falseAdds strictNullChecks, noImplicitAny, strictBindCallApply, forceConsistentCasingInFileNames and noFallthroughCasesInSwitch to tsconfig.
tags
string
Add tags to the application (used for linting).
unitTestRunner
string
Default:
noneAccepted values:
jest, noneTest runner to use for unit tests.
useProjectJson
boolean
Use a project.json configuration file instead of inlining the Nx configuration in the package.json file.
skipFormat
Internal
boolean
Default:
falseSkip formatting files.
skipPackageJson
Internal
boolean
Default:
falseDo not add dependencies to package.json.
standaloneConfig
Deprecated
boolean
Default:
trueSplit the project configuration into <projectRoot>/project.json rather than including it inside workspace.json.
Nx only supports standaloneConfig