skills/angular__angular
1
0
Fork 0
mirror of https://github.com/angular/angular.git synced 2026-09-14 13:54:52 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
76c60a609fecb7bb7d9de576e9486d22fc4e932e
angular__angular/packages/bazel/package.json
T

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

55 lines
1.3 KiB
JSON
Raw Normal View History

refactor(compiler-cli): move ngc-wrapped to packages/bazel (#18733) See design: https://goo.gl/rAeYWx PR Close #18733
2017-08-16 09:02:20 -07:00
{
"name": "@angular/bazel",
"version": "0.0.0-PLACEHOLDER",
"description": "Angular - bazel build rules",
"author": "angular",
"license": "MIT",
feat(bazel): 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 12:12:19 -07:00
"engines": {
feat(core): update Node.js version support (#60545) Node.js v18 will reach End-of-Life on April 30, 2025, and will no longer be supported in Angular v20. Node.js Release Schedule: https://github.com/nodejs/release#release-schedule BREAKING CHANGE: - Angular no longer supports Node.js v18. - Node.js versions 22.0 to 22.10 are also no longer supported. Before upgrading to Angular v20, ensure the Node.js version is at least 20.11.1. For the full list of supported versions, visit: https://angular.dev/reference/versions PR Close #60545
2025-03-25 07:58:02 +00:00
"node": "^20.11.1 || >=22.11.0"
feat(bazel): 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 12:12:19 -07:00
},
build: idiomatic install of @angular/bazel npm package (#26258) (#26488) PR Close #26488
2018-10-16 13:20:00 -07:00
"bin": {
refactor: update `packages/bazel` npm artifact to not rely on `defaults.bzl` (#48521) Fixes that we temporarily broke the Bazel npm package artifact as part of the ESM work. This commit adjusts it and also makes the artifact subsitutions more maintainable. PR Close #48521
2022-12-17 10:32:29 +00:00
"ngc-wrapped": "./src/ngc-wrapped/index.mjs",
"packager": "./src/ng_package/packager.mjs",
"xi18n": "./src/ngc-wrapped/extract_i18n.mjs"
build: idiomatic install of @angular/bazel npm package (#26258) (#26488) PR Close #26488
2018-10-16 13:20:00 -07:00
},
"typings": "./src/ngc-wrapped/index.d.ts",
fix(bazel): add configuration_env_vars = ["compile"] to generated @npm//@angular/bazel/bin:ngc-wrapped nodejs_binary (#29694) PR Close #29694
2019-04-03 16:59:20 -07:00
"bazelBin": {
"ngc-wrapped": {
"additionalAttributes": {
build: disable bazel nodejs linker to improve stability on windows (#45872) The NodeJS Bazel linker does not work well on Windows because there is no sandboxing and linker processes from different tests will attempt to modify the same `node_modules`, causing concurrency race conditions and resulting in flakiness. PR Close #45872
2022-05-04 12:47:58 +00:00
"templated_args": "[\"--nobazel_run_linker\"]"
fix(bazel): add configuration_env_vars = ["compile"] to generated @npm//@angular/bazel/bin:ngc-wrapped nodejs_binary (#29694) PR Close #29694
2019-04-03 16:59:20 -07:00
}
}
},
feat(bazel): add an ng_package rule (#22221) This produces a directory following the Angular Package layout spec. Includes integration test coverage by making a minimal ng_package in integration/bazel. Unit tests verify the content of the @angular/core and @angular/common packages. This doesn't totally match our current output, but is good enough to unblock some early adopters. It re-uses logic from the rollup_bundle rule in rules_nodejs. It should also eventually have the .pack and .publish secondary targets like npm_package rule. PR Close #22221
2018-02-13 11:26:06 -08:00
"dependencies": {
fix(bazel): update API extractor version (#46259) `@angular/bazel` currently uses an older version of `@microsoft/api-extractor` which is causing downstream issues in Components. These changes bump up to a version that has a fix. Context: https://github.com/angular/components/pull/25027 PR Close #46259
2022-06-05 11:09:55 +02:00
"@microsoft/api-extractor": "^7.24.2",
build: update all non-major dependencies (#49267) See associated pull request for more information. PR Close #49267
2023-02-28 03:09:54 +00:00
"magic-string": "^0.30.0",
refactor: replace `fast-glob` usage with `tinyglobby` (#60264) Usage of the `fast-glob` package has been replaced with the `tinyglobby` package. The change reduces the number of transitive dependencies related to these packages from 17 to 2 while also maintaining equivalent functionality. This was also changed in the Angular CLI packages. PR Close #60264
2025-03-07 09:31:06 +00:00
"tinyglobby": "^0.2.12",
"tslib": "^2.3.0"
feat(bazel): add an ng_package rule (#22221) This produces a directory following the Angular Package layout spec. Includes integration test coverage by making a minimal ng_package in integration/bazel. Unit tests verify the content of the @angular/core and @angular/common packages. This doesn't totally match our current output, but is good enough to unblock some early adopters. It re-uses logic from the rollup_bundle rule in rules_nodejs. It should also eventually have the .pack and .publish secondary targets like npm_package rule. PR Close #22221
2018-02-13 11:26:06 -08:00
},
refactor(compiler-cli): move ngc-wrapped to packages/bazel (#18733) See design: https://goo.gl/rAeYWx PR Close #18733
2017-08-16 09:02:20 -07:00
"peerDependencies": {
"@angular/compiler-cli": "0.0.0-PLACEHOLDER",
build: migrate more usages from `@bazel/typescript` to `@bazel/concatjs` (#45431) As mentioned in previous commits (check them for more details), `@bazel/typescript` no longer contains `ts_library`-specific code, so we no longer need that dependency. PR Close #45431
2022-03-22 20:03:39 +01:00
"@bazel/concatjs": "^5.3.0",
fix(bazel): speed up `d.ts` bundling by configuring worker (#45900) Speeds up the `d.ts` bundling by configuring it as a Bazel persistent worker. Also improve logging for the ng packager rule to make it easier to spot which actions/bundles take up significant time. Type bundling will occur for every entry-point so for machines with rather limited cores/threads, this will be useful to save NodeJS boot and resolution time. PR Close #45900
2022-05-05 19:50:05 +00:00
"@bazel/worker": "^5.3.0",
build: update dependency @rollup/plugin-commonjs to v28 (#57929) See associated pull request for more information. PR Close #57929
2024-09-23 17:03:38 +00:00
"@rollup/plugin-commonjs": "^28.0.0",
feat(bazel): implement partial compilation APF v13 for `ng_package` rule (#43431) This commit implements partial compilation APF v13 for the `ng_package` rule. The changes involve the following things: 1. Requesting the partial compilation output for all targets (and its transitives) in the `deps` or `srcs` attributes. 2. Downleveling of ES2020 prodmode output to a FESM2015 file. 3. Cleanup of file resolution. Previusly, execroot file paths (which are passed to the packager tool) were composed manually. This is prone to mistakes and breaks with transitions. A lot of this code can be simplified by passing the necessary Bazel `File` information as JSON. This also simplifies the packager tool significantly (and makes it more readable..) 4. Remoal of UMD bundles. This also allows us remove the `globals` rule attribute with `externals` (we do not need any UMD global identifier names anymore). 5. The `package.json` will set the `exports` field and use subpath exports to make module resolution work for ESM consumers. 6. TSLib is also always set as `external` now. Previously it had to be added as `dep` to the `ng_package` rule as UMD files bundled `tslib`. 7. The `include_devmode_srcs` option has been removed. This option was an addition to APF that allowed the `@angular/compiler` to ship non-flattened ES5 CommonJS sources. We want to keep APF consistent and not allow such exceptions. Compiler is now a strict APF package as well, and the compiler-cli just needs to go through the primary entry-point for things it needs (or it bundles the necessary parts into the CLI.) Overall, these are all changes. A lot of changes to make the packager rule and tool more readable and Bazel-idiomatic were made as well. This allows us to easier make packaging changes in the future, and it's more future-proof if we ever change how inputs (like `ng_module` targets) are generated (e.g. consider a case where we'd use the `ts_project` rule). PR Close #43431
2021-09-28 00:51:31 +02:00
"@rollup/plugin-node-resolve": "^13.0.4",
feat(bazel): support bundling `.d.ts` with code splitting (#60321) Instead of relying on Microsoft's API extractor for `d.ts` bundling, we are switching to Rollup-based `.d.ts` bundling. This allows us to support code spliting, even for `.d.ts` files, allowing for relative imports to be used between entry-points, without ending up duplicating `.d.ts` definitions in two files. This would otherwise cause problems with assignability of types. It also nicely integrates into our existing rollup configuration, and overall simplifies the `ng_package` rule even further! Notably `tsup` also uses this rollup plugin, and it seems to work well. Keep in mind that Microsoft's API extractor is pretty hard to integrate, caused many problems in the past, and isn't capable of code splitting. This aligns our d.ts bundling with the .mjs bundling (great alignment). PR Close #60321
2025-03-11 13:06:34 +00:00
"rollup-plugin-dts": "^6.1.1",
feat(bazel): implement partial compilation APF v13 for `ng_package` rule (#43431) This commit implements partial compilation APF v13 for the `ng_package` rule. The changes involve the following things: 1. Requesting the partial compilation output for all targets (and its transitives) in the `deps` or `srcs` attributes. 2. Downleveling of ES2020 prodmode output to a FESM2015 file. 3. Cleanup of file resolution. Previusly, execroot file paths (which are passed to the packager tool) were composed manually. This is prone to mistakes and breaks with transitions. A lot of this code can be simplified by passing the necessary Bazel `File` information as JSON. This also simplifies the packager tool significantly (and makes it more readable..) 4. Remoal of UMD bundles. This also allows us remove the `globals` rule attribute with `externals` (we do not need any UMD global identifier names anymore). 5. The `package.json` will set the `exports` field and use subpath exports to make module resolution work for ESM consumers. 6. TSLib is also always set as `external` now. Previously it had to be added as `dep` to the `ng_package` rule as UMD files bundled `tslib`. 7. The `include_devmode_srcs` option has been removed. This option was an addition to APF that allowed the `@angular/compiler` to ship non-flattened ES5 CommonJS sources. We want to keep APF consistent and not allow such exceptions. Compiler is now a strict APF package as well, and the compiler-cli just needs to go through the primary entry-point for things it needs (or it bundles the necessary parts into the CLI.) Overall, these are all changes. A lot of changes to make the packager rule and tool more readable and Bazel-idiomatic were made as well. This allows us to easier make packaging changes in the future, and it's more future-proof if we ever change how inputs (like `ng_module` targets) are generated (e.g. consider a case where we'd use the `ts_project` rule). PR Close #43431
2021-09-28 00:51:31 +02:00
"rollup-plugin-sourcemaps": "^0.6.3",
feat(bazel): support bundling `.d.ts` with code splitting (#60321) Instead of relying on Microsoft's API extractor for `d.ts` bundling, we are switching to Rollup-based `.d.ts` bundling. This allows us to support code spliting, even for `.d.ts` files, allowing for relative imports to be used between entry-points, without ending up duplicating `.d.ts` definitions in two files. This would otherwise cause problems with assignability of types. It also nicely integrates into our existing rollup configuration, and overall simplifies the `ng_package` rule even further! Notably `tsup` also uses this rollup plugin, and it seems to work well. Keep in mind that Microsoft's API extractor is pretty hard to integrate, caused many problems in the past, and isn't capable of code splitting. This aligns our d.ts bundling with the .mjs bundling (great alignment). PR Close #60321
2025-03-11 13:06:34 +00:00
"rollup": "4.35.0",
feat(bazel): implement partial compilation APF v13 for `ng_package` rule (#43431) This commit implements partial compilation APF v13 for the `ng_package` rule. The changes involve the following things: 1. Requesting the partial compilation output for all targets (and its transitives) in the `deps` or `srcs` attributes. 2. Downleveling of ES2020 prodmode output to a FESM2015 file. 3. Cleanup of file resolution. Previusly, execroot file paths (which are passed to the packager tool) were composed manually. This is prone to mistakes and breaks with transitions. A lot of this code can be simplified by passing the necessary Bazel `File` information as JSON. This also simplifies the packager tool significantly (and makes it more readable..) 4. Remoal of UMD bundles. This also allows us remove the `globals` rule attribute with `externals` (we do not need any UMD global identifier names anymore). 5. The `package.json` will set the `exports` field and use subpath exports to make module resolution work for ESM consumers. 6. TSLib is also always set as `external` now. Previously it had to be added as `dep` to the `ng_package` rule as UMD files bundled `tslib`. 7. The `include_devmode_srcs` option has been removed. This option was an addition to APF that allowed the `@angular/compiler` to ship non-flattened ES5 CommonJS sources. We want to keep APF consistent and not allow such exceptions. Compiler is now a strict APF package as well, and the compiler-cli just needs to go through the primary entry-point for things it needs (or it bundles the necessary parts into the CLI.) Overall, these are all changes. A lot of changes to make the packager rule and tool more readable and Bazel-idiomatic were made as well. This allows us to easier make packaging changes in the future, and it's more future-proof if we ever change how inputs (like `ng_module` targets) are generated (e.g. consider a case where we'd use the `ts_project` rule). PR Close #43431
2021-09-28 00:51:31 +02:00
"terser": "^5.9.0",
feat(core): drop support for TypeScript older than 5.8 (#60197) Narrows down the versions of TypeScript we need to support. BREAKING CHANGE: * TypeScript versions less than 5.8 are no longer supported. PR Close #60197
2025-03-04 09:33:00 +01:00
"typescript": ">=5.8 <5.9"
refactor(compiler-cli): move ngc-wrapped to packages/bazel (#18733) See design: https://goo.gl/rAeYWx PR Close #18733
2017-08-16 09:02:20 -07:00
},
fix(bazel): add terser as an optional peer dependency (#33891) `ng_package` rule has an implicitly optional depedency on terser https://github.com/angular/angular/blob/a48573efe8eca12ccfbe0c11fb60f322387bf79a/packages/bazel/src/ng_package/ng_package.bzl#L36 When using this rule without terser being available we get the below error; ``` ERROR: /home/circleci/ng/modules/express-engine/BUILD.bazel:22:1: every rule of type ng_package implicitly depends upon the target '@npm//terser/bin:terser', but this target could not be found because of: no such package '@npm//terser/bin': BUILD file not found in directory 'terser/bin' of external repository @npm. Add a BUILD file to a directory to mark it as a package. ERROR: Analysis of target '//modules/express-engine:npm_package' failed; build aborted: no such package '@npm//terser/bin': BUILD file not found in directory 'terser/bin' of external repository @npm. Add a BUILD file to a directory to mark it as a package. ``` PR Close #33891
2019-11-18 10:06:12 +01:00
"peerDependenciesMeta": {
"terser": {
"optional": true
}
},
refactor(compiler-cli): move ngc-wrapped to packages/bazel (#18733) See design: https://goo.gl/rAeYWx PR Close #18733
2017-08-16 09:02:20 -07:00
"repository": {
"type": "git",
build(packaging): add repository.directory field to package.jsons (#27544) PR Close #27544
2018-12-07 12:12:59 +01:00
"url": "https://github.com/angular/angular.git",
"directory": "packages/bazel"
feat(bazel): change ng_package rule to APF v6 (#22782) Angular Package Format v6 stops bundling files in the esm5 and esm2015 directories, now that Webpack 4 can tree-shake per-file. Adds some missing files like package.json to make packages closer to what we publish today. Refactor ng_package to be a type of npm_package and re-use the packaging action from that rule. PR Close #22782
2018-03-13 11:00:53 -07:00
},
"ng-update": {
"packageGroup": "NG_UPDATE_PACKAGE_GROUP"
refactor(compiler-cli): move ngc-wrapped to packages/bazel (#18733) See design: https://goo.gl/rAeYWx PR Close #18733
2017-08-16 09:02:20 -07:00
}
feat(core): support TypeScript 4.6 (#45190) Adds support for TypeScript 4.6. PR Close #45190
2022-03-01 14:26:08 +01:00
}
Reference in New Issue Copy Permalink