@nrwl/webSee schema

@nrwl/web:application

Create a web application using swc or babel as compiler.

Examples

Create an application named my-app:

nx g @nrwl/web:application my-app

Usage

nx generate application ...
nx g app ... #same

By default, Nx will search for application in the default collection provisioned in workspace.json.

You can specify the collection explicitly as follows:

nx g @nrwl/web:application ...

Show what will be generated without writing to disk:

nx g application ... --dry-run

Options

name

Required
string
Pattern: ^[a-zA-Z].*$

The name of the application.

bundler

string
Default: webpack
Accepted values: webpack, none, vite

The bundler to use.

compiler

string
Default: babel
Accepted values: babel, swc

The compiler to use

directory

string

The directory of the new application.

e2eTestRunner

string
Default: cypress
Accepted values: cypress, none

Test runner to use for end to end (e2e) tests

inSourceTests

boolean
Default: false

When using Vitest, separate spec files will not be generated and instead will be included within the source files.

linter

string
Default: eslint
Accepted values: eslint

The tool to use for running lint checks.

style

string
Default: css

The file extension to be used for style files.

setParserOptionsProject

boolean
Default: false

Whether or not to configure the ESLint parserOptions.project option. We do not do this by default for lint performance reasons.

tags

string

Add tags to the application (used for linting)

unitTestRunner

string
Accepted values: 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

skipFormat

boolean
Default: false

Skip formatting files

standaloneConfig

Deprecated
boolean
Default: true

Split the project configuration into <projectRoot>/project.json rather than including it inside workspace.json

Nx only supports standaloneConfig