@nx/express:application
Nx Application Options Schema.
Monorepo World: October 7, 2024Monorepo World: October 7, 2024Join us!
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/express:application ...
2Show what will be generated without writing to disk:
1nx g application ... --dry-run
2The directory of the new application.
Frontend project that needs to access this application. This sets up proxy configuration.
falseGenerate JavaScript files rather than TypeScript files.
eslinteslintThe tool to use for running lint checks.
^[a-zA-Z][^:]*$The name of the application.
as-provided, derivedWhether 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).
falseUse pascal case file names.
falseSkip formatting files.
falseDo not add dependencies to package.json.
falseUse @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).
jestjest, noneTest runner to use for unit tests.
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