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

92 lines
2.5 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",
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": {
refactor: setup bundling for `@angular/compiler-cli` package (#43431) All other frameworks packages are now using APF v13 and are strict ESM packages. The compiler-cli does not use APF and is currently shipped with its devmode ES5 CommonJS sources. This is problematic as CommonJS cannot simply import from ECMAScript modules (like `@angular/compiler`). To fix this we use a bundler that allows us to ship the compiler-cli as a strict ESM package. Note: An ESM can import from an ESM without any problems. This is what we need hre. Unfortunatley we need a bundler here because converting the compiler-cli to ESM is non-trivial as relative imports would need an explicit `.js` extension. This work can be simplified by using a bundler that avoids relative imports completely. Note: This commit uses code-splitting to create multiple bundle entry-points for `yarn ngc, `yarn ngcc` etc. This commit removed the old `ivy-ngcc` entry-point that just printed an error message (to reduce amount of bundles having to be configured). PR Close #43431
2021-09-27 23:17:43 +00:00
"ngcc": "./bundles/ngcc/main-ngcc.js",
"ngc": "./bundles/src/bin/ngc.js",
"ng-xi18n": "./bundles/src/bin/ng_xi18n.js"
},
"type": "module",
"exports": {
".": {
"types": "./index.d.ts",
"default": "./bundles/index.js"
},
"./package.json": {
"default": "./package.json"
},
refactor(compiler-cli): expose code needed by Angular CLI (#43431) Exposes code needed by the Angular CLI. Previously the CLI used deep imports for most of these things, but now with bundling the CLI, we no longer support deep imports. We will expose the necessary dependencies for the linker as part of the primary entry-point (I think that is more maintable than re-exporting them as part of the linker). We also expose the ngcc entry-point for the CLI with a new constant that will point to the ngcc command line entry-point (which the CLI relies on). PR Close #43431
2021-09-20 17:30:08 +00:00
"./ngcc": {
"types": "./ngcc/index.d.ts",
"default": "./bundles/ngcc/index.js"
},
refactor: setup bundling for `@angular/compiler-cli` package (#43431) All other frameworks packages are now using APF v13 and are strict ESM packages. The compiler-cli does not use APF and is currently shipped with its devmode ES5 CommonJS sources. This is problematic as CommonJS cannot simply import from ECMAScript modules (like `@angular/compiler`). To fix this we use a bundler that allows us to ship the compiler-cli as a strict ESM package. Note: An ESM can import from an ESM without any problems. This is what we need hre. Unfortunatley we need a bundler here because converting the compiler-cli to ESM is non-trivial as relative imports would need an explicit `.js` extension. This work can be simplified by using a bundler that avoids relative imports completely. Note: This commit uses code-splitting to create multiple bundle entry-points for `yarn ngc, `yarn ngcc` etc. This commit removed the old `ivy-ngcc` entry-point that just printed an error message (to reduce amount of bundles having to be configured). PR Close #43431
2021-09-27 23:17:43 +00:00
"./linker": {
"types": "./linker/index.d.ts",
"default": "./bundles/linker/index.js"
},
"./linker/babel": {
"types": "./linker/babel/index.d.ts",
"default": "./bundles/linker/babel/index.js"
refactor: switch packages away from deep cross-package imports (#43431) The Angular Core and localize package currently use deep imports for code that is shipped. This is problematic as we want to ship the compiler-cli as full-ESM. To achieve this we need to use a bundler and this breaks deep imports. We use a bundler for the compiler CLI because for full ESM compatibility, we would need to explicitly add the `.js` extension to all relative imports. This is very cumbersome and prone to mistakes so to mitigate this problem in a safe way, we bundle the compiler-cli. Note: Deep imports continue to exist for the language service as it bundles the compiler-cli. PR Close #43431
2021-09-18 16:01:08 +00:00
},
"./private/bazel": {
"types": "./private/bazel.d.ts",
"default": "./bundles/private/bazel.js"
},
"./private/localize": {
"types": "./private/localize.d.ts",
"default": "./bundles/private/localize.js"
},
"./private/migrations": {
"types": "./private/migrations.d.ts",
"default": "./bundles/private/migrations.js"
refactor(compiler-cli): do not use `__filename` or `__dirname` global for ESM compatibility (#43431) Switches the compiler-cli usage of `__filename` to `import.meta.url` when ESM bundles are generated. Unfortunately we cannot start using only `import.meta` yet as we still build and run all code in Angular in CommonJS module output for devmode tests. This commit also fixes various instances where a jasmine spy was applied on a namespace export that will break with ES module (and the interop for CommonJS output). We fix these spies by using a default import. PR Close #43431
2021-09-25 16:46:59 +00:00
},
refactor(compiler-cli): expose tooling code through `private` entry-point (#43431) Similar to the other private entry-points we have added for localize, bazel or the migrations, we should expose the tooling code through a dedicated private export. This will make the compiler-cli exports more consistent and it will become easier for the CLI to export necessary code. PR Close #43431
2021-09-30 17:37:11 +00:00
"./private/tooling": {
"types": "./private/tooling.d.ts",
"default": "./bundles/private/tooling.js"
},
refactor(compiler-cli): do not use `__filename` or `__dirname` global for ESM compatibility (#43431) Switches the compiler-cli usage of `__filename` to `import.meta.url` when ESM bundles are generated. Unfortunately we cannot start using only `import.meta` yet as we still build and run all code in Angular in CommonJS module output for devmode tests. This commit also fixes various instances where a jasmine spy was applied on a namespace export that will break with ES module (and the interop for CommonJS output). We fix these spies by using a default import. PR Close #43431
2021-09-25 16:46:59 +00:00
"./ngcc/src/execution/cluster/ngcc_cluster_worker": {
"default": "./bundles/ngcc/src/execution/cluster/ngcc_cluster_worker.js"
},
"./ngcc/src/locking/lock_file_with_child_process/ngcc_lock_unlocker": {
"default": "./bundles/ngcc/src/locking/lock_file_with_child_process/ngcc_lock_unlocker.js"
refactor: setup bundling for `@angular/compiler-cli` package (#43431) All other frameworks packages are now using APF v13 and are strict ESM packages. The compiler-cli does not use APF and is currently shipped with its devmode ES5 CommonJS sources. This is problematic as CommonJS cannot simply import from ECMAScript modules (like `@angular/compiler`). To fix this we use a bundler that allows us to ship the compiler-cli as a strict ESM package. Note: An ESM can import from an ESM without any problems. This is what we need hre. Unfortunatley we need a bundler here because converting the compiler-cli to ESM is non-trivial as relative imports would need an explicit `.js` extension. This work can be simplified by using a bundler that avoids relative imports completely. Note: This commit uses code-splitting to create multiple bundle entry-points for `yarn ngc, `yarn ngcc` etc. This commit removed the old `ivy-ngcc` entry-point that just printed an error message (to reduce amount of bundles having to be configured). PR Close #43431
2021-09-27 23:17:43 +00:00
}
build(offline compiler): package the compiler-cli for users Closes #8341
2016-04-29 17:35:36 +00:00
},
"dependencies": {
refactor(localize): update version of Babel (#44931) The `@angular/localize` package depends on a version of Babel that is two years old, so this commit updates to the latest version. Some changes were made to the linker and compliance tests to account for slight changes in source maps, along with a few code updates because of changes to the typings of Babel. PR Close #44931
2022-02-01 21:12:44 +00:00
"@babel/core": "^7.17.2",
refactor(compiler): replace deprecated `sourcemap-codec` (#48387) `sourcemap-codec` as been deprecated in favor of `@jridgewell/sourcemap-codec`. See: https://www.npmjs.com/package/sourcemap-codec?activeTab=versions PR Close #48387
2022-12-07 15:45:56 +00:00
"@jridgewell/sourcemap-codec": "^1.4.14",
build(offline compiler): package the compiler-cli for users Closes #8341
2016-04-29 17:35:36 +00:00
"reflect-metadata": "^0.1.2",
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",
build: update dependency-graph to version 0.11.0 (#41665) PR Close #41665
2021-04-14 07:19:56 +00:00
"dependency-graph": "^0.11.0",
build: update all non-major dependencies (#48372) See associated pull request for more information. PR Close #48372
2022-12-06 17:33:10 +00:00
"magic-string": "^0.27.0",
build: update semver to version 7.3.5 (#41715) PR Close #41715
2021-04-14 07:50:26 +00:00
"semver": "^7.0.0",
feat(core): support TypeScript 4.4 (#43281) Adds support for TypeScript 4.4. High-level overview of the changes made in this PR: * Bumps the various packages to `typescript@4.4.2` and `tslib@2.3.0`. * The `useUnknownInCatchVariables` compiler option has been disabled so that we don't have to cast error objects explicitly everywhere. * TS now passes in a third argument to the `__spreadArray` call inside child class constructors. I had to update a couple of places in the runtime and ngcc to be able to pick up the calls correctly. * TS now generates code like `(0, foo)(arg1, arg2)` for imported function calls. I had to update a few of our tests to account for it. See https://github.com/microsoft/TypeScript/pull/44624. * Our `ngtsc` test setup calls the private `matchFiles` function from TS. I had to update our usage, because a new parameter was added. * There was one place where we were setting the readonly `hasTrailingComma` property. I updated the usage to pass in the value when constructing the object instead. * Some browser types were updated which meant that I had to resolve some trivial type errors. * The downlevel decorators tranform was running into an issue where the Closure synthetic comments were being emitted twice. I've worked around it by recreating the class declaration node instead of cloning it. PR Close #43281
2021-09-22 18:50:59 +00:00
"tslib": "^2.3.0",
refactor: update yargs to new API for ESM compatibility (#43431) Given that we ship all of compiler-cli and localize in ESM mode now, we need to use a ESM compatible version of Yargs. The latest version seems ESM compatible but with some small API changes. This commit updates Yargs and updates the command line option code to use the new API. PR Close #43431
2021-09-26 10:29:54 +00:00
"yargs": "^17.2.1"
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(core): support TypeScript 4.9 (#48005) Updates to TypeScript 4.9 and resolves some of the errors and deprecation warnings that showed up as a result. PR Close #48005
2022-12-05 12:32:40 +00:00
"typescript": ">=4.8.2 <5.0"
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",
feat(compiler-cli): update supported range of node versions (#41544) Update the supported range of node versions for Angular. Angular now supports node >=12.14.1 to <16.0.0, dropping support for Node v10. PR Close #41544
2021-04-12 19:12:28 +00:00
"engines": {
feat(core): add support for Node.js version 18 (#47730) This change aligns with the supported Node.js versions of the Angular CLI. See: https://github.com/angular/angular-cli/pull/24026 BREAKING CHANGE: Angular no longer supports Node.js versions `14.[15-19].x` and `16.[10-12].x`. Current supported versions of Node.js are `14.20.x`, `16.13.x` and `18.10.x`. PR Close #47730
2022-10-11 12:39:05 +00:00
"node": "^14.20.0 || ^16.13.0 || >=18.10.0"
feat(compiler-cli): update supported range of node versions (#41544) Update the supported range of node versions for Angular. Angular now supports node >=12.14.1 to <16.0.0, dropping support for Node v10. PR Close #41544
2021-04-12 19:12:28 +00:00
},
build(offline compiler): package the compiler-cli for users Closes #8341
2016-04-29 17:35:36 +00:00
"bugs": {
"url": "https://github.com/angular/angular/issues"
},
build: clean up references to old `master` branch (#45856) Cleans up all references to the `master` branch we renamed to `main` across Angular. PR Close #45856
2022-05-03 18:34:54 +00:00
"homepage": "https://github.com/angular/angular/tree/main/packages/compiler-cli",
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
"ng-update": {
"packageGroup": "NG_UPDATE_PACKAGE_GROUP"
}
refactor(compiler-cli): implement `BabelAstFactory` and `AstHost`s (#38866) This commit adds the `AstHost` interface, along with implementations for both Babel and TS. It also implements the Babel vesion of the `AstFactory` interface, along with a linker specific implementation of the `ImportGenerator` interface. These classes will be used by the new "ng-linker" to transform prelinked library code using a Babel plugin. PR Close #38866
2020-09-16 10:19:56 +00:00
}
Reference in a new issue Copy permalink