Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
angular/packages/compiler-cli/package.json

55 lines
1.4 KiB
JSON
Raw Normal View History

build(offline compiler): package the compiler-cli for users Closes #8341
2016-04-29 17:35:36 +00:00
{
fix(compiler): use rootDirs compilerOption to affect genDir layout. Also update package.json to something releasable.
2016-05-03 17:50:55 +00:00
"name": "@angular/compiler-cli",
chore(package.json): make the packages installable
2016-05-27 23:17:16 +00:00
"version": "0.0.0-PLACEHOLDER",
docs: update descriptions in package.jsons
2016-09-14 23:44:39 +00:00
"description": "Angular - the compiler CLI for Node.js",
build(offline compiler): package the compiler-cli for users Closes #8341
2016-04-29 17:35:36 +00:00
"main": "index.js",
refactor: More generic build.sh file
2017-03-02 21:54:35 +00:00
"typings": "index.d.ts",
build(offline compiler): package the compiler-cli for users Closes #8341
2016-04-29 17:35:36 +00: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 09:51:02 +00:00
"ivy-ngcc": "./ngcc/main-ivy-ngcc.js",
"ngcc": "./ngcc/main-ngcc.js",
feat(i18n): extract messages
2016-06-01 21:58:11 +00: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 17:35:36 +00: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 18:20:07 +00: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 12:24:14 +00: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 21:16:52 +00:00
"chokidar": "^3.0.0",
feat(ivy): ngcc project skeleton (#24897) PR Close #24897
2018-07-16 07:49:56 +00: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 14:59:10 +00: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 21:07:59 +00:00
"fs-extra": "4.0.2",
feat(ivy): ngcc project skeleton (#24897) PR Close #24897
2018-07-16 07:49:56 +00: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 10:54:33 +00: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 14:59:10 +00: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 20:07:30 +00:00
"sourcemap-codec": "^1.4.8",
refactor: update to tslib 2.0 and move to direct dependencies (#37198) Tslib version is bound to the TypeScript version used to compile the library. Thus, we shouldn't list `tslib` as a `peerDependencies`. This is because, a user can install libraries which have been compiled with older versions of TypeScript and thus require multiple `tslib` versions to be installed. Reference: TOOL-1374 and TOOL-1375 Closes: #37188 PR Close #37198
2020-05-19 12:35:37 +00:00
"tslib": "^2.0.0",
build: update yargs to 15.3.0 (#36010) This is needed as we require the following fix https://github.com/yargs/yargs/issues/1325 PR Close #36010
2020-03-11 10:18:58 +00:00
"yargs": "15.3.0"
build(offline compiler): package the compiler-cli for users Closes #8341
2016-04-29 17:35:36 +00:00
},
"peerDependencies": {
feat: add TypeScript 3 support (#25275) PR Close #25275
2018-08-05 15:31:27 +00:00
"@angular/compiler": "0.0.0-PLACEHOLDER",
feat(compiler-cli): add support for TypeScript 4.0 (#38076) With this change we add support for TypeScript 4.0 PR Close #38076
2020-07-15 10:21:04 +00:00
"typescript": ">=3.9 <4.1"
build(offline compiler): package the compiler-cli for users Closes #8341
2016-04-29 17:35:36 +00: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 07:01:08 +00: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 09:32:36 +00: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-10 02:33:28 +00:00
},
build(offline compiler): package the compiler-cli for users Closes #8341
2016-04-29 17:35:36 +00:00
"repository": {
"type": "git",
build(packaging): add repository.directory field to package.jsons (#27544) PR Close #27544
2018-12-07 11:12:59 +00: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 17:35:36 +00: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 23:04:35 +00:00
"homepage": "https://github.com/angular/angular/tree/master/packages/compiler-cli",
"ng-update": {
"packageGroup": "NG_UPDATE_PACKAGE_GROUP"
Revert "build: remove wombot proxy registry from package.jsons for release (#37378)" (#37495) This reverts commit 26849ca99dcafc45fb8cb0e97af7aeb85ea11852. PR Close #37495
2020-06-09 01:07:39 +00: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 23:04:35 +00:00
}
Revert "build: remove wombot proxy registry from package.jsons for release (#37378)" (#37495) This reverts commit 26849ca99dcafc45fb8cb0e97af7aeb85ea11852. PR Close #37495
2020-06-09 01:07:39 +00:00
}
Reference in a new issue Copy permalink