@nx/node:application
Nx Application Options Schema.
Nx Application Options Schema.
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/node:application ...
2Show what will be generated without writing to disk:
1nx g application ... --dry-run
2The directory of the new application.
esbuildesbuild, webpackBundler which is used to package the application
nonejest, noneTest runner to use for end-to-end tests
Frontend project that needs to access this application. This sets up proxy configuration.
noneexpress, fastify, koa, nest, noneGenerate the node application using a framework
noneeslint, noneThe tool to use for running lint checks.
^[a-zA-Z][^:]*$The name of the application.
nonejest, noneTest runner to use for unit tests.
Add a docker build target
falseGenerate JavaScript files rather than TypeScript files.
3000The port which the server will be run on
Use @swc/jest instead ts-jest for faster test compilation.
falseWhether 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).
Use a project.json configuration file instead of inlining the Nx configuration in the package.json file.
falseCreate node application at the root of the workspace
falseSkip formatting files
falseDo not add dependencies to package.json.
falseUse babel instead ts-jest.
Use --swcJest instead for faster compilation
trueSplit the project configuration into <projectRoot>/project.json rather than including it inside workspace.json.
Nx only supports standaloneConfig