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 1
angular/package.json

233 lines
10 KiB
JSON
Raw Normal View History

build - refactor
2014-09-18 21:56:38 +00:00
{
chore(package.json): remove typings bundles This was used for , but now that our typings are laid out in the node_module, users should no longer need that. Also fix the project name in root package.json. There is a risk that someone runs npm publish in this directory, which will create a new version of angular 1, and contain a scary source tree. So this package.json may as well have a name that doesn't exist on npm, and if we did publish by accident, it would be a package name that matches the contents.
2015-10-15 16:57:29 +00:00
"name": "angular-srcs",
release: cut the v15.1.0-next.3 release
2022-12-14 19:54:33 +00:00
"version": "15.1.0-next.3",
repackaging: all the repackaging changes squashed
2016-04-29 00:50:03 +00:00
"private": true,
docs: branding fixes (#14132) Angular 1.x -> AngularJS Angular 1 -> AngularJS Angular1 -> AngularJS Angular 2+ -> Angular Angular 2.0 -> Angular Angular2 -> Angular I have deliberately not touched any of the symbol names as that would cause big merge collisions with Tobias's work. All the renames are in .md, .json, and inline comments and jsdocs. PR Close #14132
2017-01-27 06:30:42 +00:00
"description": "Angular - a web framework for modern web apps",
feat(build): add npm publish script Also fixes gulpfile: - `runSequence` needs to be called with `done` callback - `es5build` should only run when the task executes…
2015-02-10 23:18:16 +00:00
"homepage": "https://github.com/angular/angular",
"bugs": "https://github.com/angular/angular/issues",
doc(*): change package.json license field to MIT Align the package.json license with the LICENSE file from the repo Closes #6432
2016-01-12 16:36:43 +00:00
"license": "MIT",
build: set upper version limit for yarn to <2 (#34236) Rather than bumping up the allowed version of yarn on each release we should instead just allow for anything within the major version 1 range. PR Close #34236
2019-12-04 20:05:53 +00:00
"//engines-comment": "Keep this in sync with /aio/package.json and /aio/tools/examples/shared/package.json",
chore(package.json): add range of supported node versions as engines Closes #5535
2015-12-01 22:09:31 +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",
build: rely on engines to prevent using npm for dependency install (#41477) Rather than relying on a preinstall script, set `engine-strict` to `true` in a project `.npmrc` file, relying on the `engines` having `npm` set to note that yarn should be used instead. --- Output from `npm install` changes from: ``` $ npm install > angular-srcs@12.0.0-next.7 preinstall /usr/local/account/js/angular > node tools/yarn/check-yarn.js /usr/local/account/js/angular/tools/yarn/check-yarn.js:12 throw new Error( ^ Error: Please use Yarn instead of NPM to install dependencies. See: https://yarnpkg.com/lang/en/docs/install/ at Object.<anonymous> (/usr/local/account/js/angular/tools/yarn/check-yarn.js:12:9) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Function.Module.runMain (internal/modules/cjs/loader.js:831:12) at startup (internal/bootstrap/node.js:283:19) at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! angular-srcs@12.0.0-next.7 preinstall: `node tools/yarn/check-yarn.js` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the angular-srcs@12.0.0-next.7 preinstall script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /usr/local/account/.npm/_logs/2021-04-06T22_54_02_292Z-debug.log ``` to ``` $ npm install npm ERR! code ENOTSUP npm ERR! notsup Unsupported engine for angular-srcs@12.0.0-next.7: wanted: {"node":">=10.19.0 <13.0.0","yarn":">=1.22.4 <2","npm":"Plesae use yarn instead of NPM to install dependencies"} (current: {"node":"10.20.1","npm":"6.14.4"}) npm ERR! notsup Not compatible with your version of node/npm: angular-srcs@12.0.0-next.7 npm ERR! notsup Not compatible with your version of node/npm: angular-srcs@12.0.0-next.7 npm ERR! notsup Required: {"node":">=10.19.0 <13.0.0","yarn":">=1.22.4 <2","npm":"Plesae use yarn instead of NPM to install dependencies"} npm ERR! notsup Actual: {"npm":"6.14.4","node":"10.20.1"} npm ERR! A complete log of this run can be found in: npm ERR! /usr/local/account/.npm/_logs/2021-04-06T22_53_23_912Z-debug.log ``` PR Close #41477
2021-04-06 22:51:45 +00:00
"yarn": ">=1.22.4 <2",
"npm": "Please use yarn instead of NPM to install dependencies"
chore(package.json): add range of supported node versions as engines Closes #5535
2015-12-01 22:09:31 +00:00
},
chore(package.json): npm No repository field. npm install yields a warning ```bash npm WARN package.json angular@0.0.0 No repository field. ``` also include `"bugs": "https://github.com/angular/angular/issues"`
2015-01-24 18:50:18 +00:00
"repository": {
"type": "git",
"url": "https://github.com/angular/angular.git"
},
build - refactor
2014-09-18 21:56:38 +00:00
"scripts": {
build: complete removal of bazel format yarn commands (#37148) Remove bazel yarn format deprecation message to complete the removal of formatting bazel related files via yarn command command. PR Close #37148
2020-05-15 23:01:38 +00:00
"/": "",
build: fix typo in package.json file comment (#45569) Change comment in scripts section of package.json PR Close #45569
2022-04-09 11:41:26 +00:00
"// 1": "Many of our checks/scripts/tools have moved to our ng-dev tool",
build: complete removal of bazel format yarn commands (#37148) Remove bazel yarn format deprecation message to complete the removal of formatting bazel related files via yarn command command. PR Close #37148
2020-05-15 23:01:38 +00:00
"// 2": "Find the usage you are looking for with:",
"// 3": "yarn ng-dev --help",
"/ ": "",
build: patch `ts_library` to not emit a tsickle extern file (#48521) The prodmode compilation pipeline -that we intend to use more heavily now given it emitting files with the `.mjs` extension- exposes an additional tsickle closure externs file. This file is empty most of the time anyway since tsickle is not wired up. We remove this generation as otherwise convenient `$(location` of such ts library targets break because there always is more than 1 file. PR Close #48521
2022-12-08 17:51:12 +00:00
"postinstall": "node scripts/webdriver-manager-update.js && node --preserve-symlinks --preserve-symlinks-main ./tools/postinstall-patches.js && patch-package --patch-dir tools/esm-interop/patches/npm",
build: install husky in `prepare` script instead of `postinstall` (#41405) With typicode/husky#890, the recommended way to install husky is in the `prepare` script instead of the `postinstall`. This commit moves the husky installation to the `prepare` script to align with the new recommendation. PR Close #41405
2021-04-02 23:13:10 +00:00
"prepare": "husky install",
build: update dev-infra packages and account for build-tooling split from `ng-dev` (#46976) The dev-infra build tooling is now decoupled from `ng-dev`. This will make it easier to update `ng-dev` without necessarily needing to upgrade the whole build system, Bazel etc. This is useful when e.g. new release tool features have been added and should also be ported to active LTS branches. PR Close #46976
2022-07-27 08:03:49 +00:00
"ng-dev": "cross-env TS_NODE_PROJECT=$PWD/.ng-dev/tsconfig.json TS_NODE_TRANSPILE_ONLY=1 node --no-warnings --loader ts-node/esm node_modules/@angular/ng-dev/bundles/cli.mjs",
build: convert release package build scripts to typescript (#46456) Follow-up to: cce395a928bdcd85fe1b24c5887c2ca587b659a2. PR Close #46456
2022-06-22 16:13:15 +00:00
"build": "ts-node --esm --project scripts/tsconfig.json scripts/build/build-packages-dist.mts",
test: remove view-engine-only tests (#43884) This commit removes most tests that were designated as only covering View Engine code. It also removes tag filters from CI and local commands to run tests. In a few cases (such as with the packages/compiler tests), this tag was improperly applied, and certain test cases have been added back running in Ivy mode. This commit also empties `@angular/compiler/testing` as it is no longer necessary (this is safe since compiler packages are not public API). It can be deleted in the future. PR Close #43884
2021-11-09 18:59:21 +00:00
"test": "bazelisk test",
build(bazel): add bazel build and test targets for aio build (#45022) First step towards a migration of aio to bazel. Not yet built by ci. PR Close #45022
2022-01-13 23:43:39 +00:00
"test:ci": "bazelisk test -- //... -//devtools/... -//aio/...",
build: Turn tsec checks into bazel tests. (#43108) Introduce two new bazel rules: tsec_test and tsec_config, for describing the tsec checks and the tsconfig file needed for such checks, respectively. Currently, tsec_test only checks the srcs of a ts_library or ng_module. It does not check direct or transitive dependencies. Also, tsconfig files need to be manually maintained to make sure tsec can read all necessary input (including global symbols). PR Close #43108
2021-08-13 04:50:34 +00:00
"test-tsec": "bazelisk test //... --build_tag_filters=tsec --test_tag_filters=tsec",
build: migrate from gulp to ng-dev for running formatting (#36726) Migrates away from gulp to ng-dev for running our formatter. Additionally, provides a deprecation warning for any attempted usage of the previous `gulp format:*` tasks. PR Close #36726
2020-04-20 20:04:08 +00:00
"lint": "yarn -s tslint && yarn -s ng-dev format changed --check",
feat(dev-infra): add lint rule to enforce no-implicit-override abstract members (#42512) TypeScript introduced a new flag called `noImplicitOverride` as part of TypeScript v4.3. This flag introduces a new keyword called `override` that can be applied to members which override declarations from a base class. This helps with code health as TS will report an error if e.g. the base class changes the method name but the override would still have the old method name. Similarly, if the base class removes the method completely, TS would complain that the memeber with `override` no longer overrides any method. A similar concept applies to abstract methods, with the exception that TypeScript's builtin `noImplicitOverride` option does not flag members which are implemented as part of an abstract class. We want to enforce this as a best-practice in the repository as adding `override` to such implemented members will cause TS to complain if an abstract member is removed, but still implemented by derived classes. More details: https://github.com/microsoft/TypeScript/issues/44457. PR Close #42512
2021-07-06 17:41:48 +00:00
"tslint": "tslint -c tslint.json --project tsconfig-tslint.json",
ci: move public-api goldens to goldens directory (#35768) Moves the public api .d.ts files from tools/public_api_guard to goldens/public-api. Additionally, provides a README in the goldens directory and a script assist in testing the current state of the repo against the goldens as well as a command for accepting all changes to the goldens in a single command. PR Close #35768
2020-02-26 17:09:35 +00:00
"public-api:check": "node goldens/public-api/manage.js test",
build: create tool for validating typescript circular dependencies (#35647) Creates a tool for validating TypeScript circular dependencies. The tool has been designed in a way that allows us to slowly burn down the amount of circular dependencies while ensuring that we don't regress. The tool doesn't rely on Madge since it doesn't provide a programmatic way for doing path mapping. We need path mapping since we also want to check for cycles across different entry-points or packages. The tool uses the TypeScript AST to manually collect cycles. This code is not a lot of bloat and also gives us more flexibility (if we ever need it). Closes #35041. PR Close #35647
2020-02-24 11:03:15 +00:00
"public-api:update": "node goldens/public-api/manage.js accept",
build: create temporary script for symbol extractor tests (#38819) Creates a temporary script to running all symbol extractor tests. PR Close #38819
2020-09-11 21:54:53 +00:00
"symbol-extractor:check": "node tools/symbol-extractor/run_all_symbols_extractor_tests.js test",
"symbol-extractor:update": "node tools/symbol-extractor/run_all_symbols_extractor_tests.js accept",
refactor(dev-infra): create ng-dev executable locally in the repo (#39089) Rather than running ng-dev via ts-node, going forward ng-dev is generated and run locally via node. Additionally, the generated file is tested on each commit to ensure that the local generated version stays up to date. PR Close #39089
2020-10-01 23:06:56 +00:00
"ts-circular-deps:check": "yarn -s ng-dev ts-circular-deps check --config ./packages/circular-deps-test.conf.js",
build: check .ng-dev tool configuration in CI (#43322) Checks the `.ng-dev` tool configuration in CI, compared to doing it locally when the caretaker intends to perform a merge and then realizes the config is broken. PR Close #43322
2021-09-02 14:29:47 +00:00
"ts-circular-deps:approve": "yarn -s ng-dev ts-circular-deps approve --config ./packages/circular-deps-test.conf.js",
build: convert release package build scripts to typescript (#46456) Follow-up to: cce395a928bdcd85fe1b24c5887c2ca587b659a2. PR Close #46456
2022-06-22 16:13:15 +00:00
"check-tooling-setup": "yarn tsc --project .ng-dev/tsconfig.json && yarn tsc --project scripts/tsconfig.json",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"devtools:devserver": "ibazel run //devtools/src:devserver",
build: convert release package build scripts to typescript (#46456) Follow-up to: cce395a928bdcd85fe1b24c5887c2ca587b659a2. PR Close #46456
2022-06-22 16:13:15 +00:00
"devtools:build:chrome": "bazelisk build --config snapshot-build --//devtools/projects/shell-browser/src:flag_browser=chrome -- devtools/projects/shell-browser/src:prodapp",
"devtools:build:firefox": "bazelisk build --config snapshot-build --//devtools/projects/shell-browser/src:flag_browser=firefox -- devtools/projects/shell-browser/src:prodapp",
"devtools:test": "bazelisk test --config snapshot-build --//devtools/projects/shell-browser/src:flag_browser=chrome -- //devtools/..."
build - refactor
2014-09-18 21:56:38 +00:00
},
build: Move non-bazel deps to devDependencies (#26691) This makes yarn_install of ngdeps under Bazel faster, since we don't need many of the large dependencies. It's important because downstream angular/bazel users will observe the same install time. PR Close #26691
2018-10-22 21:26:52 +00:00
"// 1": "dependencies are used locally and by bazel",
build - refactor
2014-09-18 21:56:38 +00:00
"dependencies": {
build: update cross-repo angular dependencies (#48409) See associated pull request for more information. Closes: #48339 (cherry picked from commit 31742210a38b3e01e25cfa9c4e13f6f0e13bf1dd) PR Close #48409
2022-12-09 08:26:05 +00:00
"@angular-devkit/build-angular": "15.1.0-next.2",
build: update cross-repo angular dependencies (#46642) | datasource | package | from | to | | ---------- | --------------------------------- | -------- | --------------- | | npm | @angular-devkit/architect-cli | 0.1400.0 | 0.1401.0-next.3 | | npm | @angular-devkit/build-angular | 13.3.6 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.0 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.0 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.4 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.4 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.4 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.4 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.4 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.4 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.4 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.4 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.4 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.4 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.4 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.4 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.0 | 14.1.0-next.3 | | npm | @angular-devkit/build-angular | 14.0.0 | 14.1.0-next.3 | | npm | @angular-devkit/build-optimizer | 0.1302.1 | 0.1302.0-rc.1 | | npm | @angular-devkit/core | 13.3.6 | 14.1.0-next.3 | | npm | @angular-devkit/schematics | 13.3.6 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.0 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.0 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.4 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.4 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.4 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.4 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.4 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.4 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.4 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.4 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.4 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.4 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.4 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.4 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.4 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.4 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.0 | 14.1.0-next.3 | | npm | @angular/animations | 14.0.0 | 14.1.0-next.3 | | npm | @angular/cdk | 13.3.7 | 14.1.0-next.3 | | npm | @angular/cdk | 14.0.0 | 14.1.0-next.3 | | npm | @angular/cdk | 14.0.0 | 14.1.0-next.3 | | npm | @angular/cli | 13.3.6 | 14.1.0-next.3 | | npm | @angular/common | 14.0.0 | 14.1.0-next.3 | | npm | @angular/common | 14.0.0 | 14.1.0-next.3 | | npm | @angular/common | 14.0.4 | 14.1.0-next.3 | | npm | @angular/common | 14.0.4 | 14.1.0-next.3 | | npm | @angular/common | 14.0.4 | 14.1.0-next.3 | | npm | @angular/common | 14.0.4 | 14.1.0-next.3 | | npm | @angular/common | 14.0.4 | 14.1.0-next.3 | | npm | @angular/common | 14.0.4 | 14.1.0-next.3 | | npm | @angular/common | 14.0.4 | 14.1.0-next.3 | | npm | @angular/common | 14.0.4 | 14.1.0-next.3 | | npm | @angular/common | 14.0.4 | 14.1.0-next.3 | | npm | @angular/common | 14.0.4 | 14.1.0-next.3 | | npm | @angular/common | 14.0.4 | 14.1.0-next.3 | | npm | @angular/common | 14.0.4 | 14.1.0-next.3 | | npm | @angular/common | 14.0.4 | 14.1.0-next.3 | | npm | @angular/common | 14.0.4 | 14.1.0-next.3 | | npm | @angular/common | 14.0.0 | 14.1.0-next.3 | | npm | @angular/common | 14.0.0 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.0 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.0 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.0 | 14.1.0-next.3 | | npm | @angular/compiler | 14.0.0 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.0 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.0 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.4 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.0 | 14.1.0-next.3 | | npm | @angular/compiler-cli | 14.0.0 | 14.1.0-next.3 | | npm | @angular/core | 14.0.0 | 14.1.0-next.3 | | npm | @angular/core | 14.0.0 | 14.1.0-next.3 | | npm | @angular/core | 14.0.4 | 14.1.0-next.3 | | npm | @angular/core | 14.0.4 | 14.1.0-next.3 | | npm | @angular/core | 14.0.4 | 14.1.0-next.3 | | npm | @angular/core | 14.0.4 | 14.1.0-next.3 | | npm | @angular/core | 14.0.4 | 14.1.0-next.3 | | npm | @angular/core | 14.0.4 | 14.1.0-next.3 | | npm | @angular/core | 14.0.4 | 14.1.0-next.3 | | npm | @angular/core | 14.0.4 | 14.1.0-next.3 | | npm | @angular/core | 14.0.4 | 14.1.0-next.3 | | npm | @angular/core | 14.0.4 | 14.1.0-next.3 | | npm | @angular/core | 14.0.4 | 14.1.0-next.3 | | npm | @angular/core | 14.0.4 | 14.1.0-next.3 | | npm | @angular/core | 14.0.4 | 14.1.0-next.3 | | npm | @angular/core | 14.0.4 | 14.1.0-next.3 | | npm | @angular/core | 14.0.0 | 14.1.0-next.3 | | npm | @angular/core | 14.0.0 | 14.1.0-next.3 | | npm | @angular/elements | 14.0.0 | 14.1.0-next.3 | | npm | @angular/elements | 14.0.0 | 14.1.0-next.3 | | npm | @angular/elements | 14.0.4 | 14.1.0-next.3 | | npm | @angular/elements | 14.0.4 | 14.1.0-next.3 | | npm | @angular/elements | 14.0.0 | 14.1.0-next.3 | | npm | @angular/elements | 14.0.0 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.0 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.0 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.4 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.4 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.4 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.4 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.4 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.4 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.4 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.4 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.4 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.4 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.4 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.4 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.4 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.4 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.0 | 14.1.0-next.3 | | npm | @angular/forms | 14.0.0 | 14.1.0-next.3 | | npm | @angular/localize | 14.0.0 | 14.1.0-next.3 | | npm | @angular/localize | 14.0.0 | 14.1.0-next.3 | | npm | @angular/localize | 14.0.4 | 14.1.0-next.3 | | npm | @angular/localize | 14.0.4 | 14.1.0-next.3 | | npm | @angular/material | 13.3.7 | 14.1.0-next.3 | | npm | @angular/material | 14.0.0 | 14.1.0-next.3 | | npm | @angular/material | 14.0.0 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.0 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.0 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.0 | 14.1.0-next.3 | | npm | @angular/platform-browser | 14.0.0 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.0 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.0 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.0 | 14.1.0-next.3 | | npm | @angular/platform-browser-dynamic | 14.0.0 | 14.1.0-next.3 | | npm | @angular/platform-server | 14.0.0 | 14.1.0-next.3 | | npm | @angular/platform-server | 14.0.0 | 14.1.0-next.3 | | npm | @angular/platform-server | 14.0.4 | 14.1.0-next.3 | | npm | @angular/platform-server | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.0 | 14.1.0-next.3 | | npm | @angular/router | 14.0.0 | 14.1.0-next.3 | | npm | @angular/router | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.4 | 14.1.0-next.3 | | npm | @angular/router | 14.0.0 | 14.1.0-next.3 | | npm | @angular/router | 14.0.0 | 14.1.0-next.3 | | npm | @angular/service-worker | 14.0.0 | 14.1.0-next.3 | | npm | @angular/service-worker | 14.0.0 | 14.1.0-next.3 | | npm | @angular/service-worker | 14.0.4 | 14.1.0-next.3 | | npm | @angular/service-worker | 14.0.4 | 14.1.0-next.3 | | npm | @angular/service-worker | 14.0.0 | 14.1.0-next.3 | | npm | @angular/service-worker | 14.0.0 | 14.1.0-next.3 | | npm | @angular/upgrade | 14.0.0 | 14.1.0-next.3 | | npm | @angular/upgrade | 14.0.0 | 14.1.0-next.3 | | npm | @angular/upgrade | 14.0.4 | 14.1.0-next.3 | | npm | @angular/upgrade | 14.0.4 | 14.1.0-next.3 | | npm | @schematics/angular | 13.3.6 | 14.1.0-next.3 | PR Close #46642
2022-06-30 12:47:56 +00:00
"@angular-devkit/build-optimizer": "0.1302.0-rc.1",
build: update cross-repo angular dependencies (#48409) See associated pull request for more information. Closes: #48339 (cherry picked from commit 31742210a38b3e01e25cfa9c4e13f6f0e13bf1dd) PR Close #48409
2022-12-09 08:26:05 +00:00
"@angular-devkit/core": "15.1.0-next.2",
"@angular-devkit/schematics": "15.1.0-next.2",
build: update angular (#44024) PR Close #44024
2021-11-03 21:17:22 +00:00
"@angular/animations-12": "npm:@angular/animations@12.2.13",
build: update cross-repo angular dependencies (#48409) See associated pull request for more information. Closes: #48339 (cherry picked from commit 31742210a38b3e01e25cfa9c4e13f6f0e13bf1dd) PR Close #48409
2022-12-09 08:26:05 +00:00
"@angular/cdk": "15.1.0-next.1",
"@angular/cli": "15.1.0-next.2",
build: update angular (#44024) PR Close #44024
2021-11-03 21:17:22 +00:00
"@angular/common-12": "npm:@angular/common@12.2.13",
"@angular/core-12": "npm:@angular/core@12.2.13",
"@angular/forms-12": "npm:@angular/forms@12.2.13",
build: update cross-repo angular dependencies (#48409) See associated pull request for more information. Closes: #48339 (cherry picked from commit 31742210a38b3e01e25cfa9c4e13f6f0e13bf1dd) PR Close #48409
2022-12-09 08:26:05 +00:00
"@angular/material": "15.1.0-next.1",
build: update angular (#44024) PR Close #44024
2021-11-03 21:17:22 +00:00
"@angular/platform-browser-12": "npm:@angular/platform-browser@12.2.13",
"@angular/platform-browser-dynamic-12": "npm:@angular/platform-browser-dynamic@12.2.13",
"@angular/platform-server-12": "npm:@angular/platform-server@12.2.13",
"@angular/router-12": "npm:@angular/router@12.2.13",
build: update babel dependencies (#47765) See associated pull request for more information. PR Close #47765
2022-10-13 19:39:34 +00:00
"@babel/cli": "7.19.3",
"@babel/core": "7.19.3",
"@babel/generator": "7.19.5",
"@babel/parser": "7.19.4",
"@babel/preset-env": "7.19.4",
"@babel/template": "7.18.10",
"@babel/traverse": "7.19.4",
"@babel/types": "7.19.4",
build: update bazel setup to v5.7.1 (#47884) See associated pull request for more information. PR Close #47884
2022-11-22 21:02:53 +00:00
"@bazel/concatjs": "5.7.1",
"@bazel/esbuild": "5.7.1",
"@bazel/jasmine": "5.7.1",
"@bazel/protractor": "5.7.1",
"@bazel/rollup": "5.7.1",
"@bazel/runfiles": "5.7.1",
"@bazel/terser": "5.7.1",
"@bazel/worker": "5.7.1",
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",
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 09:09:55 +00:00
"@microsoft/api-extractor": "^7.24.2",
build: update dependency @rollup/plugin-babel to v6 (#47701) See associated pull request for more information. PR Close #47701
2022-10-08 04:45:06 +00:00
"@rollup/plugin-babel": "^6.0.0",
build: update dependency @rollup/plugin-commonjs to v23 (#47711) See associated pull request for more information. PR Close #47711
2022-10-10 16:44:25 +00:00
"@rollup/plugin-commonjs": "^23.0.0",
build: update bazel setup to latest dev-infra package and rules_nodejs v4.2.0 (#43431) Updates the Bazel setup to the latest shared dev-infra package. Also the rules_nodejs version is updated to v4.2.0. We have landed various changes that prepare us for the APF v13 implementation. e.g. * Ability to control the linker mappings for the `ng_package` rule. This will become important for using a transition that could accidentally cause linker mappings that would otheriwse conflict. * Use of latest version of rollup & terser in the Bazel rules the dev-infra package exposes. This is necessary for ES2020 support. PR Close #43431
2021-09-27 21:41:51 +00:00
"@rollup/plugin-node-resolve": "^13.0.4",
build: update cross-repo angular dependencies (#48409) See associated pull request for more information. Closes: #48339 (cherry picked from commit 31742210a38b3e01e25cfa9c4e13f6f0e13bf1dd) PR Close #48409
2022-12-09 08:26:05 +00:00
"@schematics/angular": "15.1.0-next.2",
build: switch example e2e tests to bazel (#28402) * No longer builds the example e2e tests using "tsc". The examples are now built with Bazel and can therefore be built with Ivy by using the `--define=compile=aot` switch. * No longer runs the example e2e tests using the protractor CLI. example e2e tests are executed with the Bazel protractor rule and can therefore run incrementally. NOTE: Unit tests found within the examples are still running within the legacy jobs. PR Close #28402
2019-01-28 20:59:25 +00:00
"@types/angular": "^1.6.47",
build: update all non-major dependencies (#48271) See associated pull request for more information. PR Close #48271
2022-11-30 08:02:44 +00:00
"@types/babel__core": "7.1.20",
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
"@types/babel__generator": "7.6.4",
"@types/babel__template": "7.4.1",
build: update all non-major dependencies (#48271) See associated pull request for more information. PR Close #48271
2022-11-30 08:02:44 +00:00
"@types/babel__traverse": "7.18.3",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"@types/base64-js": "1.3.0",
build: move zone.js to angular repo (#30962) PR Close #30962
2019-05-31 15:56:07 +00:00
"@types/bluebird": "^3.5.27",
build: update all non-major dependencies (#48271) See associated pull request for more information. PR Close #48271
2022-11-30 08:02:44 +00:00
"@types/chrome": "^0.0.203",
build: add dependencies to be used by ngcc (#24897) PR Close #24897
2018-07-16 06:08:48 +00:00
"@types/convert-source-map": "^1.5.1",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"@types/diff": "^5.0.0",
refactor(dev-infra): use conventional-commits-parser for commit parsing (#41286) Use conventional-commits-parser for parsing commits for validation, this is being done in anticipation of relying on this parser for release note creation. Unifying how commits are parsed will provide the most consistency in our tooling. PR Close #41286
2021-03-19 19:11:21 +00:00
"@types/events": "3.0.0",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"@types/filesystem": "^0.0.32",
build: avoid use of `ts-node` wrapper script as it breaks child process forking (#46456) `ts-node` spawns a custom node launcher script and has a brotli-base64 encoded configuration that will point to the user-provided entry-point. This breaks child process forking as we wouldn't be able to specify our custom build worker and basically `ng-dev` would run inside `ng-dev` again. PR Close #46456
2022-06-22 20:41:12 +00:00
"@types/hammerjs": "2.0.41",
build: update to jasmine 4.0 (#45558) Updates us to version 4.0 of Jasmine and fixes some errors that were the result of us depending upon deprecated APIs. We need to do this both to stay up to date and because it was going to break eventually, because one of the Bazel packages was logging a deprecation warning that version 4.0 was required. There were also some cases where the state of `ngDevMode` had started leaking out between tests. PR Close #45558
2022-04-08 19:37:30 +00:00
"@types/jasmine": "^4.0.0",
build: import in-memory-web-api project (#37182) Moves the `angular-in-memory-web-api` project into the main repository in order to make it easier to maintain and release. PR Close #37182
2020-06-12 16:25:08 +00:00
"@types/jasmine-ajax": "^3.3.1",
build: update jasmine to 3.5 (#34625) 1. update jasmine to 3.5 2. update @types/jasmine to 3.5 3. update @types/jasminewd2 to 2.0.8 Also fix several cases, the new jasmine 3 will help to create test cases correctly, such as in the `jasmine 2.x` version, the following case will pass ``` expect(1 == 2); ``` But in jsamine 3, the case will need to be ``` expect(1 == 2).toBeTrue(); ``` PR Close #34625
2020-01-03 05:28:06 +00:00
"@types/jasminewd2": "^2.0.8",
feat(dev-infra): check services/status information of the repository for caretaker (#38601) The angular team relies on a number of services for hosting code, running CI, etc. This tool allows for checking the operational status of all services at once as well as the current state of the repository with respect to merge and triage ready issues and prs. PR Close #38601
2020-08-26 20:49:43 +00:00
"@types/multimatch": "^4.0.0",
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
"@types/node": "^16.11.7",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"@types/resize-observer-browser": "^0.1.5",
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 17:51:03 +00:00
"@types/selenium-webdriver": "3.0.7",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"@types/semver": "^7.3.4",
build: fix build scripts on macOS (#33854) In #33823, `scripts/package-builds.sh` (which is used by both `build-packages-dist.sh` and `build-ivy-npm-packages.sh`) was updated to use `realpath`. It turns out that `realpath` does not exist on macOS, so the build scripts do not work there. In order to fix this (and also reduce the likelihood of introducing similar issues in the future), this commit changes these bash scripts to Node.js scripts (using [ShellJS](https://github.com/shelljs/shelljs) for a cross-platform implementation of Unix shell commands where necessary). PR Close #33854
2019-11-15 00:56:55 +00:00
"@types/shelljs": "^0.8.6",
build: move zone.js to angular repo (#30962) PR Close #30962
2019-05-31 15:56:07 +00:00
"@types/systemjs": "0.19.32",
build: update dependency @types/uuid to v9 (#48285) See associated pull request for more information. PR Close #48285
2022-11-29 18:36:17 +00:00
"@types/uuid": "^9.0.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
"@types/yargs": "^17.0.3",
build: fix elements test failures on IE (#35940) Fixes the following issues which caused the `elements` unit tests to break on IE: 1. `core.js` wasn't included which caused an error about `Promise` and `Symbol` to be thrown. 2. We were using a version of `@webcomponents/custom-elements` which was shipping ES6 code to npm. As a result, IE was throwing a syntax error. PR Close #35940
2020-03-08 15:52:17 +00:00
"@webcomponents/custom-elements": "^1.1.0",
test(upgrade): run tests against multiple AngularJS versions (#22167) Fixes #19332 PR Close #22167
2018-02-15 17:21:18 +00:00
"angular-1.5": "npm:angular@1.5",
test(upgrade): run tests against AngularJS v1.7.x as well (#25231) PR Close #25231
2018-07-31 12:10:13 +00:00
"angular-1.6": "npm:angular@1.6",
test(upgrade): run tests against AngularJS v1.8.x as well (#39972) We intend to run the `@angular/upgrade` tests against all supported versions of AngularJS (v1.5+). Previously, we only ran them against v1.5, v1.6 and v1.7. Since AngularJS v1.8 was released recently, this commit adds it to the list of AngularJS versions we test against. PR Close #39972
2020-12-04 14:53:12 +00:00
"angular-1.7": "npm:angular@1.7",
fix(dev-infra): `ng_rollup_bundle` rule should error if import cannot be resolved (#42760) Rollup just prints a warning if an import cannot be resolved and ends up being treated as an external dependency. This in combination with the `silent = True` attribute for `rollup_bundle` means that bundles might end up being extremely small without people noticing that it misses actual imports. To improve this situation, the warning is replaced by an error if an import cannot be resolved. This unveiles an issue with the `ng_rollup_bundle` macro from dev-infra where imports in View Engine were not resolved but ended up being treated as external. This did not prevent benchmarks using this macro from working because the ConcatJS devserver had builtin resolution for workspace manifest paths. Though given the new check for no unresolved imports, this will now cause errors within Rollup, and we need to fix the resolution. We can fix the issue by temporarily enabling workspace linking. This does not have any performance downsides. To enable workspace linking (which we might need more often in the future given the linker taking over patched module resolution), we had to rename the `angular` dependency to a more specific one so that the Angular linker could link into `node_modules/angular`. PR Close #42760
2021-07-06 13:29:19 +00:00
"angular-1.8": "npm:angular@1.8",
test(upgrade): run tests against multiple AngularJS versions (#22167) Fixes #19332 PR Close #22167
2018-02-15 17:21:18 +00:00
"angular-mocks-1.5": "npm:angular-mocks@1.5",
test(upgrade): run tests against AngularJS v1.7.x as well (#25231) PR Close #25231
2018-07-31 12:10:13 +00:00
"angular-mocks-1.6": "npm:angular-mocks@1.6",
test(upgrade): run tests against AngularJS v1.8.x as well (#39972) We intend to run the `@angular/upgrade` tests against all supported versions of AngularJS (v1.5+). Previously, we only ran them against v1.5, v1.6 and v1.7. Since AngularJS v1.8 was released recently, this commit adds it to the list of AngularJS versions we test against. PR Close #39972
2020-12-04 14:53:12 +00:00
"angular-mocks-1.7": "npm:angular-mocks@1.7",
fix(dev-infra): `ng_rollup_bundle` rule should error if import cannot be resolved (#42760) Rollup just prints a warning if an import cannot be resolved and ends up being treated as an external dependency. This in combination with the `silent = True` attribute for `rollup_bundle` means that bundles might end up being extremely small without people noticing that it misses actual imports. To improve this situation, the warning is replaced by an error if an import cannot be resolved. This unveiles an issue with the `ng_rollup_bundle` macro from dev-infra where imports in View Engine were not resolved but ended up being treated as external. This did not prevent benchmarks using this macro from working because the ConcatJS devserver had builtin resolution for workspace manifest paths. Though given the new check for no unresolved imports, this will now cause errors within Rollup, and we need to fix the resolution. We can fix the issue by temporarily enabling workspace linking. This does not have any performance downsides. To enable workspace linking (which we might need more often in the future given the linker taking over patched module resolution), we had to rename the `angular` dependency to a more specific one so that the Angular linker could link into `node_modules/angular`. PR Close #42760
2021-07-06 13:29:19 +00:00
"angular-mocks-1.8": "npm:angular-mocks@1.8",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"base64-js": "1.5.1",
build: Update dependencies (#40726) Updates some dependencies. PR Close #40726
2021-02-05 18:13:21 +00:00
"bluebird": "^3.7.2",
build: Remove cc_binary dependency on brotli (#29912) Just use the JavaScript port instead. We don't care about speed since we compress once as a build step. PR Close #29912
2019-04-15 18:57:36 +00:00
"brotli": "^1.3.2",
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: update `chalk` to version 4.0.1 (#41738) Update `chalk` to `4.0.1` so that it can be managed by Renovate. PR Close #41738
2021-04-21 06:38:13 +00:00
"chalk": "^4.1.0",
build: Update dependencies (#40726) Updates some dependencies. PR Close #40726
2021-02-05 18:13:21 +00:00
"chokidar": "^3.5.1",
build: Move non-bazel deps to devDependencies (#26691) This makes yarn_install of ngdeps under Bazel faster, since we don't need many of the large dependencies. It's important because downstream angular/bazel users will observe the same install time. PR Close #26691
2018-10-22 21:26:52 +00:00
"convert-source-map": "^1.5.1",
build: remove `core-js` in favor of `core-js-bundle` (#41739) `core-js` is a CJS package which cannot be used directly in the browser. `core-js-bundle` is the bundled version of the package which can be used in directly in the browser. PR Close #41739
2021-04-21 08:13:34 +00:00
"core-js-bundle": "^3.10.2",
build: update dependency d3 to v7 (#44892) PR Close #44892
2022-01-29 12:01:59 +00:00
"d3": "^7.0.0",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"dependency-graph": "^0.11.0",
"diff": "^5.0.0",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"document-register-element": "^1.7.2",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"domino": "~2.1.6",
build: update all non-major dependencies (#48271) See associated pull request for more information. PR Close #48271
2022-11-30 08:02:44 +00:00
"google-closure-compiler": "20221102.0.1",
build: update all non-major dependencies (#45470) Updates all non-major dependencies, including Bazel PR Close #45470
2022-04-09 20:42:17 +00:00
"graceful-fs": "4.2.10",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"hammerjs": "~2.0.8",
build: update dependency http-server to v14 (#43900) PR Close #43900
2021-10-20 12:18:46 +00:00
"http-server": "^14.0.0",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"incremental-dom": "0.7.0",
build: update to jasmine 4.0 (#45558) Updates us to version 4.0 of Jasmine and fixes some errors that were the result of us depending upon deprecated APIs. We need to do this both to stay up to date and because it was going to break eventually, because one of the Bazel packages was logging a deprecation warning that version 4.0 was required. There were also some cases where the state of `ngDevMode` had started leaking out between tests. PR Close #45558
2022-04-08 19:37:30 +00:00
"jasmine": "^4.0.0",
build: import in-memory-web-api project (#37182) Moves the `angular-in-memory-web-api` project into the main repository in order to make it easier to maintain and release. PR Close #37182
2020-06-12 16:25:08 +00:00
"jasmine-ajax": "^4.0.0",
build: update to jasmine 4.0 (#45558) Updates us to version 4.0 of Jasmine and fixes some errors that were the result of us depending upon deprecated APIs. We need to do this both to stay up to date and because it was going to break eventually, because one of the Bazel packages was logging a deprecation warning that version 4.0 was required. There were also some cases where the state of `ngDevMode` had started leaking out between tests. PR Close #45558
2022-04-08 19:37:30 +00:00
"jasmine-core": "^4.0.0",
build: update all non-major dependencies (#47225) See associated pull request for more information. PR Close #47225
2022-09-01 12:44:30 +00:00
"jquery": "3.6.1",
feat(compiler-cli): report error if undecorated class with Angular features is discovered (#36921) Previously in v9, we deprecated the pattern of undecorated base classes that rely on Angular features. We ran a migration for this in version 9 and will run the same on in version 10 again. To ensure that projects do not regress and start using the unsupported pattern again, we report an error in ngtsc if such undecorated classes are discovered. We keep the compatibility code enabled in ngcc so that libraries can be still be consumed, even if they have not been migrated yet. Resolves FW-2130. PR Close #36921
2020-05-04 19:20:00 +00:00
"js-levenshtein": "^1.1.6",
build: update all non-major dependencies (#46707) See associated pull request for more information. PR Close #46707
2022-08-05 17:09:37 +00:00
"karma": "~6.4.0",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"karma-chrome-launcher": "^3.1.0",
"karma-firefox-launcher": "^2.1.0",
build: update dependency karma-jasmine to v5 | datasource | package | from | to | | ---------- | ------------- | ----- | ----- | | npm | karma-jasmine | 4.0.2 | 5.1.0 |
2022-06-29 17:49:08 +00:00
"karma-jasmine": "^5.0.0",
build: update to nodejs rules 0.41.0 (#33996) This bring is changes to the @nodejs repository required for https://github.com/angular/angular/pull/33927. See release notes for more details: https://github.com/bazelbuild/rules_nodejs/releases/tag/0.41.0. rules_nodejs is approaching 1.0 and breaking changes for that release are being made more frequently. In this release, the ts_devserver API changed and it no longer injects html script tags into a provided index.html file. The diff on this commit is large as this breaking change affects quite a few tests. Also note that we don’t update @angular/bazel schematics and integration/bazel as 0.41.0 is not a recommended update for angular users yet due to the breaking changes in ts_devserver & web_package (now named pkg_web). When a suitable plain npm package that is in progress is finished then it will be possible to easily replace the html injection functionality removed from ts_devserver & pkg_web. PR Close #33996
2019-11-22 21:12:05 +00:00
"karma-requirejs": "^1.1.0",
"karma-sourcemap-loader": "^0.3.7",
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: fix web_worker playground examples using external resources (#28562) The `web_workers/images` example is not being tested by any e2e spec and therefore it's technically not necessary to fix that it uses external resources, though in order to ensure that the Bazel builds are hermetic and that we can eventually add e2e specs for the web_worker/image example, we should avoid any use of external resources. We remove the `web-animations` polyfill in the `web_workers/animations` example because we should try to vendor as few as possible deps. Also the animations API is already supported by browsers we run the e2e tests against (note here: `web_workers/animations` is currently also disabled) PR Close #28562
2019-02-06 11:33:17 +00:00
"materialize-css": "1.0.0",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"memo-decorator": "^2.0.1",
"ngx-flamegraph": "0.0.11",
build: move zone.js to angular repo (#30962) PR Close #30962
2019-05-31 15:56:07 +00:00
"nodejs-websocket": "^1.7.2",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"protractor": "^7.0.0",
build: update puppeteer to 18.0.5 (#47584) This is needed as Angular does not support Chrome 93. PR Close #47584
2022-09-29 13:02:48 +00:00
"puppeteer": "18.0.5",
build: Move non-bazel deps to devDependencies (#26691) This makes yarn_install of ngdeps under Bazel faster, since we don't need many of the large dependencies. It's important because downstream angular/bazel users will observe the same install time. PR Close #26691
2018-10-22 21:26:52 +00:00
"reflect-metadata": "^0.1.3",
build: update to nodejs rules 0.41.0 (#33996) This bring is changes to the @nodejs repository required for https://github.com/angular/angular/pull/33927. See release notes for more details: https://github.com/bazelbuild/rules_nodejs/releases/tag/0.41.0. rules_nodejs is approaching 1.0 and breaking changes for that release are being made more frequently. In this release, the ts_devserver API changed and it no longer injects html script tags into a provided index.html file. The diff on this commit is large as this breaking change affects quite a few tests. Also note that we don’t update @angular/bazel schematics and integration/bazel as 0.41.0 is not a recommended update for angular users yet due to the breaking changes in ts_devserver & web_package (now named pkg_web). When a suitable plain npm package that is in progress is finished then it will be possible to easily replace the html injection functionality removed from ts_devserver & pkg_web. PR Close #33996
2019-11-22 21:12:05 +00:00
"requirejs": "^2.3.6",
build: update all non-major dependencies (#47225) See associated pull request for more information. PR Close #47225
2022-09-01 12:44:30 +00:00
"rollup": "~2.79.0",
build: update bazel setup to latest dev-infra package and rules_nodejs v4.2.0 (#43431) Updates the Bazel setup to the latest shared dev-infra package. Also the rules_nodejs version is updated to v4.2.0. We have landed various changes that prepare us for the APF v13 implementation. e.g. * Ability to control the linker mappings for the `ng_package` rule. This will become important for using a transition that could accidentally cause linker mappings that would otheriwse conflict. * Use of latest version of rollup & terser in the Bazel rules the dev-infra package exposes. This is necessary for ES2020 support. PR Close #43431
2021-09-27 21:41:51 +00:00
"rollup-plugin-preserve-shebang": "^1.0.1",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"rollup-plugin-sourcemaps": "^0.6.3",
test: re-enable platform-server integration test (#44055) Re-enables the platform-server integration test that we had to disable when we landed the APF v13 changes. We can re-enable it by setting up the `fullySpecified` option similar to how the CLI does it. PR Close #44055
2021-11-04 10:56:42 +00:00
"rxjs": "^6.6.7",
build: Move non-bazel deps to devDependencies (#26691) This makes yarn_install of ngdeps under Bazel faster, since we don't need many of the large dependencies. It's important because downstream angular/bazel users will observe the same install time. PR Close #26691
2018-10-22 21:26:52 +00:00
"selenium-webdriver": "3.5.0",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"semver-dsl": "^1.0.1",
build: avoid use of `ts-node` wrapper script as it breaks child process forking (#46456) `ts-node` spawns a custom node launcher script and has a brotli-base64 encoded configuration that will point to the user-provided entry-point. This breaks child process forking as we wouldn't be able to specify our custom build worker and basically `ng-dev` would run inside `ng-dev` again. PR Close #46456
2022-06-22 20:41:12 +00:00
"shelljs": "^0.8.5",
build: update source-map package to latest version (#46888) The source-map package is updated as part #46707, but the minor version bump introduced breaking changes. This commit extracts the update so that we can handle it separately accounting for the breaking changes. Also removing the caret since this package apparently makes breaking changes in minor segment bumps. PR Close #46888
2022-07-19 08:10:45 +00:00
"source-map": "0.7.4",
build: update dependency source-map-support to v0.5.21 (#44225) PR Close #44225
2021-11-19 11:32:21 +00:00
"source-map-support": "0.5.21",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"start-server-and-test": "^1.10.11",
build: switch playground examples to bazel (#28490) Currently all playground examples are built with `tsc` and served with the `gulp serve` task. In order to be able to test these examples easily with Ivy, we now build and serve the examples using Bazel. This allows us to expand our Ivy test coverage and additionally it allows us to move forward with the overall Bazel migration. Building & serving individual examples is now very easy and doesn't involve building everything inside of `/modules`. PR Close #28490
2019-02-01 13:27:13 +00:00
"systemjs": "0.18.10",
build: update bazel setup to latest dev-infra package and rules_nodejs v4.2.0 (#43431) Updates the Bazel setup to the latest shared dev-infra package. Also the rules_nodejs version is updated to v4.2.0. We have landed various changes that prepare us for the APF v13 implementation. e.g. * Ability to control the linker mappings for the `ng_package` rule. This will become important for using a transition that could accidentally cause linker mappings that would otheriwse conflict. * Use of latest version of rollup & terser in the Bazel rules the dev-infra package exposes. This is necessary for ES2020 support. PR Close #43431
2021-09-27 21:41:51 +00:00
"terser": "^5.8.0",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"tmp": "0.2.1",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"todomvc-app-css": "^2.3.0",
"todomvc-common": "^1.0.5",
feat(compiler-cli): support more recent version of `tsickle` (#47018) Updates the tsickle version in the repository and accounts for its changes in the `compiler-cli` package. Tsickle made a breaking change in the minor version segment bump that would break the use with `@angular/compiler-cli` Additionally the tsickle version for `@angular/bazel` is updated since we updated `@bazel/typescript` to also account for the breaking changes. See: https://github.com/bazelbuild/rules_nodejs/commit/78a05281075c50ee31658bc48dd852e35b973496 PR Close #47018
2022-07-25 13:44:11 +00:00
"tsickle": "0.46.3",
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",
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
"tslint": "6.1.3",
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.9.3",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"webtreemap": "^2.0.1",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"xhr2": "0.2.1",
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: Move non-bazel deps to devDependencies (#26691) This makes yarn_install of ngdeps under Bazel faster, since we don't need many of the large dependencies. It's important because downstream angular/bazel users will observe the same install time. PR Close #26691
2018-10-22 21:26:52 +00:00
},
"// 2": "devDependencies are not used under Bazel. Many can be removed after test.sh is deleted.",
"devDependencies": {
build: update dev-infra build tooling to leverage recent ESM changes (#48521) Update dev-infra's build-tooling since multiple ESM changes have landed there. e.g. not relying on `require.main === module` for API bundling. This will allow us to also execute all dev-infra rules in ESM because we plan on applying our ESM patching to `ts_library` (which would also affect build-tooling then). PR Close #48521
2022-12-12 16:18:01 +00:00
"@angular/build-tooling": "https://github.com/angular/dev-infra-private-build-tooling-builds.git#e1aec534818208328b29a76cfe9892c2a031ed94",
build: update cross-repo angular dependencies (#48405) See associated pull request for more information. PR Close #48405
2022-12-09 19:03:21 +00:00
"@angular/ng-dev": "https://github.com/angular/dev-infra-private-ng-dev-builds.git#05278122c48e06eff8e5398d59c49ed6688c949b",
build: update to latest version of `rules_nodejs` v3.3.0 (#41599) Updates to the latest version of `rules_nodejs` that supports the most recent NodeJS lts version v14.16.1. Additionally the latest version of `rules_nodejs` provides [a package for runfile resolution](https://github.com/bazelbuild/rules_nodejs/pull/2568) w/ types that we can leverage. PR Close #41599
2021-04-13 17:07:12 +00:00
"@bazel/bazelisk": "^1.7.5",
build: update bazel (#45431) Update `@bazel` packages to the latest 5.x version. Some of the changes here are modeled after angular/dev-infra@40c0ac855975ce9586b07af3a36a0bf4e3b58350. Co-Authored-By: George Kalpakas <kalpakas.g@gmail.com> PR Close #45431
2022-03-21 17:09:54 +00:00
"@bazel/buildifier": "^5.0.0",
build: update dependency @bazel/ibazel to ^0.16.0 (#45259) PR Close #45259
2022-03-26 01:14:35 +00:00
"@bazel/ibazel": "^0.16.0",
build: update dependency @octokit/graphql to v5 (#46753) See associated pull request for more information. PR Close #46753
2022-07-08 18:03:52 +00:00
"@octokit/graphql": "^5.0.0",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"@types/browser-sync": "^2.26.1",
build: convert CLDR locale extraction from Gulp to Bazel tool (#42230) Converts the CLDR locale extraction script to a Bazel tool. This allows us to generate locale files within Bazel, so that locales don't need to live as sources within the repo. Also it allows us to get rid of the legacy Gulp tooling. The migration of the Gulp script to a Bazel tool involved the following things: 1. Basic conversion of the `extract.js` script to TypeScript. This mostly was about adding explicit types. e.g. adding `locale: string` or `localeData: CldrStatic`. 2. Split-up into separate files. Instead of keeping the large `extract.js` file, the tool has been split into separate files. The logic remains the same, just that code is more readable and maintainable. 3. Introduction of a new `index.ts` file that is the entry-point for the Bazel tool. Previously the Gulp tool just generated all locale files, the default locale and base currency files at once. The new entry-point accepts a mode to be passed as first process argument. based on that argument, either locales are generated into a specified directory, or the default locale, base currencies or closure file is generated. This allows us to generate files with a Bazel genrule where we simply run the tool and specify the outputs. Note: It's necessary to have multiple modes because files live in separate locations. e.g. the default locale in `@angular/core`, but the rest in `@angular/common`. 4. Removal of the `cldr-data-downloader` and custom CLDR resolution logic. Within Bazel we cannot run a downloader using network. We switch this to something more Bazel idiomatic with better caching. For this a new repository rule is introduced that downloads the CLDR JSON repository and extracts it. Within that rule we determine the supported locales so that they can be used to pre-declare outputs (for the locales) within Bazel analysis phase. This allows us to add the generated locale files to a `ts_library` (which we want to have for better testing, and consistent JS transpilation). Note that the removal of `cldr-data-downloader` also requires us to add logic for detecting locales without data. The CLDR data downloader overwrote the `availableLocales.json` file with a file that only lists locales that CLDR provides data for. We use the official `availableLocales` file CLDR provides, but filter out locales for which no data is available. This is needed until we update to CLDR 39 where data is available for all such locales listed in `availableLocales.json`. PR Close #42230
2021-05-21 20:57:42 +00:00
"@types/cldrjs": "^0.4.22",
feat(dev-infra): create format tool in @angular/dev-infra-private (#36726) Previously we used gulp to run our formatter, currently clang-format, across our repository. This new tool within ng-dev allows us to migrate away from our gulp based solution as our gulp solution had issue with memory pressure and would cause OOM errors with too large of change sets. PR Close #36726
2020-04-20 20:00:10 +00:00
"@types/cli-progress": "^3.4.2",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"@types/minimist": "^1.2.0",
build: update dependency @types/send to ^0.17.0 (#44890) PR Close #44890
2022-01-29 09:34:09 +00:00
"@types/send": "^0.17.0",
ci: check versions of non-local integration project dependencies (#33968) In order to keep integration tests on CI as determinitstic as possible, we need to ensure that the same dependencies (including transitive ones) are installed each time. One way to ensure that is using a lockfile (such as `yarn.lock`) to pin the dependencies to exact versions. This works as long as the lockfile itself is in-sync with the corresponding `package.json`, which specifies the dependencies. Ideally, we would run `yarn install` with the `--frozen-lockfile` option to verify that the lockfile is in-sync with `package.json`, but we cannot do that for integration projects, because we want to be able to install the locally built Angular packages). Therefore, we must manually esnure that the integration project lockfiles remain in-sync, which is error-prone. This commit introduces a helper script that performs some checks on each project's (non-local) dependencies: - Ensure that exact versions (not version ranges) are specified in `package.json`. This reduces the probability of installing a breaking version of a direct or transitive dependency, in case of an out-of-sync lockfile. - Ensure that the lockfile is in-sync with `package.json` wrt these dependencies. While these checks are not full-proof, they provide yet another line of defense against indeterminism. PR Close #33968
2019-11-25 15:48:18 +00:00
"@yarnpkg/lockfile": "^1.1.0",
build: update all non-major dependencies (#45967) PR Close #45967
2022-05-16 22:16:36 +00:00
"browser-sync": "2.27.10",
build: Update dependencies (#40726) Updates some dependencies. PR Close #40726
2021-02-05 18:13:21 +00:00
"check-side-effects": "0.0.23",
build: update all non-major dependencies (#48271) See associated pull request for more information. PR Close #48271
2022-11-30 08:02:44 +00:00
"cldr": "7.3.0",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"cldrjs": "0.5.5",
"conventional-changelog": "^3.1.24",
build: avoid use of `ts-node` wrapper script as it breaks child process forking (#46456) `ts-node` spawns a custom node launcher script and has a brotli-base64 encoded configuration that will point to the user-provided entry-point. This breaks child process forking as we wouldn't be able to specify our custom build worker and basically `ng-dev` would run inside `ng-dev` again. PR Close #46456
2022-06-22 20:41:12 +00:00
"cross-env": "^7.0.3",
build: update dependency firebase-tools to v11 (#46779) See associated pull request for more information. PR Close #46779
2022-07-11 20:03:45 +00:00
"firebase-tools": "^11.0.0",
build: update all non-major dependencies (#45967) PR Close #45967
2022-05-16 22:16:36 +00:00
"glob": "8.0.3",
build: update gulp and gulp-conventional-changelog (#40810) Update gulp and gulp-conventional-changelog to address security vulnerabilities. PR Close #40810
2021-02-11 20:09:30 +00:00
"gulp": "^4.0.2",
"gulp-conventional-changelog": "^2.0.35",
build: update all non-major dependencies (#48271) See associated pull request for more information. PR Close #48271
2022-11-30 08:02:44 +00:00
"husky": "8.0.2",
build: update karma-sauce-launcher to latest version with heartbeat to prevent idle timeout (#43659) Updates the `karma-sauce-launcher` to the latest version that comes with the heartbeat implemented. Whenever we create an instance of a browser in Saucelabs, we need to send a Selenium command every X seconds as otherwise Saucelabs will terminate the session due to it thinking the session is already unused. This is especially a problem for Karma unit tests as there is no selenium command at all, except for the initial one loading the Karma site. The latest version of the launcher has implemented an interval that dispatches a noop selenium command every X seconds to notify Saucelabs that the instance is still active. The current version of the launcher does not do that. This is likely the source of some disconnects because after 10-13min, the SL browser is terminated but Karma still waits some minute after realizing the browser is actually disconnected. We (the Angular team), contributed to that version in the past since the heartbeat was very flaky.. and we removed it. With the new version a lot has changed, the underlying Selenium client has changed so it's worth trying again with the heartbeat re-implemented; it worked pretty well so far in the COMP repo). PR Close #43659
2021-09-30 20:37:22 +00:00
"karma-sauce-launcher": "^4.3.6",
build: update dependency madge to v5 (#42629) PR Close #42629
2021-06-24 15:49:49 +00:00
"madge": "^5.0.0",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"minimist": "^1.2.0",
build: bundle spec files for saucelabs legacy job (#44281) Bundle spec files similar to how it is done within the Angular Components repo. This should simplify the setup and also speed up the Saucelab job as only a single spec bundle would need to be downloaded, compared to having to load hundreds of files through the Saucelabs tunnel. Also makes a couple of tests more robust with the emulators/and accounts for ES2015 test runner changes. The tests should be less reluctant to such build process changes. Note for reviewers: Some imports have been simplified here. This work came from Joey's original WIP for this. It's unclear to me whether this is still needed, but it sounded like this was necessary for the ESBuild bundling to work. I have robusted the module resolution plugin though, so I doubt it's still needed. At the same time though: Not worth reverting/trying as these changes are nice to have anyway! Co-Authored-By: Joey Perrott <josephperrott@gmail.com> Co-Authored-By: Paul Gschwendtner <paulgschwendtner@gmail.com> PR Close #44281
2021-11-26 14:24:04 +00:00
"multimatch": "^6.0.0",
build: patch `ts_library` to not emit a tsickle extern file (#48521) The prodmode compilation pipeline -that we intend to use more heavily now given it emitting files with the `.mjs` extension- exposes an additional tsickle closure externs file. This file is empty most of the time anyway since tsickle is not wired up. We remove this generation as otherwise convenient `$(location` of such ts library targets break because there always is more than 1 file. PR Close #48521
2022-12-08 17:51:12 +00:00
"patch-package": "^6.5.0",
build: update angular (#44490) Updates Angular and the dev-infra package to the latest version/build. PR Close #44490
2021-12-13 17:48:47 +00:00
"prettier": "^2.5.1",
build: update saucelabs connect version (#47433) Update to saucelabs connect 4.8.1 PR Close #47433
2022-09-14 16:06:59 +00:00
"sauce-connect": "https://saucelabs.com/downloads/sc-4.8.1-linux.tar.gz",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"semver": "^7.3.5",
build: update dependency send to ^0.18.0 (#45428) PR Close #45428
2022-03-24 09:29:37 +00:00
"send": "^0.18.0",
build: update `dev-infra` package to latest version with full ESM (#46437) Updates `angular/dev-infra` to the latest version which is now full ESM. PR Close #46437
2022-06-20 13:05:13 +00:00
"ts-node": "^10.8.1",
build: update all non-major dependencies (#46707) See associated pull request for more information. PR Close #46707
2022-08-05 17:09:37 +00:00
"tsec": "0.2.6",
build: update tslint to latest version (#35800) The old version we currently use does not properly implement the option to exclude files from within the `tslint.json` file. PR Close #35800
2020-03-02 18:00:50 +00:00
"tslint-eslint-rules": "5.4.0",
refactor: remove toplevel property accesses (#29329) PR Close #29329
2019-05-02 15:44:24 +00:00
"tslint-no-toplevel-property-access": "0.0.2",
build: update typed-graphqlify to version 3.1.1 (#41738) Use latest version of typed-graphqlify PR Close #41738
2021-04-21 12:23:57 +00:00
"typed-graphqlify": "^3.1.1",
build: update dependency vlq to v2 (#43901) PR Close #43901
2021-10-20 10:22:10 +00:00
"vlq": "2.0.4",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"vrsource-tslint-rules": "6.0.0"
build: Fix gulp format for Node >= 10.14 (#28213) With Node.js v10.14 and greater, running `yarn gulp format` produces the following error: ``` $ nvm current v10.15.0 $ yarn gulp format:changed yarn run v1.12.3 $ /usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/.bin/gulp format:changed internal/util/inspect.js:31 const types = internalBinding('types'); ^ ReferenceError: internalBinding is not defined at internal/util/inspect.js:31:15 at req_ (/usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/natives/index.js:137:5) at require (/usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/natives/index.js:110:12) at util.js:25:21 at req_ (/usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/natives/index.js:137:5) at require (/usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/natives/index.js:110:12) at fs.js:42:21 at req_ (/usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/natives/index.js:137:5) at Object.req [as require] (/usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/natives/index.js:54:10) at Object.<anonymous> (/usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/vinyl-fs/node_modules/graceful-fs/fs.js:1:99) ``` A search on GitHub reveals this issue is due to natives@1.1.4: gulpjs/gulp#2246 ``` $ yarn why natives yarn why v1.12.3 [1/4] Why do we have the module "natives"...? [2/4] Initialising dependency graph... [3/4] Finding dependency... [4/4] Calculating file sizes... => Found "natives@1.1.6" info Reasons this module exists - "gulp#vinyl-fs#graceful-fs" depends on it - Hoisted from "gulp#vinyl-fs#graceful-fs#natives" - Hoisted from "browserstacktunnel-wrapper#unzip#fstream#graceful-fs#natives" ``` The solution is to add a manual resolution for natives@1.1.6 PR Close #28213
2019-01-18 18:43:04 +00:00
},
build: fix gulp setup not working with node v12 (#33348) It looks like the gulp setup does not work with NodeJS v12. This is because we still use gulp for a few tasks, but gulp v3 is not compatible with NodeJS v12. We had a similar issue for NodeJS v12, but worked around it by updating the `natives` module version. To actually solve this in a more future-proof way, without updating or removing Gulp (for now), we just overwrite the `graceful-fs` version. The latest version of `graceful-fs` does no longer depend on the `natives` package and therefore works properly with NodeJS >= v10. PR Close #33348
2019-10-23 10:49:49 +00:00
"// 4": "Overwrite graceful-fs to a version that does not rely on the 'natives' package. This fixes gulp for >= 10.13, more information: #28213",
test: use puppeteer in integration tests and to download correct chromedriver (#35049) This means integration tests no longer need to depend on a $CI_CHROMEDRIVER_VERSION_ARG environment variable to specify which chromedriver version to download to match the locally installed chrome. This was bad DX and not having it specified was not reliable as webdriver-manager would not always download the chromedriver version to work with the locally installed chrome. webdriver-manager update --gecko=false --standalone=false $CI_CHROMEDRIVER_VERSION_ARG is now replaced with node webdriver-manager-update.js in the root package.json, which checks which version of chrome puppeteer has come bundled with & downloads informs webdriver-manager to download the corresponding chrome driver version. Integration tests now use "webdriver-manager": "file:../../node_modules/webdriver-manager" so they don't have to waste time calling webdriver-manager update in postinstall "// resolutions": "Ensure a single version of webdriver-manager which comes from root node_modules that has already run webdriver-manager update", "resolutions": { "**/webdriver-manager": "file:../../node_modules/webdriver-manager" } This should speed up each integration postinstall by a few seconds. Further, integration test package.json files link puppeteer via file:../../node_modules/puppeteer which is the ideal situation as the puppeteer post-install won't download chrome if it is already downloaded. In CI, since node_modules is cached it should not need to download Chrome either unless the node_modules cache is busted. NB: each version of puppeteer comes bundles with a specific version of chrome. Root package.json & yarn.lock currently pull down puppeteer 2.1.0 which comes with chrome 80. See https://github.com/puppeteer/puppeteer#q-which-chromium-version-does-puppeteer-use for more info. Only two references to CI_CHROMEDRIVER_VERSION_ARG left in integration tests at integration/bazel-schematics/test.sh which I'm not entirely sure how to get rid of it Use a lightweight puppeteer=>chrome version mapping instead of launching chrome and calling browser.version() Launching puppeteer headless chrome and calling browser.version() was a heavy-handed approach to determine the Chrome version. A small and easy to update mappings file is a better solution and it means that the `yarn install` step does not require chrome shared libs available on the system for its postinstall step PR Close #35049
2020-01-31 23:50:44 +00:00
"// 5": "Ensure a single version of webdriver-manager so it is hoisted as the integration tests depend on it being found at ../../node_modules/webdriver-manager",
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
"// 6": "Ensure that transitive dependencies on `https-proxy-agent` are at minimum v5 as older versions patch NodeJS directly, breaking tools like webdriver which is used by the karma-sauce-launcher as an example.",
"// 7": "Ensure that a single instance of the `saucelabs` package is used. Protractor and the Karma sauce launcher pull this package as dependency. A single instance allows for e.g. easier patching in the Karma config.",
build: Fix gulp format for Node >= 10.14 (#28213) With Node.js v10.14 and greater, running `yarn gulp format` produces the following error: ``` $ nvm current v10.15.0 $ yarn gulp format:changed yarn run v1.12.3 $ /usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/.bin/gulp format:changed internal/util/inspect.js:31 const types = internalBinding('types'); ^ ReferenceError: internalBinding is not defined at internal/util/inspect.js:31:15 at req_ (/usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/natives/index.js:137:5) at require (/usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/natives/index.js:110:12) at util.js:25:21 at req_ (/usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/natives/index.js:137:5) at require (/usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/natives/index.js:110:12) at fs.js:42:21 at req_ (/usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/natives/index.js:137:5) at Object.req [as require] (/usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/natives/index.js:54:10) at Object.<anonymous> (/usr/local/google/home/kyliau/Documents/GitHub/angular/node_modules/vinyl-fs/node_modules/graceful-fs/fs.js:1:99) ``` A search on GitHub reveals this issue is due to natives@1.1.4: gulpjs/gulp#2246 ``` $ yarn why natives yarn why v1.12.3 [1/4] Why do we have the module "natives"...? [2/4] Initialising dependency graph... [3/4] Finding dependency... [4/4] Calculating file sizes... => Found "natives@1.1.6" info Reasons this module exists - "gulp#vinyl-fs#graceful-fs" depends on it - Hoisted from "gulp#vinyl-fs#graceful-fs#natives" - Hoisted from "browserstacktunnel-wrapper#unzip#fstream#graceful-fs#natives" ``` The solution is to add a manual resolution for natives@1.1.6 PR Close #28213
2019-01-18 18:43:04 +00:00
"resolutions": {
build: update all non-major dependencies (#45470) Updates all non-major dependencies, including Bazel PR Close #45470
2022-04-09 20:42:17 +00:00
"**/graceful-fs": "4.2.10",
build: update several dependencies (#41434) With this change we update several dependencies to avoid Renovate creating a lot of PRs during onboarding. We also remove yarn workspaces as after further analysis these are not needed. Certain dependencies such as `@octokit/rest`, `remark` and `@babel/*` have not been updated as they require a decent amount of work to update, and it's best to leave them for a seperate PR. PR Close #41434
2021-04-05 09:57:24 +00:00
"**/webdriver-manager": "12.1.8",
build: update all non-major dependencies (#45632) PR Close #45632
2022-04-14 19:37:46 +00:00
"**/https-proxy-agent": "5.0.1",
build: update all non-major dependencies (#46150) PR Close #46150
2022-06-10 02:41:07 +00:00
"**/saucelabs": "7.2.0"
build: convert CLDR locale extraction from Gulp to Bazel tool (#42230) Converts the CLDR locale extraction script to a Bazel tool. This allows us to generate locale files within Bazel, so that locales don't need to live as sources within the repo. Also it allows us to get rid of the legacy Gulp tooling. The migration of the Gulp script to a Bazel tool involved the following things: 1. Basic conversion of the `extract.js` script to TypeScript. This mostly was about adding explicit types. e.g. adding `locale: string` or `localeData: CldrStatic`. 2. Split-up into separate files. Instead of keeping the large `extract.js` file, the tool has been split into separate files. The logic remains the same, just that code is more readable and maintainable. 3. Introduction of a new `index.ts` file that is the entry-point for the Bazel tool. Previously the Gulp tool just generated all locale files, the default locale and base currency files at once. The new entry-point accepts a mode to be passed as first process argument. based on that argument, either locales are generated into a specified directory, or the default locale, base currencies or closure file is generated. This allows us to generate files with a Bazel genrule where we simply run the tool and specify the outputs. Note: It's necessary to have multiple modes because files live in separate locations. e.g. the default locale in `@angular/core`, but the rest in `@angular/common`. 4. Removal of the `cldr-data-downloader` and custom CLDR resolution logic. Within Bazel we cannot run a downloader using network. We switch this to something more Bazel idiomatic with better caching. For this a new repository rule is introduced that downloads the CLDR JSON repository and extracts it. Within that rule we determine the supported locales so that they can be used to pre-declare outputs (for the locales) within Bazel analysis phase. This allows us to add the generated locale files to a `ts_library` (which we want to have for better testing, and consistent JS transpilation). Note that the removal of `cldr-data-downloader` also requires us to add logic for detecting locales without data. The CLDR data downloader overwrote the `availableLocales.json` file with a file that only lists locales that CLDR provides data for. We use the official `availableLocales` file CLDR provides, but filter out locales for which no data is available. This is needed until we update to CLDR 39 where data is available for all such locales listed in `availableLocales.json`. PR Close #42230
2021-05-21 20:57:42 +00:00
}
release: cut the v14.0.0-next.12 release (#45603) PR Close #45603
2022-04-12 19:59:46 +00:00
}
Reference in a new issue Copy permalink