angular-docs-cn/packages/compiler-cli/package.json

{
  "name": "@angular/compiler-cli",
  "version": "0.0.0-PLACEHOLDER",
  "description": "Angular - the compiler CLI for Node.js",
  "main": "index.js",
  "typings": "index.d.ts",
  "bin": {
    "ivy-ngcc": "./ngcc/main-ivy-ngcc.js",
    "ngcc": "./ngcc/main-ngcc.js",
    "ngc": "./src/main.js",
    "ng-xi18n": "./src/extract_i18n.js"
  },
  "dependencies": {
    "reflect-metadata": "^0.1.2",
    "minimist": "^1.2.0",
    "canonical-path": "1.0.0",
    "chokidar": "^3.0.0",
    "convert-source-map": "^1.5.1",
    "dependency-graph": "^0.7.2",
    "fs-extra": "4.0.2",
    "magic-string": "^0.25.0",
    "semver": "^6.3.0",
    "source-map": "^0.6.1",
    "sourcemap-codec": "^1.4.8",
    "yargs": "13.1.0"
  },
  "peerDependencies": {
    "@angular/compiler": "0.0.0-PLACEHOLDER",
    "tslib": "^1.10.0",
    "typescript": ">=3.6 <3.8"
  },
  "engines": {
    "node": ">=10.0"
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/angular/angular.git",
    "directory": "packages/compiler-cli"
  },
  "keywords": [
    "angular",
    "compiler"
  ],
  "license": "MIT",
  "bugs": {
    "url": "https://github.com/angular/angular/issues"
  },
  "homepage": "https://github.com/angular/angular/tree/master/packages/compiler-cli",
  "ng-update": {
    "packageGroup": "NG_UPDATE_PACKAGE_GROUP"
  },
  "publishConfig": {
    "registry": "https://wombat-dressing-room.appspot.com"
  }
}
build(offline compiler): package the compiler-cli for users Closes #8341 2016-04-29 13:35:36 -04:00			`{`
fix(compiler): use rootDirs compilerOption to affect genDir layout. Also update package.json to something releasable. 2016-05-03 13:50:55 -04:00			`"name": "@angular/compiler-cli",`
chore(package.json): make the packages installable 2016-05-27 19:17:16 -04:00			`"version": "0.0.0-PLACEHOLDER",`
docs: update descriptions in package.jsons 2016-09-14 19:44:39 -04:00			`"description": "Angular - the compiler CLI for Node.js",`
build(offline compiler): package the compiler-cli for users Closes #8341 2016-04-29 13:35:36 -04:00			`"main": "index.js",`
refactor: More generic build.sh file 2017-03-02 16:54:35 -05:00			`"typings": "index.d.ts",`
build(offline compiler): package the compiler-cli for users Closes #8341 2016-04-29 13:35:36 -04:00			`"bin": {`
fix(ngcc): rename the executable from `ivy-ngcc` to `ngcc` (#33140) Previously, the executable for the Angular Compatibility Compiler (`ngcc`) was called `ivy-ngcc`. This would be confusing for users not familiar with our internal terminology, especially given that we call it `ngcc` in all our docs and presentations. This commit renames the executable to `ngcc` and replaces `ivy-ngcc` with a script that errors with an informative message (prompting the user to use `ngcc` instead). Jira issue: [FW-1624](https://angular-team.atlassian.net/browse/FW-1624) PR Close #33140 2019-10-14 05:51:02 -04:00			`"ivy-ngcc": "./ngcc/main-ivy-ngcc.js",`
			`"ngcc": "./ngcc/main-ngcc.js",`
feat(i18n): extract messages 2016-06-01 17:58:11 -04:00			`"ngc": "./src/main.js",`
			`"ng-xi18n": "./src/extract_i18n.js"`
build(offline compiler): package the compiler-cli for users Closes #8341 2016-04-29 13:35:36 -04:00			`},`
			`"dependencies": {`
			`"reflect-metadata": "^0.1.2",`
refactor(compiler-cli): use the transformer based compiler by default The source map does not currently work with the transformer pipeline. It will be re-enabled after TypeScript 2.4 is made the min version. To revert to the former compiler, use the `disableTransformerPipeline` in tsconfig.json: ``` { "angularCompilerOptions": { "disableTransformerPipeline": true } } ``` 2017-08-02 14:20:07 -04:00			`"minimist": "^1.2.0",`
build: update `canonical-path` dependency (#26719) This new version (1.0.0) provides a typings file! PR Close #26719 2018-10-24 08:24:14 -04:00			`"canonical-path": "1.0.0",`
build(compiler-cli): update to chokidar 3.x (#35047) Update from chokidar 2.x to 3.x in ngc/ngtsc, to eliminate any possibility of a security issue with a downstream dependency of the package. FW-1809 #resolve PR Close #35047 2020-01-29 16:16:52 -05:00			`"chokidar": "^3.0.0",`
feat(ivy): ngcc project skeleton (#24897) PR Close #24897 2018-07-16 03:49:56 -04:00			`"convert-source-map": "^1.5.1",`
fix(ivy): ngcc should compile entry-points in the correct order (#25862) The compiler should process all an entry-points dependencies before processing that entry-point. PR Close #25862 2018-08-09 10:59:10 -04:00			`"dependency-graph": "^0.7.2",`
feat(ngcc): automatically clean outdated ngcc artifacts (#35079) If ngcc gets updated to a new version then the artifacts left in packages that were processed by the previous version are possibly invalid. Previously we just errored if we found packages that had already been processed by an outdated version. Now we automatically clean the packages that have outdated artifacts so that they can be reprocessed correctly with the current ngcc version. Fixes #35082 PR Close #35079 2020-01-31 16:07:59 -05:00			`"fs-extra": "4.0.2",`
feat(ivy): ngcc project skeleton (#24897) PR Close #24897 2018-07-16 03:49:56 -04:00			`"magic-string": "^0.25.0",`
feat(ngcc): support version ranges in project/default configurations (#33008) By appending a version range to the package name, it is now possible to target configuration to specific versions of a package. PR Close #33008 2019-10-04 06:54:33 -04:00			`"semver": "^6.3.0",`
fix(ivy): ngcc should compile entry-points in the correct order (#25862) The compiler should process all an entry-points dependencies before processing that entry-point. PR Close #25862 2018-08-09 10:59:10 -04:00			`"source-map": "^0.6.1",`
feat(ngcc): implement source-map flattening (#35132) The library used by ngcc to update the source files (MagicString) is able to generate a source-map but it is not able to account for any previous source-map that the input text is already associated with. There have been various attempts to fix this but none have been very successful, since it is not a trivial problem to solve. This commit contains a novel approach that is able to load up a tree of source-files connected by source-maps and flatten them down into a single source-map that maps directly from the final generated file to the original sources referenced by the intermediate source-maps. PR Close #35132 2020-02-16 15:07:30 -05:00			`"sourcemap-codec": "^1.4.8",`
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722 2019-04-05 04:44:43 -04:00			`"yargs": "13.1.0"`
build(offline compiler): package the compiler-cli for users Closes #8341 2016-04-29 13:35:36 -04:00			`},`
			`"peerDependencies": {`
feat: add TypeScript 3 support (#25275) PR Close #25275 2018-08-05 11:31:27 -04:00			`"@angular/compiler": "0.0.0-PLACEHOLDER",`
feat: typescript 3.6 support (#32946) BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6 Fixes #32380 PR Close #32946 2019-10-01 19:44:50 -04:00			`"tslib": "^1.10.0",`
build: typescript 3.7 support (#33717) This PR updates TypeScript version to 3.7 while retaining compatibility with TS3.6. PR Close #33717 2019-11-09 13:36:22 -05:00			`"typescript": ">=3.6 <3.8"`
build(offline compiler): package the compiler-cli for users Closes #8341 2016-04-29 13:35:36 -04:00			`},`
feat: add support for typescript 3.2 (#27536) https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-2.html https://blogs.msdn.microsoft.com/typescript/2018/11/29/announcing-typescript-3-2/ Any application using tsickle for closure compatibility will need to update it's tsickle dependency to 0.34 PR Close #27536 2018-12-07 02:01:08 -05:00			`"engines": {`
feat(compiler-cli): require node 10 as runtime engine (#34722) Similar to c602563 this commit aligns the node.js version requirements of the Angular compiler with Angular CLI. PR Close #34722 2020-01-17 04:32:36 -05:00			`"node": ">=10.0"`
feat(compiler-cli): require node 8 as runtime engine (#22669) This is not expected to be a breaking change for anyone who's on Node LTS (currently v8) and aligns @angular/compilar-cli with @angular/cli's runtime requirements. PR Close #22669 2018-03-09 21:33:28 -05:00			`},`
build(offline compiler): package the compiler-cli for users Closes #8341 2016-04-29 13:35:36 -04:00			`"repository": {`
			`"type": "git",`
build(packaging): add repository.directory field to package.jsons (#27544) PR Close #27544 2018-12-07 06:12:59 -05:00			`"url": "https://github.com/angular/angular.git",`
			`"directory": "packages/compiler-cli"`
build(offline compiler): package the compiler-cli for users Closes #8341 2016-04-29 13:35:36 -04:00			`},`
			`"keywords": [`
			`"angular",`
			`"compiler"`
			`],`
			`"license": "MIT",`
			`"bugs": {`
			`"url": "https://github.com/angular/angular/issues"`
			`},`
release: add ng update package group metadata to angular (#22482) "ng update" supports having multiple packages as part of a group which should be updated together, meaning that e.g. calling "ng update @angular/core" would be equivalent to updating all packages of the group (that are part of the package.json already). In order to support the grouping feature, the package.json of the version the user is updating to needs to include an "ng-update" key that points to this metadata. The entire specification for the update workflow can be found here: https://github.com/hansl/devkit/blob/2e8b12a4ef53833dc006e8711acf95cf3a6cf24e/docs/specifications/update.md PR Close #22482 2018-02-27 18:04:35 -05:00			`"homepage": "https://github.com/angular/angular/tree/master/packages/compiler-cli",`
			`"ng-update": {`
			`"packageGroup": "NG_UPDATE_PACKAGE_GROUP"`
build: set up all packages to publish via wombot proxy (#33747) PR Close #33747 2019-11-11 17:18:13 -05:00			`},`
feat(ngcc): implement source-map flattening (#35132) The library used by ngcc to update the source files (MagicString) is able to generate a source-map but it is not able to account for any previous source-map that the input text is already associated with. There have been various attempts to fix this but none have been very successful, since it is not a trivial problem to solve. This commit contains a novel approach that is able to load up a tree of source-files connected by source-maps and flatten them down into a single source-map that maps directly from the final generated file to the original sources referenced by the intermediate source-maps. PR Close #35132 2020-02-16 15:07:30 -05:00			`"publishConfig": {`
			`"registry": "https://wombat-dressing-room.appspot.com"`
release: add ng update package group metadata to angular (#22482) "ng update" supports having multiple packages as part of a group which should be updated together, meaning that e.g. calling "ng update @angular/core" would be equivalent to updating all packages of the group (that are part of the package.json already). In order to support the grouping feature, the package.json of the version the user is updating to needs to include an "ng-update" key that points to this metadata. The entire specification for the update workflow can be found here: https://github.com/hansl/devkit/blob/2e8b12a4ef53833dc006e8711acf95cf3a6cf24e/docs/specifications/update.md PR Close #22482 2018-02-27 18:04:35 -05:00			`}`
feat(ngcc): implement source-map flattening (#35132) The library used by ngcc to update the source files (MagicString) is able to generate a source-map but it is not able to account for any previous source-map that the input text is already associated with. There have been various attempts to fix this but none have been very successful, since it is not a trivial problem to solve. This commit contains a novel approach that is able to load up a tree of source-files connected by source-maps and flatten them down into a single source-map that maps directly from the final generated file to the original sources referenced by the intermediate source-maps. PR Close #35132 2020-02-16 15:07:30 -05:00			`}`