nx/docs/angular/api-nest/generators/application.md
Craigory Coppola bdcbac4445
feat(core): standalone project configuration is default (#7351)
* feat(core): standalone project configuration is default

* chore(core): changes to e2e tests

* fix(core): intuit projects when inside their directories when using project.json files

* chore(core): e2e changes

* fix(core): standalone configurations work with npm-project generator

* chore(core): e2e tests should use standalone configurations

* chore(core): e2e fixes per review
2021-10-16 00:07:12 +02:00

1.5 KiB

@nrwl/nest:application

Create a NestJS application.

Usage

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

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

You can specify the collection explicitly as follows:

nx g @nrwl/nest:application ...

Show what will be generated without writing to disk:

nx g application ... --dry-run

Options

name (required)

Type: string

The name of the application.

directory

Type: string

The directory of the new application.

frontendProject

Type: string

Frontend project that needs to access this application. This sets up proxy configuration.

linter

Default: eslint

Type: string

Possible values: eslint, none

The tool to use for running lint checks.

setParserOptionsProject

Default: false

Type: boolean

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

skipFormat

Default: false

Type: boolean

Skip formatting files.

skipPackageJson

Default: false

Type: boolean

Do not add dependencies to package.json.

standaloneConfig

Type: boolean

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

tags

Type: string

Add tags to the application (used for linting).

unitTestRunner

Default: jest

Type: string

Possible values: jest, none

Test runner to use for unit tests.