@nx/web:application
Create a web application using swc
or babel
as compiler.
The State of JS survey is live, featuring a monorepo tools sectionThe State of JS survey is live, featuring a monorepo tools sectionVote for us
Create a web application using swc
or babel
as compiler.
Create an application named my-app
:
1nx g @nx/web:application my-app
2
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/web: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.
webpack
webpack
, none
, vite
The bundler to use.
swc
swc
, babel
The compiler to use
The directory of the new application.
cypress
cypress
, playwright
, none
Test runner to use for end to end (e2e) tests
false
When using Vitest, separate spec files will not be generated and instead will be included within the source files.
eslint
eslint
, none
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
).
css
The file extension to be used for style files.
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
, vitest
, none
Test runner to use for unit tests. Default value is 'jest' when using 'webpack' or 'none' as the bundler and 'vitest' when using 'vite' as the bundler
false
Skip formatting files
true
Split the project configuration into <projectRoot>/project.json
rather than including it inside workspace.json
Nx only supports standaloneConfig