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
b558d4e2c1782519c4b8a982cf47d0ec0ef1b510
angular__angular/packages/bazel/package.json
T

55 lines
1.4 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 version support range to support v16 (#43740) This commit updates the `node` engines range for all Angular framework packages to: * No longer support NodeJS v12 `< 12.20`. This is done because APF v13 uses package export patterns which are only supported as of v12.20. https://nodejs.org/api/packages.html#packages_subpath_patterns. * Allows for the latest v16 NodeJS versions. This matches with the CLI which added NodeJS v16 support with https://github.com/angular/angular-cli/pull/21854. We already limit this to `>= v16.10.0` in preparation to only supporting the LTS minors of Node v16. BREAKING CHANGE: NodeJS versions older than `v12.20.0` are no longer supported due to the Angular packages using the NodeJS package exports feature with subpath patterns. PR Close #43740
2021-10-06 18:25:26 +02:00
"node": "^12.20.0 || ^14.15.0 || >=16.10.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": {
fix(bazel): add missing binary path for api-extractor (#29202) `api-extractor` binary is required for external consumers of `ng_module` that want to use the `bundle_dts` flag. This also sets a different api-exttractor binary to use for ng_module, based if it's internal or external. PR Close #29202
2019-03-09 13:24:20 +01:00
"api-extractor": "./src/api-extractor/index.js",
build: idiomatic install of @angular/bazel npm package (#26258) (#26488) PR Close #26488
2018-10-16 13:20:00 -07:00
"ngc-wrapped": "./src/ngc-wrapped/index.js",
"packager": "./src/ng_package/packager.js",
refactor(bazel): remove unused `modify_tsconfig.js` file (#43431) Removes the unused `modify_tsconfig.js` file located in the `@angular/bazel` package. This file existed in the past for the ESM5 compilation aspect relying on the TS compilation to be replayed. We just forgot removing the file and associated `nodejs_binary`. PR Close #43431
2021-09-27 23:54:52 +02:00
"xi18n": "./src/ngc-wrapped/extract_i18n.js"
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": {
fix(bazel): ngc-wrapped should not rely on linker for external workspaces (#43690) Currently when `ngc-wrapped` runs in external/consumer workspaces, like in the Angular Components project, the `ngc-wrapped` binary relies on the linker due to the patched module resolution in `rules_nodejs` no longer being default. The reliance on the linker of `rules_nodejs` is problematic for workers as the required `node_modules` are not re-linked for every build. This was previously not an issue before the APF v13 changes because the `compiler-cli` module was loaded only once through an import statement. As of APF v13, the compiler-cli module is loaded dynamically for every build. This dynamic import can then break as the worker does not initially load the compiler-cli module when becoming online. Instead, the module is loaded on the first build where the node modules might not be linked properly anymore (due to e.g. other targets running at the same time). We fix thi issue by doing the following things: 1. Enabling the patched module resolution for consumer/external workspaces. This would match how we use ngc-wrapped inside FW as well. 2. Caching the compiler CLI module. Instead of re-fetching the module through dynamic imports for every build (in a worker), we should use the cached version. This is semantically the same as with APF v12 where a single import statement at file top-level was used. Technically, NodeJS should cache the module, but it doesn't hurt directly caching it as the module resolution will be patched by `rules_nodejs` and could perform unnecessary tasks. PR Close #43690
2021-10-03 13:08:43 +02:00
"configuration_env_vars": "[\"angular_ivy_enabled\"]",
"templated_args": "[\"--bazel_patch_module_resolver\"]"
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": {
build: update all non-major dependencies (#43974) PR Close #43974
2021-11-08 18:58:30 +00:00
"@microsoft/api-extractor": "7.18.19",
build: update shelljs to version 0.8.4 (#41673) PR Close #41673
2021-04-14 07:23:07 +00:00
"shelljs": "0.8.4",
fix(bazel): add missing dependency on `tslib` (#41480) `@angular/bazel` depends on `tslib` https://unpkg.com/browse/@angular/bazel@11.2.8/src/api-extractor/index.js#L20 Related failure https://github.com/angular/universal/pull/2040 PR Close #41480
2021-04-07 09:46:13 +02:00
"tsickle": "^0.38.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 20:50:59 +02:00
"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: update to rules nodejs 1.0.1 (#34736) This brings in a few minor fixes including a better way to patch require for bootstrap scripts Also remove install_source_map_support attribute from nodejs_binary targets This attribute will be removed from nodejs_binary in the future PR Close #34736
2020-01-02 19:05:47 -08:00
"@bazel/typescript": ">=1.0.0",
build: update dependency @rollup/plugin-commonjs to v21 (#43675) PR Close #43675
2021-10-02 05:14:37 +00:00
"@rollup/plugin-commonjs": "^21.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",
"rollup": "^2.56.3",
"rollup-plugin-sourcemaps": "^0.6.3",
"terser": "^5.9.0",
feat(core): drop support for TypeScript 4.2 and 4.3 (#43642) Bumps the minimum required TypeScript version to 4.4.2 and removes the integration tests for 4.1, 4.2 and 4.3. BREAKING CHANGE: TypeScript versions older than 4.4.2 are no longer supported. PR Close #43642
2021-10-02 14:51:04 +02:00
"typescript": ">=4.4.2 <4.5"
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
}
refactor(bazel): Remove schematics and builder from package.json (#37190) This commit removes the fields for ng-add, schematics and builder from package.json of `@angular/bazel`. PR Close #37190
2020-05-20 17:03:38 -07:00
}
Reference in New Issue Copy Permalink