@nx/node:application
Nx Application Options Schema.
Webinar April 17: Making the Argument for MonoreposWebinar April 17: Making the Argument for MonoreposRegister now!
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/node:application ...
2
Show what will be generated without writing to disk:
1nx g application ... --dry-run
2
^[a-zA-Z][^:]*$
The name of the application.
esbuild
esbuild
, webpack
Bundler which is used to package the application
The directory of the new application.
Frontend project that needs to access this application. This sets up proxy configuration.
none
express
, fastify
, koa
, nest
, none
Generate the node application using a framework
Add a docker build target
jest
jest
, none
Test runner to use for end to end (e2e) tests
false
Generate JavaScript files rather than TypeScript files.
eslint
eslint
The tool to use for running lint checks.
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
).
false
Use pascal case file names.
3000
The port which the server will be run on
false
Use @swc/jest
instead ts-jest
for faster test compilation.
false
Whether or not to configure the ESLint parserOptions.project
option. We do not do this by default for lint performance reasons.
Add tags to the application (used for linting).
jest
jest
, none
Test runner to use for unit tests.
false
Create node application at the root of the workspace
false
Skip formatting files
false
Do not add dependencies to package.json
.
false
Use babel
instead ts-jest
.
Use --swcJest instead for faster compilation
true
Split the project configuration into <projectRoot>/project.json
rather than including it inside workspace.json
.
Nx only supports standaloneConfig