Formatter Validator Minifier Escape / Unescape JSON ↔ String JSON ↔ YAML JSON → CSV NDJSON / JSON Lines JSON → Types JSON ↔ XML JSON Diff JSON Patch Canonicalize (RFC 8785) Schema Validator Schema Generator JSONPath Tester JWT Decoder JSON Errors Schemas More Tools
JSONTools / Schema registry / nest-cli
Schema registry

nest-cli

A progressive Node.js framework for building efficient and scalable server-side applications 🚀

.nestcli.json.nest-cli.jsonnest-cli.jsonnest.json

Check your file against this schema

Opens the validator with this schema already loaded. Paste your .nestcli.json and it validates in your browser — nothing is uploaded.

Validate a .nestcli.json → View raw schema

Fields

Generated directly from the schema, following local $refs, to two levels of nesting.

Field Type Description
languagestring
default: "ts"
collectionstringPoints at the collection of schematics used to generate components. you generally should not change this value.
default: "@nestjs/schematics"
sourceRootstringPoints at the root of the source code for the single project in standard mode structures, or the default project in monorepo mode structures.
default: "src"
entryFilestringThe entry file where 'nest start' work with. Default to 'main'.
default: "main"
monorepoboolean(monorepo only) For a monorepo mode structure, this value is always true.
default: false
rootstring(monorepo only) Points at the project root of the default project.
default: ""
compilerOptionsobjectA map with keys specifying compiler options and values specifying the option setting. See https://docs.nestjs.com/cli/monorepo#global-compiler-options for details
default: {}
compilerOptions.tsConfigPathstring(monorepo only) Points at the file containing the tsconfig.json settings that will be used when nest build or nest start is called without a project option (e.g., when the default project is built or started). 'nest build' will not work as
default: "tsconfig.build.json"
compilerOptions.builderanyOf
compilerOptions.typeCheckbooleanIf true, enable type checking (when SWC is used). See https://docs.nestjs.com/recipes/swc#type-checking for details.
default: false
compilerOptions.webpackbooleanIf true, use webpack compiler (deprecated option, use `builder` instead). If false or not present, use tsc. In monorepo mode, the default is true (use webpack), in standard mode, the default is false (use tsc). See
default: false
compilerOptions.webpackConfigPathstringPoints at a webpack options file. If not specified, Nest looks for the file webpack.config.js.
default: "webpack.config.js"
compilerOptions.pluginsarray
default: []
compilerOptions.assetsarrayEnables automatically distributing non-TypeScript assets whenever a compilation step begins (asset distribution does not happen on incremental compiles in --watch mode). Accept glob-like string and object. See
default: []
compilerOptions.watchAssetsbooleanIf true, run in watch-mode, watching all non-TypeScript assets. Setting watchAssets in a top-level compilerOptions property overrides any watchAssets settings within the assets property.
default: false
compilerOptions.deleteOutDirbooleanIf true, whenever the compiler is invoked, it will first remove the compilation output directory (as configured in tsconfig.json, where the default is ./dist).
default: false
compilerOptions.manualRestartbooleanIf true, enables the shortcut `rs` to manually restart the server.
default: false
generateOptionsobjectA map with keys specifying global generate options and values specifying the option setting. See https://docs.nestjs.com/cli/monorepo#global-generate-options for details
default: {}
generateOptions.specboolean | objectIf the value is boolean, a value of true enables spec generation by default and a value of false disables it. A flag passed on the CLI command line overrides this setting, as does a project-specific generateOptions setting (more below). If
generateOptions.spec.applicationbooleanGenerate spec file for application schematics or not.
generateOptions.spec.classbooleanDisable spec file generation for class schematics.
generateOptions.spec.clbooleanAlias for class
generateOptions.spec.configurationbooleanGenerate spec file for configuration schematics or not.
generateOptions.spec.configbooleanAlias for configuration
generateOptions.spec.controllerbooleanGenerate spec file for controller schematics or not.
generateOptions.spec.cobooleanAlias for controller
generateOptions.spec.decoratorbooleanGenerate spec file for decorator schematics or not.
generateOptions.spec.dbooleanAlias for decorator
generateOptions.spec.filterbooleanGenerate spec file for filter schematics or not.
generateOptions.spec.fbooleanAlias for filter
generateOptions.spec.gatewaybooleanGenerate spec file for gateway schematics or not.
generateOptions.spec.gabooleanAlias for gateway
generateOptions.spec.guardbooleanGenerate spec file for guard schematics or not.
generateOptions.spec.gubooleanAlias for guard
generateOptions.spec.interceptorbooleanGenerate spec file for interceptor schematics or not.
generateOptions.spec.inbooleanAlias for interceptor
generateOptions.spec.interfacebooleanGenerate spec file for interface schematics or not.
generateOptions.spec.middlewarebooleanGenerate spec file for middleware schematics or not.
generateOptions.spec.mibooleanAlias for middleware
generateOptions.spec.modulebooleanGenerate spec file for module schematics or not.
generateOptions.spec.mobooleanAlias for module
generateOptions.spec.pipebooleanGenerate spec file for pipe schematics or not.
generateOptions.spec.pibooleanAlias for pipe
generateOptions.spec.providerbooleanGenerate spec file for provider schematics or not.
generateOptions.spec.prbooleanAlias for provider
generateOptions.spec.resolverbooleanGenerate spec file for resolver schematics or not.
generateOptions.spec.rbooleanAlias for resolver
generateOptions.spec.servicebooleanGenerate spec file for service schematics or not.
generateOptions.spec.sbooleanAlias for resolver
generateOptions.spec.librarybooleanGenerate spec file for library schematics or not.
generateOptions.spec.libbooleanAlias for library
generateOptions.spec.sub-appbooleanGenerate spec file for sub-app schematics or not.
generateOptions.spec.appbooleanAlias for sub-app
generateOptions.spec.resourcebooleanGenerate spec file for resource schematics or not.
generateOptions.spec.resbooleanAlias for resource
generateOptions.flatbooleanIf true, all generate commands will generate a flat structure
default: false
generateOptions.baseDirstringBase directory
default: ""
projectsobject
default: {}
defaultLibraryPrefixstringDefault import prefix for newly generated libraries.
default: "@app"

What we found in this schema

Specification sections for the keywords in this schema

Keyword Document Section
$commentJSON Schema Core, draft 2020-12§8.3 — Comments With "$comment"
$idJSON Schema Core, draft 2020-12§8.2.1 — The "$id" Keyword
$refJSON Schema Core, draft 2020-12§8.2.3.1 — Direct References with "$ref"
$schemaJSON Schema Core, draft 2020-12§8.1.1 — "$schema"
additionalPropertiesJSON Schema Core, draft 2020-12§10.3.2.3 — "additionalProperties"
anyOfJSON Schema Core, draft 2020-12§10.2.1.2 — "anyOf"
defaultJSON Schema Validation, draft 2020-12§9.2 — "default"
descriptionJSON Schema Validation, draft 2020-12§9.1 — "title" and "description"
enumJSON Schema Validation, draft 2020-12§6.1.2 — "enum"
itemsJSON Schema Core, draft 2020-12§10.3.1.2 — "items"
propertiesJSON Schema Core, draft 2020-12§10.3.2.1 — "properties"
typeJSON Schema Validation, draft 2020-12§6.1.1 — "type"

Documents

Attribution

This schema comes from SchemaStore, distributed under the Apache License 2.0. Copyright 2015–present Mads Kristensen and contributors. View the original file. The field table and audit on this page are generated by JSONTools.tools; the schema itself is unmodified.

← All schemas