honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/yarn.lock

12165 lines
460 KiB
Plaintext
Raw Normal View History

build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
# yarn lockfile v1
build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) PR Close #29966
2019-04-17 20:13:07 -04:00
"@angular-devkit/architect@0.800.0-beta.15", "@angular-devkit/architect@^0.800.0-beta.15":
version "0.800.0-beta.15"
resolved "https://registry.yarnpkg.com/@angular-devkit/architect/-/architect-0.800.0-beta.15.tgz#2aa215ded902c6821c2b4f25e2d293766c5c30b0"
integrity sha512-ubEZsjAaDrW4VgnN7vFsx7XBDRfjeTKm/Ifqc03NcrvfBN5ze/iygzHS2kfSCmEcSkceAVJAKzAwSGRxRjcWKw==
build: update @angular/cli version to 8.0.0-beta.13 (#29873) This commit updates the version of @angular/cli to the recently pushed 8.0.0-beta.13. This is necessary as the CI has started to fail with a module hoisting issue caused by a relative import in the CLI, which is fixed in the latest (emergency) release. PR Close #29873
2019-04-12 18:51:39 -04:00
dependencies:
build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) PR Close #29966
2019-04-17 20:13:07 -04:00
"@angular-devkit/core" "8.0.0-beta.15"
build: update @angular/cli version to 8.0.0-beta.13 (#29873) This commit updates the version of @angular/cli to the recently pushed 8.0.0-beta.13. This is necessary as the CI has started to fail with a module hoisting issue caused by a relative import in the CLI, which is fixed in the latest (emergency) release. PR Close #29873
2019-04-12 18:51:39 -04:00
rxjs "6.4.0"
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
"@angular-devkit/build-optimizer@0.14.0-beta.5":
version "0.14.0-beta.5"
resolved "https://registry.yarnpkg.com/@angular-devkit/build-optimizer/-/build-optimizer-0.14.0-beta.5.tgz#f842a0b2717517cdc8e40704076d6182feccb81a"
integrity sha512-sQ86BGrd65QD9fV+wgDWNFKS2kxsZFj/lSn3pjgguV43XjGvnNlXnsVAgZOruygyXjB/afEOkNpO/4sKFNxiMw==
dependencies:
loader-utils "1.2.3"
source-map "0.5.6"
typescript "3.2.4"
webpack-sources "1.3.0"
build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) PR Close #29966
2019-04-17 20:13:07 -04:00
"@angular-devkit/build-optimizer@^0.800.0-beta.15":
version "0.800.0-beta.15"
resolved "https://registry.yarnpkg.com/@angular-devkit/build-optimizer/-/build-optimizer-0.800.0-beta.15.tgz#1474df7321ec90e7a2ce95a8fdb65fe44c1bb201"
integrity sha512-rQiMXZI4ySjFsLD0q4Ag7DDXAFUZkpueRJCa/AbOsHIen6/t4m6Vzn6wiHTE5VO7Exo3JQCAW04pENEH7Tqgxw==
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
dependencies:
build: update version of Angular CLI and Build Optimizer used for tests (#28372) PR Close #28372
2019-01-25 11:33:22 -05:00
loader-utils "1.2.3"
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
source-map "0.5.6"
build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) PR Close #29966
2019-04-17 20:13:07 -04:00
typescript "3.4.3"
build: update version of Angular CLI and Build Optimizer used for tests (#28372) PR Close #28372
2019-01-25 11:33:22 -05:00
webpack-sources "1.3.0"
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) PR Close #29966
2019-04-17 20:13:07 -04:00
"@angular-devkit/core@8.0.0-beta.15", "@angular-devkit/core@^8.0.0-beta.15":
version "8.0.0-beta.15"
resolved "https://registry.yarnpkg.com/@angular-devkit/core/-/core-8.0.0-beta.15.tgz#dac6ef16ddd5c2c5dc6a1184bd2aad7b8ed57e93"
integrity sha512-pWhD0aZ9vcjguBiR+22CT0ihvwmGTf5EY1lPBhIkbTkKXihQ3g0Pg36RHU2wW+dMlapZ6wuT9jW57vvJ2Vf41w==
build: update @angular/cli version to 8.0.0-beta.13 (#29873) This commit updates the version of @angular/cli to the recently pushed 8.0.0-beta.13. This is necessary as the CI has started to fail with a module hoisting issue caused by a relative import in the CLI, which is fixed in the latest (emergency) release. PR Close #29873
2019-04-12 18:51:39 -04:00
dependencies:
ajv "6.10.0"
fast-json-stable-stringify "2.0.0"
magic-string "0.25.2"
rxjs "6.4.0"
source-map "0.7.3"
build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) PR Close #29966
2019-04-17 20:13:07 -04:00
"@angular-devkit/schematics@8.0.0-beta.15", "@angular-devkit/schematics@^8.0.0-beta.15":
version "8.0.0-beta.15"
resolved "https://registry.yarnpkg.com/@angular-devkit/schematics/-/schematics-8.0.0-beta.15.tgz#fefb6f3dd3e6638f3484fc96a5fbbfc89732ba7b"
integrity sha512-XtOB6m0RjDfeNpiq1Zs6OelDwBL7dk7LBAICnYGpvexUKoksgFR6klQEbOconV+WB0YAYQqcqoTq5q9GI9s1ZA==
refactor(bazel): Remove bazel-workspace schematics (#29148) `bazel-workspace` schematics is no longer needed now that the Bazel files are injected into the project by the Bazel builder. PR Close #29148
2019-03-06 20:50:57 -05:00
dependencies:
build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) PR Close #29966
2019-04-17 20:13:07 -04:00
"@angular-devkit/core" "8.0.0-beta.15"
build: update @angular/cli version to 8.0.0-beta.13 (#29873) This commit updates the version of @angular/cli to the recently pushed 8.0.0-beta.13. This is necessary as the CI has started to fail with a module hoisting issue caused by a relative import in the CLI, which is fixed in the latest (emergency) release. PR Close #29873
2019-04-12 18:51:39 -04:00
rxjs "6.4.0"
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871) PR Close #28871
2019-02-20 12:54:42 -05:00
"@angular/bazel@file:./tools/npm/@angular_bazel":
version "0.0.0"
build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) PR Close #29966
2019-04-17 20:13:07 -04:00
"@angular/cli@^8.0.0-beta.15":
version "8.0.0-beta.15"
resolved "https://registry.yarnpkg.com/@angular/cli/-/cli-8.0.0-beta.15.tgz#0281691e3e91c02d6fcba4d4b3847731d4ce9860"
integrity sha512-bERWWHZbMe+8loT2DRkZSMwAgMQ6U29ya9pPH/sZM6Z2HwkNSOM3tMrFLWS1CkYVLIXq0tF3pVJ6Ss3HYwUuFg==
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
dependencies:
build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) PR Close #29966
2019-04-17 20:13:07 -04:00
"@angular-devkit/architect" "0.800.0-beta.15"
"@angular-devkit/core" "8.0.0-beta.15"
"@angular-devkit/schematics" "8.0.0-beta.15"
"@schematics/angular" "8.0.0-beta.15"
"@schematics/update" "0.800.0-beta.15"
test(bazel): Cleanup bazel-schematics integration test (#28351) PR Close #28351
2019-01-24 14:51:20 -05:00
"@yarnpkg/lockfile" "1.1.0"
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
debug "^4.1.1"
test(bazel): Cleanup bazel-schematics integration test (#28351) PR Close #28351
2019-01-24 14:51:20 -05:00
ini "1.3.5"
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
inquirer "6.2.2"
test(bazel): Cleanup bazel-schematics integration test (#28351) PR Close #28351
2019-01-24 14:51:20 -05:00
npm-package-arg "6.1.0"
build: update @angular/cli version to 8.0.0-beta.13 (#29873) This commit updates the version of @angular/cli to the recently pushed 8.0.0-beta.13. This is necessary as the CI has started to fail with a module hoisting issue caused by a relative import in the CLI, which is fixed in the latest (emergency) release. PR Close #29873
2019-04-12 18:51:39 -04:00
open "6.1.0"
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
pacote "9.5.0"
semver "6.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
symbol-observable "1.2.0"
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
universal-analytics "^0.4.20"
uuid "^3.3.2"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
"@babel/code-frame@^7.0.0":
version "7.0.0"
resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.0.0.tgz#06e2ab19bdb535385559aabb5ba59729482800f8"
integrity sha512-OfC2uemaknXr87bdLUkWog7nYuliM9Ij5HUcajsVcMCpQrcLmtxRbVFTIqmcSkSeYRBFBRxs2FiUqFJDLdiebA==
dependencies:
"@babel/highlight" "^7.0.0"
"@babel/highlight@^7.0.0":
version "7.0.0"
resolved "https://registry.yarnpkg.com/@babel/highlight/-/highlight-7.0.0.tgz#f710c38c8d458e6dd9a201afb637fcb781ce99e4"
integrity sha512-UFMC4ZeFC48Tpvj7C8UgLvtkaUuovQX+5xNWrsIoMG8o2z+XFKjKaN9iVmS84dPwVN00W4wPmqvYoZF3EGAsfw==
dependencies:
chalk "^2.0.0"
esutils "^2.0.2"
js-tokens "^4.0.0"
build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) nodejs rules 0.34.0 now includes protractor_web_test_suite rule (via new @bazel/protractor rule) so we switch to that location for that rule in this PR so that /packages/bazel/src/protractor can be removed in a future PR this PR also brings in node toolchain support which was released in nodejs rules 0.33.0. this is a prerequisite for RBE for mac & windows users bazel schematics also updated with the same. @bazel/bazel 0.28.1 npm package includes transitive dep on hide-bazel-files so we're able to remove an explicit dep on that as well. PR Close #31824
2019-07-24 11:52:26 -04:00
"@bazel/bazel-darwin_x64@0.28.1":
version "0.28.1"
resolved "https://registry.yarnpkg.com/@bazel/bazel-darwin_x64/-/bazel-darwin_x64-0.28.1.tgz#415658785e1dbd6f7ab5c8f2b98c1c99c614e1d5"
integrity sha512-VDKWmplAfa4uCAbkIQ5nRn04MFQqtsPNuc2HkluJ8OIum773yC2dPR+OlLBKxrlBuKJYB27TtbOwOa6w/uK7aw==
"@bazel/bazel-linux_x64@0.28.1":
version "0.28.1"
resolved "https://registry.yarnpkg.com/@bazel/bazel-linux_x64/-/bazel-linux_x64-0.28.1.tgz#f78006089e17660261088272a0e04fc886572e34"
integrity sha512-n4XfNxagYhejQD32V4XSxT/qzuH1l/2jxslbKSak66/uQ+wad8Ew9rjNb4JUin3xtrfFtzmxx2jpQkybZsRVGA==
"@bazel/bazel-win32_x64@0.28.1":
version "0.28.1"
resolved "https://registry.yarnpkg.com/@bazel/bazel-win32_x64/-/bazel-win32_x64-0.28.1.tgz#60a2819618cf7582cc35ac16c01763a5e807b414"
integrity sha512-T4xksGfKikaHS4zxnGT6r5R436mz9j2lz//L1vc5sJnaEF/1e2Gv6MLl86vfZW2Xxo6iIEi6ntSzgYxP2Blohw==
"@bazel/bazel@0.28.1":
version "0.28.1"
resolved "https://registry.yarnpkg.com/@bazel/bazel/-/bazel-0.28.1.tgz#3a6b9b7a74d566c66805242ccaa2f907592b5bff"
integrity sha512-s4bn5/vegEec66l15ZjyUe4jNybQ5J/cg9gFzR5f8deKj8lM+2WtCfvTLO3XfUe2pbrB4BG7C31jpyFPOC+6aw==
dependencies:
"@bazel/hide-bazel-files" latest
build: use bazel version from node modules (#26691) * No longer depends on a custom CircleCI docker image that comes with Bazel pre-installed. Since Bazel is now available through NPM, we should be able to use the version from `@bazel/bazel` in order to enforce a consistent environment on CI and locally. * This also reduces the amount of packages that need to be published (ngcontainer is removed) PR Close #26691
2018-10-27 03:25:45 -04:00
optionalDependencies:
build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) nodejs rules 0.34.0 now includes protractor_web_test_suite rule (via new @bazel/protractor rule) so we switch to that location for that rule in this PR so that /packages/bazel/src/protractor can be removed in a future PR this PR also brings in node toolchain support which was released in nodejs rules 0.33.0. this is a prerequisite for RBE for mac & windows users bazel schematics also updated with the same. @bazel/bazel 0.28.1 npm package includes transitive dep on hide-bazel-files so we're able to remove an explicit dep on that as well. PR Close #31824
2019-07-24 11:52:26 -04:00
"@bazel/bazel-darwin_x64" "0.28.1"
"@bazel/bazel-linux_x64" "0.28.1"
"@bazel/bazel-win32_x64" "0.28.1"
build: use bazel version from node modules (#26691) * No longer depends on a custom CircleCI docker image that comes with Bazel pre-installed. Since Bazel is now available through NPM, we should be able to use the version from `@bazel/bazel` in order to enforce a consistent environment on CI and locally. * This also reduces the amount of packages that need to be published (ngcontainer is removed) PR Close #26691
2018-10-27 03:25:45 -04:00
style: fix bazel lint in zone.js (#31172) Update to latest buildifier to fix a false positive error PR Close #31172
2019-06-20 14:53:45 -04:00
"@bazel/buildifier-darwin_x64@0.26.0":
version "0.26.0"
resolved "https://registry.yarnpkg.com/@bazel/buildifier-darwin_x64/-/buildifier-darwin_x64-0.26.0.tgz#0e4f5066750f7984689857e332f93368e0d782dd"
integrity sha512-yvlHuaP2FIMJ4Z4Ucs/R1wgwkDjhDkwvGD1eyhy9Qblqu7Ypgxtv2wz8dygrxDJVxhk3Kiwzlrp3otq6OYjv5A==
"@bazel/buildifier-linux_x64@0.26.0":
version "0.26.0"
resolved "https://registry.yarnpkg.com/@bazel/buildifier-linux_x64/-/buildifier-linux_x64-0.26.0.tgz#05020641f17441145056821ec33a2c667e253a3f"
integrity sha512-4+ZGEVMQdJr39My2eH6GmQrBIQfuw/DWO3Vwpy5vS1p61EvV0a5+jaukRelA3p//FD0j2cAKaBvwZdsijtDsZw==
"@bazel/buildifier-win32_x64@0.26.0":
version "0.26.0"
resolved "https://registry.yarnpkg.com/@bazel/buildifier-win32_x64/-/buildifier-win32_x64-0.26.0.tgz#51d983d36fd41f59063347e027487a447e4ea83e"
integrity sha512-S3QvjopF6cQ0rMv8zxi/SWfRBtA+oBGiTPcfpn1wJZa8Q21PdOcjH9ZgPJKpIV53x6sJ8XBVs7HSW44dPrwxQA==
"@bazel/buildifier@^0.26.0":
version "0.26.0"
resolved "https://registry.yarnpkg.com/@bazel/buildifier/-/buildifier-0.26.0.tgz#65af3851f9ebe8b9ac651185d051b1a155012dbb"
integrity sha512-PVzkCOYhjlgcRCXUO31dy/GmtjDWzeTyVmPCFc4pxTFBvlrG7qkVlUW3DCIbBI5neTes0pY8mju837UBdK0OFQ==
ci: use buildifier binary release (#27489) Switch from Skylint to buildifier --lint - this is required for the Bazel 0.20 upgrade since Bazel no longer lets us use the embedded JDK to build and run Java programs, and Skylint is a Java program PR Close #27489
2018-12-05 15:16:14 -05:00
optionalDependencies:
style: fix bazel lint in zone.js (#31172) Update to latest buildifier to fix a false positive error PR Close #31172
2019-06-20 14:53:45 -04:00
"@bazel/buildifier-darwin_x64" "0.26.0"
"@bazel/buildifier-linux_x64" "0.26.0"
"@bazel/buildifier-win32_x64" "0.26.0"
ci: use buildifier binary release (#27489) Switch from Skylint to buildifier --lint - this is required for the Bazel 0.20 upgrade since Bazel no longer lets us use the embedded JDK to build and run Java programs, and Skylint is a Java program PR Close #27489
2018-12-05 15:16:14 -05:00
build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) nodejs rules 0.34.0 now includes protractor_web_test_suite rule (via new @bazel/protractor rule) so we switch to that location for that rule in this PR so that /packages/bazel/src/protractor can be removed in a future PR this PR also brings in node toolchain support which was released in nodejs rules 0.33.0. this is a prerequisite for RBE for mac & windows users bazel schematics also updated with the same. @bazel/bazel 0.28.1 npm package includes transitive dep on hide-bazel-files so we're able to remove an explicit dep on that as well. PR Close #31824
2019-07-24 11:52:26 -04:00
"@bazel/hide-bazel-files@latest":
version "0.34.0"
resolved "https://registry.yarnpkg.com/@bazel/hide-bazel-files/-/hide-bazel-files-0.34.0.tgz#368ea84db2756ff80ead23bb9eb179e9ed24b462"
integrity sha512-suyO6cZf8iV6W2LkM1X1spWBt7CsRRXH7gU1wYNuAuHYkkfI0A6qj84yPiIXiOt/2G44kbioGyC1bUsI3fKv7A==
build: update to rules_nodejs 0.32.2 (#31325) Brings in ts_library fixes required to get angular/angular building after 0.32.0: typescript: exclude typescript lib declarations in node_module_library transitive_declarations typescript: remove override of @bazel/tsetse (+1 squashed commit) @npm//node_modules/foobar:foobar.js labels changed to @npm//:node_modules/foobar/foobar.js with fix for bazelbuild/rules_nodejs#802 also updates to rules_rass commit compatible with rules_nodejs 0.32.0 PR Close #31325
2019-06-19 00:26:53 -04:00
build: update ibazel to version that supports windows (#32390) The `bazel-watcher` (also known as `ibazel`) currently does not work on windows. This is because all versions before `v0.10.0` did not have official windows support. This commit updates `ibazel` to the latest version which also comes with windows support. PR Close #32390
2019-08-29 05:52:45 -04:00
"@bazel/ibazel@^0.10.3":
version "0.10.3"
resolved "https://registry.yarnpkg.com/@bazel/ibazel/-/ibazel-0.10.3.tgz#2e2b8a1d3e885946eac41db2b1aa6801fb319887"
integrity sha512-v1nXbMTHVlMM4z4uWp6XiRoHAyUlYggF1SOboLLWRp0+D22kWixqArWqnozLw2mOtnxr97BdLjluWiho6A8Hjg==
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
"@bazel/jasmine@0.38.1":
version "0.38.1"
resolved "https://registry.yarnpkg.com/@bazel/jasmine/-/jasmine-0.38.1.tgz#0741e090de1d69a9ef0a961a88e4fdfb6c7d6c77"
integrity sha512-tUVVBceOt3Of2RsY/ys298HfVkPyz44nO+quZ5eU5hwf16KW62rFZsIo+ZgVguUsDmzjjWFN+pUcfA535rPsiw==
build: update to latest bazel rules (#28931) PR Close #28931
2019-02-22 16:22:11 -05:00
dependencies:
build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) nodejs rules 0.34.0 now includes protractor_web_test_suite rule (via new @bazel/protractor rule) so we switch to that location for that rule in this PR so that /packages/bazel/src/protractor can be removed in a future PR this PR also brings in node toolchain support which was released in nodejs rules 0.33.0. this is a prerequisite for RBE for mac & windows users bazel schematics also updated with the same. @bazel/bazel 0.28.1 npm package includes transitive dep on hide-bazel-files so we're able to remove an explicit dep on that as well. PR Close #31824
2019-07-24 11:52:26 -04:00
jasmine "~3.4.0"
jasmine-core "~3.4.0"
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
v8-coverage "1.0.9"
build: update to latest bazel rules (#28931) PR Close #28931
2019-02-22 16:22:11 -05:00
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
"@bazel/karma@0.38.1":
version "0.38.1"
resolved "https://registry.yarnpkg.com/@bazel/karma/-/karma-0.38.1.tgz#7175b2284d21b1a725f24d8ca24577ec7c54c222"
integrity sha512-Hz6+7tm70Qv59iX+iryln7WC1GT8R2Jc93zu6EdqlkyVSWbTb6J+pmp3hcBKG+4Y2iAlLk+Czaj8cQu1DRt8GQ==
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
dependencies:
jasmine-core "2.8.0"
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
karma "~4.1.0"
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
karma-chrome-launcher "2.2.0"
karma-firefox-launcher "1.1.0"
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
karma-jasmine "2.0.1"
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
karma-requirejs "1.1.0"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
karma-sauce-launcher "2.0.2"
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
karma-sourcemap-loader "0.3.7"
requirejs "2.3.5"
build(bazel): Bump @bazel/typescript & @bazel/karma to 0.22.1 (#28031) PR Close #28031
2019-01-09 19:22:06 -05:00
semver "5.6.0"
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
tmp "0.0.33"
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
"@bazel/protractor@0.38.1":
version "0.38.1"
resolved "https://registry.yarnpkg.com/@bazel/protractor/-/protractor-0.38.1.tgz#0785c863254071f6d848d1d78c7ceb47af9ae218"
integrity sha512-bAixjddJyGA4OKxkhKIWNH1u5atOm7qCQKTR5GFhEEECuxwabwuyZGDtGzWGKgngCwy7UZitG8BTX2CKU4cknw==
build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) nodejs rules 0.34.0 now includes protractor_web_test_suite rule (via new @bazel/protractor rule) so we switch to that location for that rule in this PR so that /packages/bazel/src/protractor can be removed in a future PR this PR also brings in node toolchain support which was released in nodejs rules 0.33.0. this is a prerequisite for RBE for mac & windows users bazel schematics also updated with the same. @bazel/bazel 0.28.1 npm package includes transitive dep on hide-bazel-files so we're able to remove an explicit dep on that as well. PR Close #31824
2019-07-24 11:52:26 -04:00
dependencies:
protractor "^5.4.2"
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
"@bazel/typescript@0.38.1":
version "0.38.1"
resolved "https://registry.yarnpkg.com/@bazel/typescript/-/typescript-0.38.1.tgz#fe9a84e0992580a4b67cbc48fbe72f9154bacf56"
integrity sha512-etTftAm6jN0cdHS9Pgb6fJXgHaot+nRhgr8VjUKZr/ITs31U7iDA/9ehjoVFVbqzJzQy4BfdicbydP+cqXz2Xg==
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
dependencies:
build(bazel): update to nodejs rules 0.27.10 (#29694) PR Close #29694
2019-04-03 19:56:20 -04:00
protobufjs "6.8.8"
build(bazel): Bump @bazel/typescript & @bazel/karma to 0.22.1 (#28031) PR Close #28031
2019-01-09 19:22:06 -05:00
semver "5.6.0"
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
source-map-support "0.5.9"
tsutils "2.27.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
"@buxlabs/amd-to-es6@^0.12.0":
version "0.12.5"
resolved "https://registry.yarnpkg.com/@buxlabs/amd-to-es6/-/amd-to-es6-0.12.5.tgz#18c12479512ae09106fc6f60ad1b4b9eb8e8eb62"
integrity sha512-RaZQrUhSl+IPIn3tBdMlDAb20jcWcBGQpnmUth9Jf9Bx1c7zGPQAxTzuag5UBLGBEBAKGr5fxvwGGdF+C/mDjQ==
dependencies:
"@buxlabs/ast" "^0.9.5"
"@buxlabs/utils" "^2.2.2"
array-uniq "^1.0.3"
commander "^2.13.0"
glob "^7.1.2"
mkdirp "^0.5.1"
"@buxlabs/ast@^0.9.5":
version "0.9.6"
resolved "https://registry.yarnpkg.com/@buxlabs/ast/-/ast-0.9.6.tgz#e7a14d3fae74cd3d0530fd2cf39afc09272707e7"
integrity sha512-1fKAxOU/c3uLa0mQL2jrNqv0QkcMJMnDfze/N5HeIh3DWtl9Q8PfOskuGa+zZb/EZEwLLNACmHbIUTvfM0Ogsw==
dependencies:
comparify "^0.2.0"
escodegen "^1.9.0"
espree "^3.5.1"
esquery "^1.0.0"
estemplate "^0.5.1"
estraverse "^4.2.0"
prettier "^1.7.4"
to-ast "^1.0.0"
"@buxlabs/utils@^2.2.2":
version "2.3.4"
resolved "https://registry.yarnpkg.com/@buxlabs/utils/-/utils-2.3.4.tgz#32a3102e5875c4b0f34cac89ec403748b1759249"
integrity sha512-XtGxRNCQFf0Ed5aXSsjJWdZfs8o4eFBNqtXyFvyiAQ/8/W+YfkTAgwbBUHECSd4qOxgOXI5iQcYDn21rEN7TMw==
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
"@google-cloud/common@^0.17.0":
version "0.17.0"
resolved "https://registry.yarnpkg.com/@google-cloud/common/-/common-0.17.0.tgz#8ef558750db481fc10a13757a49479ab9a1c8c07"
integrity sha512-HRZLSU762E6HaKoGfJGa8W95yRjb9rY7LePhjaHK9ILAnFacMuUGVamDbTHu1csZomm1g3tZTtXfX/aAhtie/Q==
dependencies:
array-uniq "^1.0.3"
arrify "^1.0.1"
concat-stream "^1.6.0"
create-error-class "^3.0.2"
duplexify "^3.5.0"
ent "^2.2.0"
extend "^3.0.1"
google-auto-auth "^0.10.0"
is "^3.2.0"
log-driver "1.2.7"
methmeth "^1.1.0"
modelo "^4.2.0"
request "^2.79.0"
retry-request "^3.0.0"
split-array-stream "^1.0.0"
stream-events "^1.0.1"
string-format-obj "^1.1.0"
through2 "^2.0.3"
"@google-cloud/functions-emulator@^1.0.0-beta.5":
version "1.0.0-beta.5"
resolved "https://registry.yarnpkg.com/@google-cloud/functions-emulator/-/functions-emulator-1.0.0-beta.5.tgz#08aa14a007b739aadcf7296e0b4354cd8a8d81df"
integrity sha512-65qxXqyyD5SnKBlv76YNZDKRxP2o8sh2B5bSkiV4VHNmoaRiB/SYjc2GQuKqrxwJ6MbI4mhTLgvNTy6BSP2QSQ==
dependencies:
"@google-cloud/storage" "^1.7.0"
adm-zip "^0.4.11"
ajv "^6.5.2"
body-parser "^1.18.3"
cli-table2 "0.2.0"
colors "1.1.2"
configstore "^3.1.2"
express "^4.16.3"
googleapis "^23.0.2"
got "^8.3.2"
http-proxy "1.16.2"
lodash "4.17.5"
prompt "1.0.0"
rimraf "2.6.2"
semver "5.5.0"
serializerr "1.0.3"
tmp "0.0.33"
uuid "3.2.1"
winston "2.4.0"
yargs "11.0.0"
"@google-cloud/storage@^1.7.0":
version "1.7.0"
resolved "https://registry.yarnpkg.com/@google-cloud/storage/-/storage-1.7.0.tgz#07bff573d92d5c294db6a04af246688875a8f74b"
integrity sha512-QaAxzCkbhspwajoaEnT0GcnQcpjPRcBrHYuQsXtD05BtOJgVnHCLXSsfUiRdU0nVpK+Thp7+sTkQ0fvk5PanKg==
dependencies:
"@google-cloud/common" "^0.17.0"
arrify "^1.0.0"
async "^2.0.1"
compressible "^2.0.12"
concat-stream "^1.5.0"
create-error-class "^3.0.2"
duplexify "^3.5.0"
extend "^3.0.0"
gcs-resumable-upload "^0.10.2"
hash-stream-validation "^0.2.1"
is "^3.0.1"
mime "^2.2.0"
mime-types "^2.0.8"
once "^1.3.1"
pumpify "^1.5.1"
request "^2.85.0"
safe-buffer "^5.1.1"
snakeize "^0.1.0"
stream-events "^1.0.1"
through2 "^2.0.0"
xdg-basedir "^3.0.0"
feat(bazel): update to the latest `@microsoft/api-extractor` (#32185) PR Close #32185
2019-08-19 05:55:34 -04:00
"@microsoft/api-extractor-model@7.3.2":
version "7.3.2"
resolved "https://registry.yarnpkg.com/@microsoft/api-extractor-model/-/api-extractor-model-7.3.2.tgz#71229ba80f8aafc56afe4d3ee83f19b1ce72eb24"
integrity sha512-2yNbQsQl5PI36l5WzHQshwjBHPe5IeIcmidWad0E+wjyaAxGMLx5pBp5AgXY2JG9S9VQjFmmGmqJJBXn8tzu+w==
dependencies:
"@microsoft/node-core-library" "3.14.0"
"@microsoft/tsdoc" "0.12.12"
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
"@types/node" "8.5.8"
feat(bazel): update to the latest `@microsoft/api-extractor` (#32185) PR Close #32185
2019-08-19 05:55:34 -04:00
"@microsoft/api-extractor@^7.3.9":
version "7.3.9"
resolved "https://registry.yarnpkg.com/@microsoft/api-extractor/-/api-extractor-7.3.9.tgz#c035748e9e8745eb9df43351f76ace1f529d17dc"
integrity sha512-8qj+N/3CgJaHFZj/YlXqtyPAK8vQ2e4oFzKrzbQNw5mtlVnyLlayTkNfVIq93Q0xRMwAhPJjlmxmAuu1ZI88oQ==
dependencies:
"@microsoft/api-extractor-model" "7.3.2"
"@microsoft/node-core-library" "3.14.0"
"@microsoft/ts-command-line" "4.2.7"
"@microsoft/tsdoc" "0.12.12"
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
colors "~1.2.1"
feat(bazel): update to the latest `@microsoft/api-extractor` (#32185) PR Close #32185
2019-08-19 05:55:34 -04:00
lodash "~4.17.15"
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
resolve "1.8.1"
feat(bazel): update to the latest `@microsoft/api-extractor` (#32185) PR Close #32185
2019-08-19 05:55:34 -04:00
source-map "~0.6.1"
typescript "~3.5.3"
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
feat(bazel): update to the latest `@microsoft/api-extractor` (#32185) PR Close #32185
2019-08-19 05:55:34 -04:00
"@microsoft/node-core-library@3.14.0":
version "3.14.0"
resolved "https://registry.yarnpkg.com/@microsoft/node-core-library/-/node-core-library-3.14.0.tgz#c7014328c67c4a4110e2ed2a9bd11cfd0ad3318d"
integrity sha512-+gbTXTRfvR40hTH+C3Vno/RJ51sU/RZAyHb2bo9af8GCdOgxCxCs+qp2KCXklbpuolmIPFfbCmdTwv90yH5tJw==
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
dependencies:
"@types/fs-extra" "5.0.4"
"@types/jju" "~1.4.0"
"@types/node" "8.5.8"
"@types/z-schema" "3.16.31"
colors "~1.2.1"
fs-extra "~7.0.1"
jju "~1.4.0"
z-schema "~3.18.3"
feat(bazel): update to the latest `@microsoft/api-extractor` (#32185) PR Close #32185
2019-08-19 05:55:34 -04:00
"@microsoft/ts-command-line@4.2.7":
version "4.2.7"
resolved "https://registry.yarnpkg.com/@microsoft/ts-command-line/-/ts-command-line-4.2.7.tgz#01e963c683ae782e57225c5c424aa65702a9732c"
integrity sha512-PwUMIIDl8oWyl64Y5DW5FAuoRk4KWTBZdk4FEh366KEm5xYFBQhCeatHGURIj8nEYm0Xb2coCrXF77dGDlp/Qw==
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
dependencies:
"@types/argparse" "1.0.33"
"@types/node" "8.5.8"
argparse "~1.0.9"
colors "~1.2.1"
feat(bazel): update to the latest `@microsoft/api-extractor` (#32185) PR Close #32185
2019-08-19 05:55:34 -04:00
"@microsoft/tsdoc@0.12.12":
version "0.12.12"
resolved "https://registry.yarnpkg.com/@microsoft/tsdoc/-/tsdoc-0.12.12.tgz#6692f1cbca664f68abbc62f9a26459fba8b9ff28"
integrity sha512-5EzH1gHIonvvgA/xWRmVAJmRkTQj/yayUXyr66hFwNZiFE4j7lP8is9YQeXhwxGZEjO1PVMblAmFF0CyjNtPGw==
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
build(bazel): update to nodejs rules 0.27.10 (#29694) PR Close #29694
2019-04-03 19:56:20 -04:00
"@protobufjs/aspromise@^1.1.1", "@protobufjs/aspromise@^1.1.2":
version "1.1.2"
resolved "https://registry.yarnpkg.com/@protobufjs/aspromise/-/aspromise-1.1.2.tgz#9b8b0cc663d669a7d8f6f5d0893a14d348f30fbf"
integrity sha1-m4sMxmPWaafY9vXQiToU00jzD78=
"@protobufjs/base64@^1.1.2":
version "1.1.2"
resolved "https://registry.yarnpkg.com/@protobufjs/base64/-/base64-1.1.2.tgz#4c85730e59b9a1f1f349047dbf24296034bb2735"
integrity sha512-AZkcAA5vnN/v4PDqKyMR5lx7hZttPDgClv83E//FMNhR2TMcLUhfRUBHCmSl0oi9zMgDDqRUJkSxO3wm85+XLg==
"@protobufjs/codegen@^2.0.4":
version "2.0.4"
resolved "https://registry.yarnpkg.com/@protobufjs/codegen/-/codegen-2.0.4.tgz#7ef37f0d010fb028ad1ad59722e506d9262815cb"
integrity sha512-YyFaikqM5sH0ziFZCN3xDC7zeGaB/d0IUb9CATugHWbd1FRFwWwt4ld4OYMPWu5a3Xe01mGAULCdqhMlPl29Jg==
"@protobufjs/eventemitter@^1.1.0":
version "1.1.0"
resolved "https://registry.yarnpkg.com/@protobufjs/eventemitter/-/eventemitter-1.1.0.tgz#355cbc98bafad5978f9ed095f397621f1d066b70"
integrity sha1-NVy8mLr61ZePntCV85diHx0Ga3A=
"@protobufjs/fetch@^1.1.0":
version "1.1.0"
resolved "https://registry.yarnpkg.com/@protobufjs/fetch/-/fetch-1.1.0.tgz#ba99fb598614af65700c1619ff06d454b0d84c45"
integrity sha1-upn7WYYUr2VwDBYZ/wbUVLDYTEU=
dependencies:
"@protobufjs/aspromise" "^1.1.1"
"@protobufjs/inquire" "^1.1.0"
"@protobufjs/float@^1.0.2":
version "1.0.2"
resolved "https://registry.yarnpkg.com/@protobufjs/float/-/float-1.0.2.tgz#5e9e1abdcb73fc0a7cb8b291df78c8cbd97b87d1"
integrity sha1-Xp4avctz/Ap8uLKR33jIy9l7h9E=
"@protobufjs/inquire@^1.1.0":
version "1.1.0"
resolved "https://registry.yarnpkg.com/@protobufjs/inquire/-/inquire-1.1.0.tgz#ff200e3e7cf2429e2dcafc1140828e8cc638f089"
integrity sha1-/yAOPnzyQp4tyvwRQIKOjMY48Ik=
"@protobufjs/path@^1.1.2":
version "1.1.2"
resolved "https://registry.yarnpkg.com/@protobufjs/path/-/path-1.1.2.tgz#6cc2b20c5c9ad6ad0dccfd21ca7673d8d7fbf68d"
integrity sha1-bMKyDFya1q0NzP0hynZz2Nf79o0=
"@protobufjs/pool@^1.1.0":
version "1.1.0"
resolved "https://registry.yarnpkg.com/@protobufjs/pool/-/pool-1.1.0.tgz#09fd15f2d6d3abfa9b65bc366506d6ad7846ff54"
integrity sha1-Cf0V8tbTq/qbZbw2ZQbWrXhG/1Q=
"@protobufjs/utf8@^1.1.0":
version "1.1.0"
resolved "https://registry.yarnpkg.com/@protobufjs/utf8/-/utf8-1.1.0.tgz#a777360b5b39a1a2e5106f8e858f2fd2d060c570"
integrity sha1-p3c2C1s5oaLlEG+OhY8v0tBgxXA=
build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) PR Close #29966
2019-04-17 20:13:07 -04:00
"@schematics/angular@8.0.0-beta.15", "@schematics/angular@^8.0.0-beta.15":
version "8.0.0-beta.15"
resolved "https://registry.yarnpkg.com/@schematics/angular/-/angular-8.0.0-beta.15.tgz#f285f5e87a2bc84f3960da86b67cb8c6680ae4aa"
integrity sha512-zQ+EAIN6jDRxyA9iHXWdHFrAsV+O6a75Ph+7qx5Sj11i4qCCeScg461xz108V4Taat6E7ZRgG/uru8LZi1JOlw==
refactor(bazel): Remove bazel-workspace schematics (#29148) `bazel-workspace` schematics is no longer needed now that the Bazel files are injected into the project by the Bazel builder. PR Close #29148
2019-03-06 20:50:57 -05:00
dependencies:
build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) PR Close #29966
2019-04-17 20:13:07 -04:00
"@angular-devkit/core" "8.0.0-beta.15"
"@angular-devkit/schematics" "8.0.0-beta.15"
refactor(bazel): Remove bazel-workspace schematics (#29148) `bazel-workspace` schematics is no longer needed now that the Bazel files are injected into the project by the Bazel builder. PR Close #29148
2019-03-06 20:50:57 -05:00
build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) PR Close #29966
2019-04-17 20:13:07 -04:00
"@schematics/update@0.800.0-beta.15":
version "0.800.0-beta.15"
resolved "https://registry.yarnpkg.com/@schematics/update/-/update-0.800.0-beta.15.tgz#b5842e5defd653a12852800a6454982866e1c88f"
integrity sha512-VSdR2LEA7jXc8vxjeuhindpCSkBhiXvMR/r5fvjkQOdg4lBsj6EgE0PIYYcrPUizXQDLtDQNTuwZkmZxduEbAQ==
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
dependencies:
build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) PR Close #29966
2019-04-17 20:13:07 -04:00
"@angular-devkit/core" "8.0.0-beta.15"
"@angular-devkit/schematics" "8.0.0-beta.15"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
"@yarnpkg/lockfile" "1.1.0"
ini "1.3.5"
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
pacote "9.5.0"
rxjs "6.4.0"
semver "6.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
semver-intersect "1.4.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
"@sindresorhus/is@^0.7.0":
version "0.7.0"
resolved "https://registry.yarnpkg.com/@sindresorhus/is/-/is-0.7.0.tgz#9a06f4f137ee84d7df0460c1fdb1135ffa6c50fd"
integrity sha512-ONhaKPIufzzrlNbqtWFFd+jlnemX6lJAgq9ZeiZtS7I1PIf/la7CW4m83rTXRnVnsMbW2k56pGYu7AUFJD9Pow==
build: upgrade AngularJS typings (#24583) Previously, we were using [@types/angularjs][1], which is deprecated and outdated (hasn't been updated for over two years). This PR switches to [@types/angular][2], which is regularly updated (based on the definitions on [DefinitelyTyped][3]). [1]: https://www.npmjs.com/package/@types/angularjs [2]: https://www.npmjs.com/package/@types/angular [3]: https://github.com/DefinitelyTyped/DefinitelyTyped PR Close #24583
2018-06-20 06:29:37 -04:00
"@types/angular@^1.6.47":
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.6.48"
resolved "https://registry.yarnpkg.com/@types/angular/-/angular-1.6.48.tgz#e8f77bf41d00d3293421cbaaed2bafb4d5f399f9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-zF0WlsWOjTkZjWq93ESfvq/4s3E9P8EnbIjOFzlDbhepL2iOBk9SJf98eqnV2fvjstwrPF+uYZvcAggL7Xw1FA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
"@types/argparse@1.0.33":
version "1.0.33"
resolved "https://registry.yarnpkg.com/@types/argparse/-/argparse-1.0.33.tgz#2728669427cdd74a99e53c9f457ca2866a37c52d"
integrity sha512-VQgHxyPMTj3hIlq9SY1mctqx+Jj8kpQfoLvDlVSDNOyuYs8JYfkuY3OW/4+dO657yPmNhHpePRx0/Tje5ImNVQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"@types/base64-js@1.2.5":
version "1.2.5"
resolved "https://registry.yarnpkg.com/@types/base64-js/-/base64-js-1.2.5.tgz#582b2476169a6cba460a214d476c744441d873d5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-WCskdhaabLpGCiFNR2x0REHYc9U=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: move zone.js to angular repo (#30962) PR Close #30962
2019-05-31 11:56:07 -04:00
"@types/bluebird@^3.5.27":
version "3.5.27"
resolved "https://registry.yarnpkg.com/@types/bluebird/-/bluebird-3.5.27.tgz#61eb4d75dc6bfbce51cf49ee9bbebe941b2cb5d0"
integrity sha512-6BmYWSBea18+tSjjSC3QIyV93ZKAeNWGM7R6aYt1ryTZXrlHF+QLV0G2yV0viEGVyRkyQsWfMoJ0k/YghBX5sQ==
build(bazel): remove @ts-api-guardian_deps yarn_install (#29799) PR Close #29799
2019-04-09 21:08:13 -04:00
"@types/chai@^4.1.2":
version "4.1.7"
resolved "https://registry.yarnpkg.com/@types/chai/-/chai-4.1.7.tgz#1b8e33b61a8c09cbe1f85133071baa0dbf9fa71a"
integrity sha512-2Y8uPt0/jwjhQ6EiluT0XCri1Dbplr0ZxfFXUz+ye13gaqE8u5gL5ppao1JrUYr9cIip5S6MvQzBS7Kke7U9VA==
build(compiler-cli): upgrade chokidar to latest version (#28797) Fixes #28771 PR Close #28797
2019-02-18 08:11:03 -05:00
"@types/chokidar@^1.7.5":
version "1.7.5"
resolved "https://registry.yarnpkg.com/@types/chokidar/-/chokidar-1.7.5.tgz#1fa78c8803e035bed6d98e6949e514b133b0c9b6"
integrity sha512-PDkSRY7KltW3M60hSBlerxI8SFPXsO3AL/aRVsO4Kh9IHRW74Ih75gUuTd/aE4LSSFqypb10UIX3QzOJwBQMGQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(compiler-cli): upgrade chokidar to latest version (#28797) Fixes #28771 PR Close #28797
2019-02-18 08:11:03 -05:00
"@types/events" "*"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"@types/node" "*"
build: add dependencies to be used by ngcc (#24897) PR Close #24897
2018-07-16 02:08:48 -04:00
"@types/convert-source-map@^1.5.1":
version "1.5.1"
resolved "https://registry.yarnpkg.com/@types/convert-source-map/-/convert-source-map-1.5.1.tgz#d4d180dd6adc5cb68ad99bd56e03d637881f4616"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-laiDIXqqthjJlyAMYAXOtN3N8+UlbM+KvZi4BaY5ZOekmVkBs/UxfK5O0HWeJVG2eW8F+Mu2ww13fTX+kY1FlQ==
build: add dependencies to be used by ngcc (#24897) PR Close #24897
2018-07-16 02:08:48 -04:00
build(bazel): remove @ts-api-guardian_deps yarn_install (#29799) PR Close #29799
2019-04-09 21:08:13 -04:00
"@types/diff@^3.5.1":
version "3.5.3"
resolved "https://registry.yarnpkg.com/@types/diff/-/diff-3.5.3.tgz#7c6c3721ba454d838790100faf7957116ee7deab"
integrity sha512-YrLagYnL+tfrgM7bQ5yW34pi5cg9pmh5Gbq2Lmuuh+zh0ZjmK2fU3896PtlpJT3IDG2rdkoG30biHJepgIsMnw==
test: display a diff when example_apckage.spec.ts fails to ease debugging (#22933) PR Close #22933
2018-03-22 13:37:43 -04:00
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
"@types/estree@0.0.39":
version "0.0.39"
resolved "https://registry.yarnpkg.com/@types/estree/-/estree-0.0.39.tgz#e177e699ee1b8c22d23174caaa7422644389509f"
integrity sha512-EYNwp3bU+98cpU4lAWYYL7Zz+2gryWH1qbdDTidVd6hkiR6weksdbMadyXKXNPEkQFhXM+hVO9ZygomHXp+AIw==
feat(bazel): add an ng_package rule (#22221) This produces a directory following the Angular Package layout spec. Includes integration test coverage by making a minimal ng_package in integration/bazel. Unit tests verify the content of the @angular/core and @angular/common packages. This doesn't totally match our current output, but is good enough to unblock some early adopters. It re-uses logic from the rollup_bundle rule in rules_nodejs. It should also eventually have the .pack and .publish secondary targets like npm_package rule. PR Close #22221
2018-02-13 14:26:06 -05:00
"@types/events@*":
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/@types/events/-/events-1.2.0.tgz#81a6731ce4df43619e5c8c945383b3e62a89ea86"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-KEIlhXnIutzKwRbQkGWb/I4HFqBuUykAdHgDED6xqwXJfONCjF5VoE0cXEiurh3XauygxzeDzgtXUqvLkxFzzA==
feat(bazel): add an ng_package rule (#22221) This produces a directory following the Angular Package layout spec. Includes integration test coverage by making a minimal ng_package in integration/bazel. Unit tests verify the content of the @angular/core and @angular/common packages. This doesn't totally match our current output, but is good enough to unblock some early adopters. It re-uses logic from the rollup_bundle rule in rules_nodejs. It should also eventually have the .pack and .publish secondary targets like npm_package rule. PR Close #22221
2018-02-13 14:26:06 -05:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
"@types/fs-extra@4.0.2":
version "4.0.2"
resolved "https://registry.yarnpkg.com/@types/fs-extra/-/fs-extra-4.0.2.tgz#7b9b1bbf85962cbe029b5a83c9b530d7c75af3ba"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-Id1hnmfd+7G9K+jWz2syfMcpymx2mj6B1y4C72vAoYQzxOA79UhY/kNvOCyb9yYR1SoSaHyhwcYtWKKqUiLTZA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
"@types/node" "*"
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
"@types/fs-extra@5.0.4":
version "5.0.4"
resolved "https://registry.yarnpkg.com/@types/fs-extra/-/fs-extra-5.0.4.tgz#b971134d162cc0497d221adde3dbb67502225599"
integrity sha512-DsknoBvD8s+RFfSGjmERJ7ZOP1HI0UZRA3FSI+Zakhrc/Gy26YQsLI+m5V5DHxroHRJqCDLKJp7Hixn8zyaF7g==
dependencies:
"@types/node" "*"
feat(bazel): add an ng_package rule (#22221) This produces a directory following the Angular Package layout spec. Includes integration test coverage by making a minimal ng_package in integration/bazel. Unit tests verify the content of the @angular/core and @angular/common packages. This doesn't totally match our current output, but is good enough to unblock some early adopters. It re-uses logic from the rollup_bundle rule in rules_nodejs. It should also eventually have the .pack and .publish secondary targets like npm_package rule. PR Close #22221
2018-02-13 14:26:06 -05:00
"@types/glob@*":
version "5.0.35"
resolved "https://registry.yarnpkg.com/@types/glob/-/glob-5.0.35.tgz#1ae151c802cece940443b5ac246925c85189f32a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-wc+VveszMLyMWFvXLkloixT4n0harUIVZjnpzztaZ0nKLuul7Z32iMt2fUFGAaZ4y1XWjFRMtCI5ewvyh4aIeg==
feat(bazel): add an ng_package rule (#22221) This produces a directory following the Angular Package layout spec. Includes integration test coverage by making a minimal ng_package in integration/bazel. Unit tests verify the content of the @angular/core and @angular/common packages. This doesn't totally match our current output, but is good enough to unblock some early adopters. It re-uses logic from the rollup_bundle rule in rules_nodejs. It should also eventually have the .pack and .publish secondary targets like npm_package rule. PR Close #22221
2018-02-13 14:26:06 -05:00
dependencies:
"@types/events" "*"
"@types/minimatch" "*"
"@types/node" "*"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
"@types/hammerjs@2.0.35":
version "2.0.35"
resolved "https://registry.yarnpkg.com/@types/hammerjs/-/hammerjs-2.0.35.tgz#7b7c950c7d54593e23bffc8d2b4feba9866a7277"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-4mUIMSZ2U4UOWq1b+iV7XUTE4w+Kr3x+Zb/Qz5ROO6BTZLw2c8/ftjq0aRgluguLs4KRuBnrOy/s389HVn1/zA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
refactor(core): allow developers to select static-query migration strategy (#29876) Currently there are two available migration strategies for the `static-query` schematic. Both have benefits and negatives which depend on what the developer prefers. Since we can't decide which migration strategy is the best for a given project, the developer should be able to select a specific strategy through a simple choice prompt. In order to be able to use prompts in a migration schematic, we need to take advantage of the "inquirer" package which is also used by the CLI schematic prompts (schematic prompts are usually only statically defined in the schema). Additionally the schematic needs to be made "async" because with prompts the schematic can no longer execute synchronously without implementing some logic that blocks the execution. PR Close #29876
2019-04-12 18:14:33 -04:00
"@types/inquirer@^0.0.44":
version "0.0.44"
resolved "https://registry.yarnpkg.com/@types/inquirer/-/inquirer-0.0.44.tgz#60ce954581cfdf44ad3899ec4cdc5fbe3fef1694"
integrity sha512-ugbhy1yBtCz5iTWYF+AGRS/UcMcWicdyHhxl9VaeFYc3ueg0CCssthQLB3rIcIOeGtfG6WPEvHdLu/IjKYfefg==
dependencies:
"@types/rx" "*"
"@types/through" "*"
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 15:59:25 -05:00
"@types/jasmine@*":
version "3.3.5"
resolved "https://registry.yarnpkg.com/@types/jasmine/-/jasmine-3.3.5.tgz#3738ffbf34dffae9ecaac4503d7d969744f0e1d7"
integrity sha512-LJtc52O1PNUffMvH6Q3fS0BOhQWYlkh3SVu/Jc4GoPgJkUytk5Y6YPbw+6lZK2mWWvG62BtVyOFw0ih7r8STsw==
"@types/jasmine@^2.8.8":
build: upgrade jasmine (and related typings) to latest version (#19904) With these changes, the types are a little stricter now and also not compatible with Protractor's jasmine-like syntax. So, we have to also use `@types/jasminewd2` for e2e tests (but not for non-e2e tests). I also had to "augment" `@types/jasminewd2`, because the latest typings from [DefinitelyTyped][1] do not reflect the fact that the `jasminewd2` version (v2.1.0) currently used by Protractor supports passing a `done` callback to a spec. [1]: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/566e0394859fdc1dc893658ccec6b06372d56a91/types/jasminewd2/index.d.ts#L9-L15 Fixes #23952 Closes #24733 PR Close #19904
2017-10-24 07:54:08 -04:00
version "2.8.8"
resolved "https://registry.yarnpkg.com/@types/jasmine/-/jasmine-2.8.8.tgz#bf53a7d193ea8b03867a38bfdb4fbb0e0bf066c9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-OJSUxLaxXsjjhob2DBzqzgrkLmukM3+JMpRp0r0E4HTdT1nwDCWhaswjYxazPij6uOdzHCJfNbDjmQ1/rnNbCg==
build: upgrade jasmine (and related typings) to latest version (#19904) With these changes, the types are a little stricter now and also not compatible with Protractor's jasmine-like syntax. So, we have to also use `@types/jasminewd2` for e2e tests (but not for non-e2e tests). I also had to "augment" `@types/jasminewd2`, because the latest typings from [DefinitelyTyped][1] do not reflect the fact that the `jasminewd2` version (v2.1.0) currently used by Protractor supports passing a `done` callback to a spec. [1]: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/566e0394859fdc1dc893658ccec6b06372d56a91/types/jasminewd2/index.d.ts#L9-L15 Fixes #23952 Closes #24733 PR Close #19904
2017-10-24 07:54:08 -04:00
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 15:59:25 -05:00
"@types/jasminewd2@^2.0.6":
version "2.0.6"
resolved "https://registry.yarnpkg.com/@types/jasminewd2/-/jasminewd2-2.0.6.tgz#2f57a8d9875a6c9ef328a14bd070ba14a055ac39"
integrity sha512-2ZOKrxb8bKRmP/po5ObYnRDgFE4i+lQiEB27bAMmtMWLgJSqlIDqlLx6S0IRorpOmOPRQ6O80NujTmQAtBkeNw==
build: upgrade jasmine (and related typings) to latest version (#19904) With these changes, the types are a little stricter now and also not compatible with Protractor's jasmine-like syntax. So, we have to also use `@types/jasminewd2` for e2e tests (but not for non-e2e tests). I also had to "augment" `@types/jasminewd2`, because the latest typings from [DefinitelyTyped][1] do not reflect the fact that the `jasminewd2` version (v2.1.0) currently used by Protractor supports passing a `done` callback to a spec. [1]: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/566e0394859fdc1dc893658ccec6b06372d56a91/types/jasminewd2/index.d.ts#L9-L15 Fixes #23952 Closes #24733 PR Close #19904
2017-10-24 07:54:08 -04:00
dependencies:
"@types/jasmine" "*"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
"@types/jju@~1.4.0":
version "1.4.0"
resolved "https://registry.yarnpkg.com/@types/jju/-/jju-1.4.0.tgz#ee074af79540c0e187426f46f12acbe8f6c31232"
integrity sha512-s6l49zLzFiXYHaTXbA+FNcDRo8ufZgC2/T5/jH+Wfr+ZV2tYbrBpEpN9oPkXXfug+y7pTZFkdeyQ0L/88Z34JA==
build(bazel): update to nodejs rules 0.27.10 (#29694) PR Close #29694
2019-04-03 19:56:20 -04:00
"@types/long@^4.0.0":
version "4.0.0"
resolved "https://registry.yarnpkg.com/@types/long/-/long-4.0.0.tgz#719551d2352d301ac8b81db732acb6bdc28dbdef"
integrity sha512-1w52Nyx4Gq47uuu0EVcsHBxZFJgurQ+rTKS3qMHxR1GY2T8c2AJYd6vZoZ9q1rupaDjU0yT+Jc2XTyXkjeMA+Q==
feat(bazel): add an ng_package rule (#22221) This produces a directory following the Angular Package layout spec. Includes integration test coverage by making a minimal ng_package in integration/bazel. Unit tests verify the content of the @angular/core and @angular/common packages. This doesn't totally match our current output, but is good enough to unblock some early adopters. It re-uses logic from the rollup_bundle rule in rules_nodejs. It should also eventually have the .pack and .publish secondary targets like npm_package rule. PR Close #22221
2018-02-13 14:26:06 -05:00
"@types/minimatch@*":
version "3.0.3"
resolved "https://registry.yarnpkg.com/@types/minimatch/-/minimatch-3.0.3.tgz#3dca0e3f33b200fc7d1139c0cd96c1268cadfd9d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-tHq6qdbT9U1IRSGf14CL0pUlULksvY9OZ+5eEgl1N7t+OA3tGvNpxJCzuKQlsNgCVwbAs670L1vcVQi8j9HjnA==
feat(bazel): add an ng_package rule (#22221) This produces a directory following the Angular Package layout spec. Includes integration test coverage by making a minimal ng_package in integration/bazel. Unit tests verify the content of the @angular/core and @angular/common packages. This doesn't totally match our current output, but is good enough to unblock some early adopters. It re-uses logic from the rollup_bundle rule in rules_nodejs. It should also eventually have the .pack and .publish secondary targets like npm_package rule. PR Close #22221
2018-02-13 14:26:06 -05:00
build: ts-api-guardian reuses root node_modules (#22894) This avoids the need to run bazel run :install instead of yarn install. We merge the devDependencies of ts-api-guardian into the root package.json file. PR Close #22894
2018-03-20 16:13:06 -04:00
"@types/minimist@^1.2.0":
version "1.2.0"
resolved "https://registry.yarnpkg.com/@types/minimist/-/minimist-1.2.0.tgz#69a23a3ad29caf0097f06eda59b361ee2f0639f6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-aaI6OtKcrwCX8G7aWbNh7i8GOfY=
build: ts-api-guardian reuses root node_modules (#22894) This avoids the need to run bazel run :install instead of yarn install. We merge the devDependencies of ts-api-guardian into the root package.json file. PR Close #22894
2018-03-20 16:13:06 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"@types/node@*":
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "10.5.2"
resolved "https://registry.yarnpkg.com/@types/node/-/node-10.5.2.tgz#f19f05314d5421fe37e74153254201a7bf00a707"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-m9zXmifkZsMHZBOyxZWilMwmTlpC8x5Ty360JKTiXvlXZfBWYpsg9ZZvP/Ye+iZUh+Q+MxDLjItVTWIsfwz+8Q==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
"@types/node@8.5.8":
version "8.5.8"
resolved "https://registry.yarnpkg.com/@types/node/-/node-8.5.8.tgz#92509422653f10e9c0ac18d87e0610b39f9821c7"
integrity sha512-8KmlRxwbKZfjUHFIt3q8TF5S2B+/E5BaAoo/3mgc5h6FJzqxXkCK/VMetO+IRDtwtU6HUvovHMBn+XRj7SV9Qg==
build(bazel): update to nodejs rules 0.27.10 (#29694) PR Close #29694
2019-04-03 19:56:20 -04:00
"@types/node@^10.1.0":
version "10.14.4"
resolved "https://registry.yarnpkg.com/@types/node/-/node-10.14.4.tgz#1c586b991457cbb58fef51bc4e0cfcfa347714b5"
integrity sha512-DT25xX/YgyPKiHFOpNuANIQIVvYEwCWXgK2jYYwqgaMrYE6+tq+DtmMwlD3drl6DJbUwtlIDnn0d7tIn/EbXBg==
build: update node type version (#25862) PR Close #25862
2018-09-10 06:44:48 -04:00
"@types/node@^10.9.4":
version "10.9.4"
resolved "https://registry.yarnpkg.com/@types/node/-/node-10.9.4.tgz#0f4cb2dc7c1de6096055357f70179043c33e9897"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-fCHV45gS+m3hH17zgkgADUSi2RR1Vht6wOZ0jyHP8rjiQra9f+mIcgwPQHllmDocYOstIEbKlxbFDYlgrTPYqw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
"@types/node@^11.13.9":
version "11.13.10"
resolved "https://registry.yarnpkg.com/@types/node/-/node-11.13.10.tgz#4df59e5966b56f512bac98898bcbee5067411f0f"
integrity sha512-leUNzbFTMX94TWaIKz8N15Chu55F9QSH+INKayQr5xpkasBQBRF3qQXfo3/dOnMU/dEIit+Y/SU8HyOjq++GwA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"@types/q@^0.0.32":
version "0.0.32"
resolved "https://registry.yarnpkg.com/@types/q/-/q-0.0.32.tgz#bd284e57c84f1325da702babfc82a5328190c0c5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-vShOV8hPEyXacCur/IKlMoGQwMU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
"@types/resolve@0.0.8":
version "0.0.8"
resolved "https://registry.yarnpkg.com/@types/resolve/-/resolve-0.0.8.tgz#f26074d238e02659e323ce1a13d041eee280e194"
integrity sha512-auApPaJf3NPfe18hSoJkp8EbZzer2ISk7o8mCC3M9he/a04+gbMF97NkpD2S8riMGvm4BMRI59/SZQSaLTKpsQ==
dependencies:
"@types/node" "*"
refactor(core): allow developers to select static-query migration strategy (#29876) Currently there are two available migration strategies for the `static-query` schematic. Both have benefits and negatives which depend on what the developer prefers. Since we can't decide which migration strategy is the best for a given project, the developer should be able to select a specific strategy through a simple choice prompt. In order to be able to use prompts in a migration schematic, we need to take advantage of the "inquirer" package which is also used by the CLI schematic prompts (schematic prompts are usually only statically defined in the schema). Additionally the schematic needs to be made "async" because with prompts the schematic can no longer execute synchronously without implementing some logic that blocks the execution. PR Close #29876
2019-04-12 18:14:33 -04:00
"@types/rx-core-binding@*":
version "4.0.4"
resolved "https://registry.yarnpkg.com/@types/rx-core-binding/-/rx-core-binding-4.0.4.tgz#d969d32f15a62b89e2862c17b3ee78fe329818d3"
integrity sha512-5pkfxnC4w810LqBPUwP5bg7SFR/USwhMSaAeZQQbEHeBp57pjKXRlXmqpMrLJB4y1oglR/c2502853uN0I+DAQ==
dependencies:
"@types/rx-core" "*"
"@types/rx-core@*":
version "4.0.3"
resolved "https://registry.yarnpkg.com/@types/rx-core/-/rx-core-4.0.3.tgz#0b3354b1238cedbe2b74f6326f139dbc7a591d60"
integrity sha1-CzNUsSOM7b4rdPYybxOdvHpZHWA=
"@types/rx-lite-aggregates@*":
version "4.0.3"
resolved "https://registry.yarnpkg.com/@types/rx-lite-aggregates/-/rx-lite-aggregates-4.0.3.tgz#6efb2b7f3d5f07183a1cb2bd4b1371d7073384c2"
integrity sha512-MAGDAHy8cRatm94FDduhJF+iNS5//jrZ/PIfm+QYw9OCeDgbymFHChM8YVIvN2zArwsRftKgE33QfRWvQk4DPg==
dependencies:
"@types/rx-lite" "*"
"@types/rx-lite-async@*":
version "4.0.2"
resolved "https://registry.yarnpkg.com/@types/rx-lite-async/-/rx-lite-async-4.0.2.tgz#27fbf0caeff029f41e2d2aae638b05e91ceb600c"
integrity sha512-vTEv5o8l6702ZwfAM5aOeVDfUwBSDOs+ARoGmWAKQ6LOInQ8J4/zjM7ov12fuTpktUKdMQjkeCp07Vd73mPkxw==
dependencies:
"@types/rx-lite" "*"
"@types/rx-lite-backpressure@*":
version "4.0.3"
resolved "https://registry.yarnpkg.com/@types/rx-lite-backpressure/-/rx-lite-backpressure-4.0.3.tgz#05abb19bdf87cc740196c355e5d0b37bb50b5d56"
integrity sha512-Y6aIeQCtNban5XSAF4B8dffhIKu6aAy/TXFlScHzSxh6ivfQBQw6UjxyEJxIOt3IT49YkS+siuayM2H/Q0cmgA==
dependencies:
"@types/rx-lite" "*"
"@types/rx-lite-coincidence@*":
version "4.0.3"
resolved "https://registry.yarnpkg.com/@types/rx-lite-coincidence/-/rx-lite-coincidence-4.0.3.tgz#80bd69acc4054a15cdc1638e2dc8843498cd85c0"
integrity sha512-1VNJqzE9gALUyMGypDXZZXzR0Tt7LC9DdAZQ3Ou/Q0MubNU35agVUNXKGHKpNTba+fr8GdIdkC26bRDqtCQBeQ==
dependencies:
"@types/rx-lite" "*"
"@types/rx-lite-experimental@*":
version "4.0.1"
resolved "https://registry.yarnpkg.com/@types/rx-lite-experimental/-/rx-lite-experimental-4.0.1.tgz#c532f5cbdf3f2c15da16ded8930d1b2984023cbd"
integrity sha1-xTL1y98/LBXaFt7Ykw0bKYQCPL0=
dependencies:
"@types/rx-lite" "*"
"@types/rx-lite-joinpatterns@*":
version "4.0.1"
resolved "https://registry.yarnpkg.com/@types/rx-lite-joinpatterns/-/rx-lite-joinpatterns-4.0.1.tgz#f70fe370518a8432f29158cc92ffb56b4e4afc3e"
integrity sha1-9w/jcFGKhDLykVjMkv+1a05K/D4=
dependencies:
"@types/rx-lite" "*"
"@types/rx-lite-testing@*":
version "4.0.1"
resolved "https://registry.yarnpkg.com/@types/rx-lite-testing/-/rx-lite-testing-4.0.1.tgz#21b19d11f4dfd6ffef5a9d1648e9c8879bfe21e9"
integrity sha1-IbGdEfTf1v/vWp0WSOnIh5v+Iek=
dependencies:
"@types/rx-lite-virtualtime" "*"
"@types/rx-lite-time@*":
version "4.0.3"
resolved "https://registry.yarnpkg.com/@types/rx-lite-time/-/rx-lite-time-4.0.3.tgz#0eda65474570237598f3448b845d2696f2dbb1c4"
integrity sha512-ukO5sPKDRwCGWRZRqPlaAU0SKVxmWwSjiOrLhoQDoWxZWg6vyB9XLEZViKOzIO6LnTIQBlk4UylYV0rnhJLxQw==
dependencies:
"@types/rx-lite" "*"
"@types/rx-lite-virtualtime@*":
version "4.0.3"
resolved "https://registry.yarnpkg.com/@types/rx-lite-virtualtime/-/rx-lite-virtualtime-4.0.3.tgz#4b30cacd0fe2e53af29f04f7438584c7d3959537"
integrity sha512-3uC6sGmjpOKatZSVHI2xB1+dedgml669ZRvqxy+WqmGJDVusOdyxcKfyzjW0P3/GrCiN4nmRkLVMhPwHCc5QLg==
dependencies:
"@types/rx-lite" "*"
"@types/rx-lite@*":
version "4.0.6"
resolved "https://registry.yarnpkg.com/@types/rx-lite/-/rx-lite-4.0.6.tgz#3c02921c4244074234f26b772241bcc20c18c253"
integrity sha512-oYiDrFIcor9zDm0VDUca1UbROiMYBxMLMaM6qzz4ADAfOmA9r1dYEcAFH+2fsPI5BCCjPvV9pWC3X3flbrvs7w==
dependencies:
"@types/rx-core" "*"
"@types/rx-core-binding" "*"
"@types/rx@*":
version "4.1.1"
resolved "https://registry.yarnpkg.com/@types/rx/-/rx-4.1.1.tgz#598fc94a56baed975f194574e0f572fd8e627a48"
integrity sha1-WY/JSla67ZdfGUV04PVy/Y5iekg=
dependencies:
"@types/rx-core" "*"
"@types/rx-core-binding" "*"
"@types/rx-lite" "*"
"@types/rx-lite-aggregates" "*"
"@types/rx-lite-async" "*"
"@types/rx-lite-backpressure" "*"
"@types/rx-lite-coincidence" "*"
"@types/rx-lite-experimental" "*"
"@types/rx-lite-joinpatterns" "*"
"@types/rx-lite-testing" "*"
"@types/rx-lite-time" "*"
"@types/rx-lite-virtualtime" "*"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
"@types/selenium-webdriver@3.0.7":
version "3.0.7"
resolved "https://registry.yarnpkg.com/@types/selenium-webdriver/-/selenium-webdriver-3.0.7.tgz#5d3613d1ab3ca08b74d19683a3a7c573129ab18f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-tHdDdGUBKTbiLLwf5mF78EP35F31UZekG+GRNowl8G5rMQoupAT4qWn/7AaGOvmaqvROdqC3Io/hP1ZyO58QkA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
"@types/selenium-webdriver@^3.0.0":
version "3.0.14"
resolved "https://registry.yarnpkg.com/@types/selenium-webdriver/-/selenium-webdriver-3.0.14.tgz#0b20a2370e6b1b8322c9c3dfcaa409e6c7c0c0a9"
integrity sha512-4GbNCDs98uHCT/OMv40qQC/OpoPbYn9XdXeTiFwHBBFO6eJhYEPUu2zDKirXSbHlvDV8oZ9l8EQ+HrEx/YS9DQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
feat(bazel): add an ng_package rule (#22221) This produces a directory following the Angular Package layout spec. Includes integration test coverage by making a minimal ng_package in integration/bazel. Unit tests verify the content of the @angular/core and @angular/common packages. This doesn't totally match our current output, but is good enough to unblock some early adopters. It re-uses logic from the rollup_bundle rule in rules_nodejs. It should also eventually have the .pack and .publish secondary targets like npm_package rule. PR Close #22221
2018-02-13 14:26:06 -05:00
"@types/shelljs@^0.7.8":
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.7.9"
resolved "https://registry.yarnpkg.com/@types/shelljs/-/shelljs-0.7.9.tgz#3abecb72d9cad9cd4b0e7cb86ed10a97d93ba602"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-GwfXBWx+JgH+mrf35NnNFPFl6kQZgDQqZBUdWrHB1phulBbVpOwedZun7hZRyfTOxlicwo4ftsC1fpUZZIiN5w==
feat(bazel): add an ng_package rule (#22221) This produces a directory following the Angular Package layout spec. Includes integration test coverage by making a minimal ng_package in integration/bazel. Unit tests verify the content of the @angular/core and @angular/common packages. This doesn't totally match our current output, but is good enough to unblock some early adopters. It re-uses logic from the rollup_bundle rule in rules_nodejs. It should also eventually have the .pack and .publish secondary targets like npm_package rule. PR Close #22221
2018-02-13 14:26:06 -05:00
dependencies:
"@types/glob" "*"
"@types/node" "*"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"@types/systemjs@0.19.32":
version "0.19.32"
resolved "https://registry.yarnpkg.com/@types/systemjs/-/systemjs-0.19.32.tgz#e9204c4cdbc8e275d645c00e6150e68fc5615a24"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-6SBMTNvI4nXWRcAOYVDmj8VhWiQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
refactor(core): allow developers to select static-query migration strategy (#29876) Currently there are two available migration strategies for the `static-query` schematic. Both have benefits and negatives which depend on what the developer prefers. Since we can't decide which migration strategy is the best for a given project, the developer should be able to select a specific strategy through a simple choice prompt. In order to be able to use prompts in a migration schematic, we need to take advantage of the "inquirer" package which is also used by the CLI schematic prompts (schematic prompts are usually only statically defined in the schema). Additionally the schematic needs to be made "async" because with prompts the schematic can no longer execute synchronously without implementing some logic that blocks the execution. PR Close #29876
2019-04-12 18:14:33 -04:00
"@types/through@*":
version "0.0.29"
resolved "https://registry.yarnpkg.com/@types/through/-/through-0.0.29.tgz#72943aac922e179339c651fa34a4428a4d722f93"
integrity sha512-9a7C5VHh+1BKblaYiq+7Tfc+EOmjMdZaD1MYtkQjSoxgB69tBjW98ry6SKsi4zEIWztLOMRuL87A3bdT/Fc/4w==
dependencies:
"@types/node" "*"
fix(ivy): ngcc should compile entry-points in the correct order (#25862) The compiler should process all an entry-points dependencies before processing that entry-point. PR Close #25862
2018-08-09 10:59:10 -04:00
"@types/yargs@^11.1.1":
version "11.1.1"
resolved "https://registry.yarnpkg.com/@types/yargs/-/yargs-11.1.1.tgz#2e724257167fd6b615dbe4e54301e65fe597433f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-Awgju4dqD8kHXX3jc/B/LaryJC7MsyNfnbN62lIbFzTi0GewH64zrkh4bxo/YTgVEK6r9V3GNecxMhXTJw0+jA==
fix(ivy): ngcc should compile entry-points in the correct order (#25862) The compiler should process all an entry-points dependencies before processing that entry-point. PR Close #25862
2018-08-09 10:59:10 -04:00
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
"@types/z-schema@3.16.31":
version "3.16.31"
resolved "https://registry.yarnpkg.com/@types/z-schema/-/z-schema-3.16.31.tgz#2eb1d00a5e4ec3fa58c76afde12e182b66dc5c1c"
integrity sha1-LrHQCl5Ow/pYx2r94S4YK2bcXBw=
feat(elements): add support for creating custom elements (#22413) PR Close #22413
2018-02-28 12:45:11 -05:00
"@webcomponents/custom-elements@^1.0.4":
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.1.2"
resolved "https://registry.yarnpkg.com/@webcomponents/custom-elements/-/custom-elements-1.1.2.tgz#041e4c20df35245f4d160b50d044b8cff192962c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-gVhuQHLTrQ28v1qMp0WGPSCBukFL7qAlemxCf19TnuNZ0bO9KPF72bfhH6Hpuwdu9TptIMGNlqrr9PzqrzfZFQ==
feat(elements): add support for creating custom elements (#22413) PR Close #22413
2018-02-28 12:45:11 -05:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
"@yarnpkg/lockfile@1.1.0":
version "1.1.0"
resolved "https://registry.yarnpkg.com/@yarnpkg/lockfile/-/lockfile-1.1.0.tgz#e77a97fbd345b76d83245edcd17d393b1b41fb31"
integrity sha512-GpSwvyXOcOOlV70vbnzjj4fW5xW/FdUF6nQEt1ENy7m4ZCczi1+/buVUPAqmGfqznsORNFzUMjctTIp8a9tuCQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
Base64@~0.2.0:
version "0.2.1"
resolved "https://registry.yarnpkg.com/Base64/-/Base64-0.2.1.tgz#ba3a4230708e186705065e66babdd4c35cf60028"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ujpCMHCOGGcFBl5mur3Uw1z2ACg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
JSONStream@^1.0.4:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.3.3"
resolved "https://registry.yarnpkg.com/JSONStream/-/JSONStream-1.3.3.tgz#27b4b8fbbfeab4e71bcf551e7f27be8d952239bf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-3Sp6WZZ/lXl+nTDoGpGWHEpTnnC6X5fnkolYZR6nwIfzbxxvA8utPWe1gCt7i0m9uVGsSz2IS8K8mJ7HmlduMg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
jsonparse "^1.2.0"
through ">=2.2.7 <3"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
JSONStream@^1.2.1, JSONStream@^1.3.4:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "1.3.5"
resolved "https://registry.yarnpkg.com/JSONStream/-/JSONStream-1.3.5.tgz#3208c1f08d3a4d99261ab64f92302bc15e111ca0"
integrity sha512-E+iruNOY8VV9s4JEbe1aNEm6MiszPRr/UfcHMz0TQh1BXSxHK+ASV1R6W4HpjBhSeS+54PIsAMCBmwD06LLsqQ==
dependencies:
jsonparse "^1.2.0"
through ">=2.2.7 <3"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
abbrev@1:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.1.1"
resolved "https://registry.yarnpkg.com/abbrev/-/abbrev-1.1.1.tgz#f8f2c887ad10bf67f634f005b6987fed3179aac8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-nne9/IiQ/hzIhY6pdDnbBtz7DjPTKrY00P/zvPSm5pOFkl6xuGrGnXn/VtTNNfNtAfZ9/1RtehkszU9qcTii0Q==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
accepts@~1.2.12, accepts@~1.2.13:
version "1.2.13"
resolved "https://registry.yarnpkg.com/accepts/-/accepts-1.2.13.tgz#e5f1f3928c6d95fd96558c36ec3d9d0de4a6ecea"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-5fHzkoxtlf2WVYw27D2dDeSm7Oo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
mime-types "~2.1.6"
negotiator "0.5.3"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
accepts@~1.3.0, accepts@~1.3.4, accepts@~1.3.5:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.3.5"
resolved "https://registry.yarnpkg.com/accepts/-/accepts-1.3.5.tgz#eb777df6011723a3b14e8a72c0805c8e86746bd2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-63d99gEXI6OxTopywIBcjoZ0a9I=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
mime-types "~2.1.18"
negotiator "0.6.1"
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
acorn-jsx@^3.0.0:
version "3.0.1"
resolved "https://registry.yarnpkg.com/acorn-jsx/-/acorn-jsx-3.0.1.tgz#afdf9488fb1ecefc8348f6fb22f464e32a58b36b"
integrity sha1-r9+UiPsezvyDSPb7IvRk4ypYs2s=
dependencies:
acorn "^3.0.4"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
acorn@^1.0.3:
version "1.2.2"
resolved "https://registry.yarnpkg.com/acorn/-/acorn-1.2.2.tgz#c8ce27de0acc76d896d2b1fad3df588d9e82f014"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-yM4n3grMdtiW0rH6099YjZ6C8BQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
acorn@^3.0.4:
version "3.3.0"
resolved "https://registry.yarnpkg.com/acorn/-/acorn-3.3.0.tgz#45e37fb39e8da3f25baee3ff5369e2bb5f22017a"
integrity sha1-ReN/s56No/JbruP/U2niu18iAXo=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
acorn@^5.2.1:
version "5.7.1"
resolved "https://registry.yarnpkg.com/acorn/-/acorn-5.7.1.tgz#f095829297706a7c9776958c0afc8930a9b9d9d8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-d+nbxBUGKg7Arpsvbnlq61mc12ek3EY8EQldM3GPAhWJ1UVxC6TDGbIvUMNU6obBX3i1+ptCIzV4vq0gFPEGVQ==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
acorn@^5.5.0:
version "5.7.3"
resolved "https://registry.yarnpkg.com/acorn/-/acorn-5.7.3.tgz#67aa231bf8812974b85235a96771eb6bd07ea279"
integrity sha512-T/zvzYRfbVojPWahDsE5evJdHb3oJoQfFbsrKM7w5Zcs++Tr257tia3BmMP8XYVjp1S9RZXQMh7gao96BlqZOw==
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
acorn@^6.0.5:
version "6.0.5"
resolved "https://registry.yarnpkg.com/acorn/-/acorn-6.0.5.tgz#81730c0815f3f3b34d8efa95cb7430965f4d887a"
integrity sha512-i33Zgp3XWtmZBMNvCr4azvOFeWVw1Rk6p3hfi3LUDvIFraOMywb1kAtrbi+med14m4Xfpqm3zRZMT+c0FNE7kg==
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
acorn@^6.1.1:
version "6.1.1"
resolved "https://registry.yarnpkg.com/acorn/-/acorn-6.1.1.tgz#7d25ae05bb8ad1f9b699108e1094ecd7884adc1f"
integrity sha512-jPTiwtOxaHNaAPg/dmrJ/beuzLRnXtB0kQPQ8JpotKJgTB6rX6c8mlf315941pyjBSaPg8NHXS9fhP4u17DpGA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
add-stream@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/add-stream/-/add-stream-1.0.0.tgz#6a7990437ca736d5e1288db92bd3266d5f5cb2aa"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-anmQQ3ynNtXhKI25K9MmbV9csqo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
adm-zip@0.4.4:
version "0.4.4"
resolved "https://registry.yarnpkg.com/adm-zip/-/adm-zip-0.4.4.tgz#a61ed5ae6905c3aea58b3a657d25033091052736"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ph7VrmkFw66lizplfSUDMJEFJzY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
adm-zip@^0.4.11:
version "0.4.13"
resolved "https://registry.yarnpkg.com/adm-zip/-/adm-zip-0.4.13.tgz#597e2f8cc3672151e1307d3e95cddbc75672314a"
integrity sha512-fERNJX8sOXfel6qCBCMPvZLzENBEhZTzKqg6vrOW5pvoEaQuJhRU4ndTAh6lHOxn1I6jnz2NHra56ZODM751uw==
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
adm-zip@^0.4.9, adm-zip@~0.4.3, adm-zip@~0.4.x:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.4.11"
resolved "https://registry.yarnpkg.com/adm-zip/-/adm-zip-0.4.11.tgz#2aa54c84c4b01a9d0fb89bb11982a51f13e3d62a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-L8vcjDTCOIJk7wFvmlEUN7AsSb8T+2JrdP7KINBjzr24TJ5Mwj590sLu3BC7zNZowvJWa/JtPmD8eJCzdtDWjA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
after@0.8.2:
version "0.8.2"
resolved "https://registry.yarnpkg.com/after/-/after-0.8.2.tgz#fedb394f9f0e02aa9768e702bda23b505fae7e1f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-/ts5T58OAqqXaOcCvaI7UF+ufh8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
agent-base@2:
version "2.1.1"
resolved "https://registry.yarnpkg.com/agent-base/-/agent-base-2.1.1.tgz#d6de10d5af6132d5bd692427d46fc538539094c7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-1t4Q1a9hMtW9aSQn1G/FOFOQlMc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
extend "~3.0.0"
semver "~5.0.1"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
agent-base@4, agent-base@^4.1.0, agent-base@~4.2.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "4.2.1"
resolved "https://registry.yarnpkg.com/agent-base/-/agent-base-4.2.1.tgz#d89e5999f797875674c07d87f260fc41e83e8ca9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-JVwXMr9nHYTUXsBFKUqhJwvlcYU/blreOEUkhNR2eXZIvwd+c+o5V4MgDPKWnMS/56awN3TRzIP+KoPn+roQtg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
es6-promisify "^5.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
agentkeepalive@^3.4.1:
version "3.5.2"
resolved "https://registry.yarnpkg.com/agentkeepalive/-/agentkeepalive-3.5.2.tgz#a113924dd3fa24a0bc3b78108c450c2abee00f67"
integrity sha512-e0L/HNe6qkQ7H19kTlRRqUibEAwDK5AFk6y3PtMsuut2VAH6+Q4xZml1tNDJD7kSAyqmbG/K08K5WEJYtUrSlQ==
dependencies:
humanize-ms "^1.2.1"
build: update angular cli packages to latest beta (#29720) PR Close #29720
2019-04-05 02:38:16 -04:00
ajv@6.10.0:
version "6.10.0"
resolved "https://registry.yarnpkg.com/ajv/-/ajv-6.10.0.tgz#90d0d54439da587cd7e843bfb7045f50bd22bdf1"
integrity sha512-nffhOpkymDECQyR0mnsUtoCE8RlX38G0rYP+wgLWFyZuUyuuojSSvi/+euOiQBIn63whYwYVIIH1TvE3tu4OEg==
dependencies:
fast-deep-equal "^2.0.1"
fast-json-stable-stringify "^2.0.0"
json-schema-traverse "^0.4.1"
uri-js "^4.2.2"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
ajv@^5.1.0:
feat(elements): add schematics (#23298) PR Close #23298
2018-04-03 17:52:33 -04:00
version "5.5.2"
resolved "https://registry.yarnpkg.com/ajv/-/ajv-5.5.2.tgz#73b5eeca3fab653e3d3f9422b341ad42205dc965"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-c7Xuyj+rZT49P5Qis0GtQiBdyWU=
feat(elements): add schematics (#23298) PR Close #23298
2018-04-03 17:52:33 -04:00
dependencies:
co "^4.6.0"
fast-deep-equal "^1.0.0"
fast-json-stable-stringify "^2.0.0"
json-schema-traverse "^0.3.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
ajv@^6.5.2, ajv@^6.5.5:
version "6.8.1"
resolved "https://registry.yarnpkg.com/ajv/-/ajv-6.8.1.tgz#0890b93742985ebf8973cd365c5b23920ce3cb20"
integrity sha512-eqxCp82P+JfqL683wwsL73XmFs1eG6qjw+RD3YHx+Jll1r0jNd4dh8QG9NYAeNGA/hnZjeEDgtTskgJULbxpWQ==
dependencies:
fast-deep-equal "^2.0.1"
fast-json-stable-stringify "^2.0.0"
json-schema-traverse "^0.4.1"
uri-js "^4.2.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
align-text@^0.1.1, align-text@^0.1.3:
version "0.1.4"
resolved "https://registry.yarnpkg.com/align-text/-/align-text-0.1.4.tgz#0cd90a561093f35d0a99256c22b7069433fad117"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-DNkKVhCT810KmSVsIrcGlDP60Rc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
kind-of "^3.0.2"
longest "^1.0.1"
repeat-string "^1.5.2"
amdefine@>=0.0.4:
version "1.0.1"
resolved "https://registry.yarnpkg.com/amdefine/-/amdefine-1.0.1.tgz#4a5282ac164729e93619bcfd3ad151f817ce91f5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-SlKCrBZHKek2Gbz9OtFR+BfOkfU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
amdetective@0.0.2:
version "0.0.2"
resolved "https://registry.yarnpkg.com/amdetective/-/amdetective-0.0.2.tgz#260777ab35a6b9ba6edd1b8d7280d3a8ef4859b0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Jgd3qzWmubpu3RuNcoDTqO9IWbA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
esprima "~1.2.2"
test(upgrade): run tests against multiple AngularJS versions (#22167) Fixes #19332 PR Close #22167
2018-02-15 12:21:18 -05:00
"angular-1.5@npm:angular@1.5":
version "1.5.11"
resolved "https://registry.yarnpkg.com/angular/-/angular-1.5.11.tgz#8c5ba7386f15965c9acf3429f6881553aada30d6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-jFunOG8VllyazzQp9ogVU6raMNY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(upgrade): run tests against AngularJS v1.7.x as well (#25231) PR Close #25231
2018-07-31 08:10:13 -04:00
"angular-1.6@npm:angular@1.6":
version "1.6.10"
resolved "https://registry.yarnpkg.com/angular/-/angular-1.6.10.tgz#eed3080a34d29d0f681ff119b18ce294e3f74826"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-PCZ5/hVdvPQiYyH0VwsPjrErPHRcITnaXxhksceOXgtJeesKHLA7KDu4X/yvcAi+1zdGgGF+9pDxkJvghXI9Wg==
test(upgrade): run tests against AngularJS v1.7.x as well (#25231) PR Close #25231
2018-07-31 08:10:13 -04:00
test(upgrade): run tests against multiple AngularJS versions (#22167) Fixes #19332 PR Close #22167
2018-02-15 12:21:18 -05:00
"angular-mocks-1.5@npm:angular-mocks@1.5":
version "1.5.11"
resolved "https://registry.yarnpkg.com/angular-mocks/-/angular-mocks-1.5.11.tgz#a0e1dd0ea55fd77ee7a757d75536c5e964c86f81"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-oOHdDqVf137np1fXVTbF6WTIb4E=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(upgrade): run tests against AngularJS v1.7.x as well (#25231) PR Close #25231
2018-07-31 08:10:13 -04:00
"angular-mocks-1.6@npm:angular-mocks@1.6":
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.6.10"
resolved "https://registry.yarnpkg.com/angular-mocks/-/angular-mocks-1.6.10.tgz#6a139e43c461d0c9a5a1acebc91e63db16031176"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-1865/NmqHNogibNoglY1MGBjx882iu2hI46BBhYDWyz0C4TDM5ER8H8SnYwQKUUG4RXMDsJizszEQ2BEoYKV9w==
test(upgrade): run tests against multiple AngularJS versions (#22167) Fixes #19332 PR Close #22167
2018-02-15 12:21:18 -05:00
test(upgrade): run tests against AngularJS v1.7.x as well (#25231) PR Close #25231
2018-07-31 08:10:13 -04:00
"angular-mocks@npm:angular-mocks@1.7":
version "1.7.2"
resolved "https://registry.yarnpkg.com/angular-mocks/-/angular-mocks-1.7.2.tgz#8a2bc7a7ce355697a48ab00e548b88e78f71fa52"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-yj9eWPG0usXX2eDTWM6YOmAGKraT7qHwuD+NrNyaR+mtrNr2ls77WuWXTjE1hZpmxTaGj4+R1nMY696XZn740Q==
test(upgrade): run tests against AngularJS v1.7.x as well (#25231) PR Close #25231
2018-07-31 08:10:13 -04:00
"angular@npm:angular@1.7":
version "1.7.2"
resolved "https://registry.yarnpkg.com/angular/-/angular-1.7.2.tgz#687b955dbe5c533f8d73460461707af00360251f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-JcKKJbBdybUsmQ6x1M3xWyTYQ/ioVKJhSByEAjqrhmlOfvMFdhfMqAx5KIo8rLGk4DFolYPcCSgssjgTVjCtRQ==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
ansi-align@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/ansi-align/-/ansi-align-2.0.0.tgz#c36aeccba563b89ceb556f3690f0b1d9e3547f7f"
integrity sha1-w2rsy6VjuJzrVW82kPCx2eNUf38=
dependencies:
string-width "^2.0.0"
style: update gulp task to format untracked and diff files separately (#24969) PR Close #24969
2018-09-10 21:19:14 -04:00
ansi-colors@^1.0.1:
version "1.1.0"
build: secure yarn lock files (#31640) See https://yarnpkg.com/blog/2019/07/12/recommended-security-update/ PR Close #31640
2019-07-18 20:34:37 -04:00
resolved "https://registry.npmjs.org/ansi-colors/-/ansi-colors-1.1.0.tgz#6374b4dd5d4718ff3ce27a671a3b1cad077132a9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-SFKX67auSNoVR38N3L+nvsPjOE0bybKTYbkf5tRvushrAPQ9V75huw0ZxBkKVeRU9kqH3d6HA4xTckbwZ4ixmA==
style: update gulp task to format untracked and diff files separately (#24969) PR Close #24969
2018-09-10 21:19:14 -04:00
dependencies:
ansi-wrap "^0.1.0"
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
ansi-cyan@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/ansi-cyan/-/ansi-cyan-0.1.1.tgz#538ae528af8982f28ae30d86f2f17456d2609873"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-U4rlKK+JgvKK4w2G8vF0VtJgmHM=
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
dependencies:
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
ansi-wrap "0.1.0"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
ansi-escapes@^1.1.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/ansi-escapes/-/ansi-escapes-1.4.0.tgz#d3a8a83b319aa67793662b13e761c7911422306e"
integrity sha1-06ioOzGapneTZisT52HHkRQiMG4=
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
ansi-escapes@^3.2.0:
version "3.2.0"
resolved "https://registry.yarnpkg.com/ansi-escapes/-/ansi-escapes-3.2.0.tgz#8780b98ff9dbf5638152d1f1fe5c1d7b4442976b"
integrity sha512-cBhpre4ma+U0T1oM5fXg7Dy1Jw7zzwv7lt/GoCpr+hDQJoYnKVPLL4dCvSEFMmQurOQvSrwT7SL/DAlhBI97RQ==
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
ansi-gray@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/ansi-gray/-/ansi-gray-0.1.1.tgz#2962cf54ec9792c48510a3deb524436861ef7251"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-KWLPVOyXksSFEKPetSRDaGHvclE=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
ansi-wrap "0.1.0"
ansi-red@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/ansi-red/-/ansi-red-0.1.1.tgz#8c638f9d1080800a353c9c28c8a81ca4705d946c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-jGOPnRCAgAo1PJwoyKgcpHBdlGw=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
ansi-wrap "0.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ansi-regex@^2.0.0, ansi-regex@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-2.1.1.tgz#c3b33ab5ee360d86e0e628f0468ae7ef27d654df"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-w7M6te42DYbg5ijwRorn7yfWVN8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ansi-regex@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-3.0.0.tgz#ed0317c322064f79466c02966bddb605ab37d998"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-7QMXwyIGT3lGbAKWa922Bas32Zg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
ansi-regex@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-4.0.0.tgz#70de791edf021404c3fd615aa89118ae0432e5a9"
integrity sha512-iB5Dda8t/UqpPI/IjsejXu5jOGDrzn41wJyljwPH65VCIbk6+1BzFIMJGFwTNrYXT1CrD+B4l19U7awiQ8rk7w==
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
ansi-regex@^4.1.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-4.1.0.tgz#8b9f8f08cf1acb843756a839ca8c7e3168c51997"
integrity sha512-1apePfXM1UOSqw0o9IiFAovVz9M5S1Dg+4TrDwfMewQ6p/rmMueb7tWZjQ1rx4Loy1ArBggoqGpfqqdI4rondg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ansi-styles@^2.2.1:
version "2.2.1"
resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-2.2.1.tgz#b432dd3358b634cf75e1e4664368240533c1ddbe"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-tDLdM1i2NM914eRmQ2gkBTPB3b4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
ansi-styles@^3.2.1:
version "3.2.1"
resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-3.2.1.tgz#41fbb20243e50b12be0f04b8dedbf07520ce841d"
integrity sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==
dependencies:
color-convert "^1.9.0"
style: update gulp task to format untracked and diff files separately (#24969) PR Close #24969
2018-09-10 21:19:14 -04:00
ansi-wrap@0.1.0, ansi-wrap@^0.1.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.1.0"
resolved "https://registry.yarnpkg.com/ansi-wrap/-/ansi-wrap-0.1.0.tgz#a82250ddb0015e9a27ca82e82ea603bbfa45efaf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-qCJQ3bABXponyoLoLqYDu/pF768=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
any-promise@^1.0.0, any-promise@^1.1.0, any-promise@~1.3.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/any-promise/-/any-promise-1.3.0.tgz#abc6afeedcea52e809cdc0376aed3ce39635d17f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-q8av7tzqUugJzcA3au0845Y10X8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
any-promise@~0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/any-promise/-/any-promise-0.1.0.tgz#830b680aa7e56f33451d4b049f3bd8044498ee27"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-gwtoCqflbzNFHUsEnzvYBESY7ic=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
any-shell-escape@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/any-shell-escape/-/any-shell-escape-0.1.1.tgz#d55ab972244c71a9a5e1ab0879f30bf110806959"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-1Vq5ciRMcaml4asIefML8RCAaVk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
anymatch@^1.3.0:
version "1.3.2"
resolved "https://registry.yarnpkg.com/anymatch/-/anymatch-1.3.2.tgz#553dcb8f91e3c889845dfdba34c77721b90b9d7a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-0XNayC8lTHQ2OI8aljNCN3sSx6hsr/1+rlcDAotXJR7C1oZZHCNsfpbKwMjRA3Uqb5tF1Rae2oloTr4xpq+WjA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
micromatch "^2.1.5"
normalize-path "^2.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
anymatch@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/anymatch/-/anymatch-2.0.0.tgz#bcb24b4f37934d9aa7ac17b4adaf89e7c76ef2eb"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-5teOsQWABXHHBFP9y3skS5P3d/WfWXpv3FUpy+LorMrNYaT9pI4oLMQX7jzQ2KklNpGpWHzdCXTDT2Y3XGlZBw==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
micromatch "^3.1.4"
normalize-path "^2.1.1"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
aproba@^1.0.3, aproba@^1.1.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/aproba/-/aproba-1.2.0.tgz#6802e6264efd18c790a1b0d517f0f2627bf2c94a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-Y9J6ZjXtoYh8RnXVCMOU/ttDmk1aBjunq9vO0ta5x85WDQiQfUF9sIPBITdbiiIVcBo03Hi3jMxigBtsddlXRw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
archiver-utils@^1.0.0, archiver-utils@^1.3.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/archiver-utils/-/archiver-utils-1.3.0.tgz#e50b4c09c70bf3d680e32ff1b7994e9f9d895174"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-5QtMCccL89aA4y/xt5lOn52JUXQ=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
glob "^7.0.0"
graceful-fs "^4.1.0"
lazystream "^1.0.0"
lodash "^4.8.0"
normalize-path "^2.0.0"
readable-stream "^2.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
archiver@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/archiver/-/archiver-2.1.1.tgz#ff662b4a78201494a3ee544d3a33fe7496509ebc"
integrity sha1-/2YrSnggFJSj7lRNOjP+dJZQnrw=
dependencies:
archiver-utils "^1.3.0"
async "^2.0.0"
buffer-crc32 "^0.2.1"
glob "^7.0.0"
lodash "^4.8.0"
readable-stream "^2.0.0"
tar-stream "^1.5.0"
zip-stream "^1.2.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
archiver@~1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/archiver/-/archiver-1.0.1.tgz#aaffd0fda3e03c77ee45169a781b4d9be5f3f25f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-qv/Q/aPgPHfuRRaaeBtNm+Xz8l8=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
archiver-utils "^1.0.0"
async "^2.0.0"
buffer-crc32 "^0.2.1"
glob "^7.0.0"
lodash "^4.8.0"
readable-stream "^2.0.0"
tar-stream "^1.5.0"
zip-stream "^1.0.0"
archiver@~1.3.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/archiver/-/archiver-1.3.0.tgz#4f2194d6d8f99df3f531e6881f14f15d55faaf22"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-TyGU1tj5nfP1MeaIHxTxXVX6ryI=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
archiver-utils "^1.3.0"
async "^2.0.0"
buffer-crc32 "^0.2.1"
glob "^7.0.0"
lodash "^4.8.0"
readable-stream "^2.0.0"
tar-stream "^1.5.0"
walkdir "^0.0.11"
zip-stream "^1.1.0"
archy@^1.0.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.0"
resolved "https://registry.yarnpkg.com/archy/-/archy-1.0.0.tgz#f9c8c13757cc1dd7bc379ac77b2c62a5c2868c40"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+cjBN1fMHde8N5rHeyxipcKGjEA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
are-we-there-yet@~1.1.2:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.1.5"
resolved "https://registry.yarnpkg.com/are-we-there-yet/-/are-we-there-yet-1.1.5.tgz#4b35c2944f062a8bfcda66410760350fe9ddfc21"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-5hYdAkZlcG8tOLujVDTgCT+uPX0VnpAH28gWsLfzpXYm7wP6mp5Q/gYyR7YQ0cKVJcXJnl3j2kpBan13PtQf6w==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
delegates "^1.0.0"
readable-stream "^2.0.6"
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
argparse@~1.0.9:
version "1.0.10"
resolved "https://registry.yarnpkg.com/argparse/-/argparse-1.0.10.tgz#bcd6791ea5ae09725e17e5ad988134cd40b3d911"
integrity sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==
dependencies:
sprintf-js "~1.0.2"
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
arr-diff@^1.0.1:
version "1.1.0"
resolved "https://registry.yarnpkg.com/arr-diff/-/arr-diff-1.1.0.tgz#687c32758163588fef7de7b36fabe495eb1a399a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-aHwydYFjWI/vfeezb6vklesaOZo=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
arr-flatten "^1.0.1"
array-slice "^0.2.3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
arr-diff@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/arr-diff/-/arr-diff-2.0.0.tgz#8f3b827f955a8bd669697e4a4256ac3ceae356cf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-jzuCf5Vai9ZpaX5KQlasPOrjVs8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
arr-flatten "^1.0.1"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
arr-diff@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/arr-diff/-/arr-diff-4.0.0.tgz#d6461074febfec71e7e15235761a329a5dc7c520"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-1kYQdP6/7HHn4VI1dhoyml3HxSA=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
arr-flatten@^1.0.1, arr-flatten@^1.1.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.1.0"
resolved "https://registry.yarnpkg.com/arr-flatten/-/arr-flatten-1.1.0.tgz#36048bbff4e7b47e136644316c99669ea5ae91f1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-L3hKV5R/p5o81R7O02IGnwpDmkp6E982XhtbuwSe3O4qOtMMMtodicASA1Cny2U+aCXcNpml+m4dPsvsJ3jatg==
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
arr-union@^2.0.1:
version "2.1.0"
resolved "https://registry.yarnpkg.com/arr-union/-/arr-union-2.1.0.tgz#20f9eab5ec70f5c7d215b1077b1c39161d292c7d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-IPnqtexw9cfSFbEHexw5Fh0pLH0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
arr-union@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/arr-union/-/arr-union-3.1.0.tgz#e39b09aea9def866a8f206e288af63919bae39c4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-45sJrqne+Gao8gbiiK9jkZuuOcQ=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
array-differ@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/array-differ/-/array-differ-1.0.0.tgz#eff52e3758249d33be402b8bb8e564bb2b5d4031"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-7/UuN1gknTO+QCuLuOVkuytdQDE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
array-each@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/array-each/-/array-each-1.0.1.tgz#a794af0c05ab1752846ee753a1f211a05ba0c44f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-p5SvDAWrF1KEbudTofIRoFugxE8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
array-filter@~0.0.0:
version "0.0.1"
resolved "https://registry.yarnpkg.com/array-filter/-/array-filter-0.0.1.tgz#7da8cf2e26628ed732803581fd21f67cacd2eeec"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-fajPLiZijtcygDWB/SH2fKzS7uw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
array-find-index@^1.0.1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/array-find-index/-/array-find-index-1.0.2.tgz#df010aa1287e164bbda6f9723b0a96a1ec4187a1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-3wEKoSh+Fku9pvlyOwqWoexBh6E=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
array-flatten@1.1.1, array-flatten@^1.0.0:
version "1.1.1"
resolved "https://registry.yarnpkg.com/array-flatten/-/array-flatten-1.1.1.tgz#9a5f699051b1e7073328f2a008968b64ea2955d2"
integrity sha1-ml9pkFGx5wczKPKgCJaLZOopVdI=
array-flatten@2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/array-flatten/-/array-flatten-2.1.1.tgz#426bb9da84090c1838d812c8150af20a8331e296"
integrity sha1-Qmu52oQJDBg42BLIFQryCoMx4pY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
array-ify@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/array-ify/-/array-ify-1.0.0.tgz#9e528762b4a9066ad163a6962a364418e9626ece"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nlKHYrSpBmrRY6aWKjZEGOlibs4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
array-map@~0.0.0:
version "0.0.0"
resolved "https://registry.yarnpkg.com/array-map/-/array-map-0.0.0.tgz#88a2bab73d1cf7bcd5c1b118a003f66f665fa662"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-iKK6tz0c97zVwbEYoAP2b2ZfpmI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
array-reduce@~0.0.0:
version "0.0.0"
resolved "https://registry.yarnpkg.com/array-reduce/-/array-reduce-0.0.0.tgz#173899d3ffd1c7d9383e4479525dbe278cab5f2b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-FziZ0//Rx9k4PkR5Ul2+J4yrXys=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
array-slice@^0.2.3:
version "0.2.3"
resolved "https://registry.yarnpkg.com/array-slice/-/array-slice-0.2.3.tgz#dd3cfb80ed7973a75117cdac69b0b99ec86186f5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-3Tz7gO15c6dRF82sabC5nshhhvU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
array-slice@^1.0.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.1.0"
resolved "https://registry.yarnpkg.com/array-slice/-/array-slice-1.1.0.tgz#e368ea15f89bc7069f7ffb89aec3a6c7d4ac22d4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-B1qMD3RBP7O8o0H2KbrXDyB0IccejMF15+87Lvlor12ONPRHP6gTjXMNkt/d3ZuOGbAe66hFmaCfECI24Ufp6w==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
array-union@^1.0.1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/array-union/-/array-union-1.0.2.tgz#9a34410e4f4e3da23dea375be5be70f24778ec39"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-mjRBDk9OPaI96jdb5b5w8kd47Dk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
array-uniq "^1.0.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
array-uniq@^1.0.1, array-uniq@^1.0.2, array-uniq@^1.0.3:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.3"
resolved "https://registry.yarnpkg.com/array-uniq/-/array-uniq-1.0.3.tgz#af6ac877a25cc7f74e058894753858dfdb24fdb6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-r2rId6Jcx/dOBYiUdThY39sk/bY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
array-unique@^0.2.1:
version "0.2.1"
resolved "https://registry.yarnpkg.com/array-unique/-/array-unique-0.2.1.tgz#a1d97ccafcbc2625cc70fadceb36a50c58b01a53"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-odl8yvy8JiXMcPrc6zalDFiwGlM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
array-unique@^0.3.2:
version "0.3.2"
resolved "https://registry.yarnpkg.com/array-unique/-/array-unique-0.3.2.tgz#a894b75d4bc4f6cd679ef3244a9fd8f46ae2d428"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-qJS3XUvE9s1nnvMkSp/Y9Gri1Cg=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
arraybuffer.slice@~0.0.7:
version "0.0.7"
resolved "https://registry.yarnpkg.com/arraybuffer.slice/-/arraybuffer.slice-0.0.7.tgz#3bbc4275dd584cc1b10809b89d4e8b63a69e7675"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-wGUIVQXuehL5TCqQun8OW81jGzAWycqzFF8lFp+GOM5BXLYj3bKNsYC4daB7n6XjCqxQA/qgTJ+8ANR3acjrog==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
arrify@^1.0.0, arrify@^1.0.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/arrify/-/arrify-1.0.1.tgz#898508da2226f380df904728456849c1501a4b0d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-iYUI2iIm84DfkEcoRWhJwVAaSw0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
as-array@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/as-array/-/as-array-1.0.0.tgz#28a6eeeaa5729f1f4eca2047df5e9de1abda0ed1"
integrity sha1-KKbu6qVynx9OyiBH316d4avaDtE=
dependencies:
lodash.isarguments "2.4.x"
lodash.isobject "^2.4.1"
lodash.values "^2.4.1"
as-array@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/as-array/-/as-array-2.0.0.tgz#4f04805d87f8fce8e511bc2108f8e5e3a287d547"
integrity sha1-TwSAXYf4/OjlEbwhCPjl46KH1Uc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
asn1@~0.2.3:
version "0.2.3"
resolved "https://registry.yarnpkg.com/asn1/-/asn1-0.2.3.tgz#dac8787713c9966849fc8180777ebe9c1ddf3b86"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-2sh4dxPJlmhJ/IGAd36+nB3fO4Y=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
assert-plus@1.0.0, assert-plus@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/assert-plus/-/assert-plus-1.0.0.tgz#f12e0f3c5d77b0b1cdd9146942e4e96c1e4dd525"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8S4PPF13sLHN2RRpQuTpbB5N1SU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
assert-plus@^0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/assert-plus/-/assert-plus-0.2.0.tgz#d74e1b87e7affc0db8aadb7021f3fe48101ab234"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-104bh+ev/A24qttwIfP+SBAasjQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
assert@^1.1.1:
version "1.4.1"
resolved "https://registry.yarnpkg.com/assert/-/assert-1.4.1.tgz#99912d591836b5a6f5b345c0f07eefc08fc65d91"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-mZEtWRg2tab1s0XA8H7vwI/GXZE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
util "0.10.3"
build(bazel): remove @ts-api-guardian_deps yarn_install (#29799) PR Close #29799
2019-04-09 21:08:13 -04:00
assertion-error@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/assertion-error/-/assertion-error-1.1.0.tgz#e60b6b0e8f301bd97e5375215bda406c85118c0b"
integrity sha512-jgsaNduz+ndvGyFt3uSuWqvy4lCnIJiovtouQN5JZHOKCS2QuhEdbcQHFhVksz2N2U9hXJo8odG7ETyWlEeuDw==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
assign-symbols@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/assign-symbols/-/assign-symbols-1.0.0.tgz#59667f41fadd4f20ccbc2bb96b8d4f7f78ec0367"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-WWZ/QfrdTyDMvCu5a41Pf3jsA2c=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ast-types@0.9.6:
version "0.9.6"
resolved "https://registry.yarnpkg.com/ast-types/-/ast-types-0.9.6.tgz#102c9e9e9005d3e7e3829bf0c4fa24ee862ee9b9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ECyenpAF0+fjgpvwxPok7oYu6bk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
ast-types@^0.7.2:
version "0.7.8"
resolved "https://registry.yarnpkg.com/ast-types/-/ast-types-0.7.8.tgz#902d2e0d60d071bdcd46dc115e1809ed11c138a9"
integrity sha1-kC0uDWDQcb3NRtwRXhgJ7RHBOKk=
build(compiler-cli): upgrade chokidar to latest version (#28797) Fixes #28771 PR Close #28797
2019-02-18 08:11:03 -05:00
async-each@^1.0.0, async-each@^1.0.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/async-each/-/async-each-1.0.1.tgz#19d386a1d9edc6e7c1c85d388aedbcc56d33602d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-GdOGodntxufByF04iu28xW0zYC0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
async-limiter@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/async-limiter/-/async-limiter-1.0.0.tgz#78faed8c3d074ab81f22b4e985d79e8738f720f8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-jp/uFnooOiO+L211eZOoSyzpOITMXx1rBITauYykG3BRYPu8h0UcxsPNB04RR5vo4Tyz3+ay17tR6JVf9qzYWg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
async@1.2.x:
version "1.2.1"
resolved "https://registry.yarnpkg.com/async/-/async-1.2.1.tgz#a4816a17cd5ff516dfa2c7698a453369b9790de0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-pIFqF81f9RbfosdpikUzabl5DeA=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
async@2.6.0:
version "2.6.0"
resolved "https://registry.yarnpkg.com/async/-/async-2.6.0.tgz#61a29abb6fcc026fea77e56d1c6ec53a795951f4"
integrity sha512-xAfGg1/NTLBBKlHFmnd7PlmUW9KhVQIUuSrYem9xzFUZy13ScvtyGGejaae9iAVRiRq9+Cx7DPFaAAhCpyxyPw==
dependencies:
lodash "^4.14.0"
async@^0.9.0, async@~0.9.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.9.2"
resolved "https://registry.yarnpkg.com/async/-/async-0.9.2.tgz#aea74d5e61c1f899613bf64bda66d4c78f2fd17d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-rqdNXmHB+JlhO/ZL2mbUx48v0X0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
async@^1.3.0, async@^1.4.0, async@^1.5.2, async@~1.5.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.5.2"
resolved "https://registry.yarnpkg.com/async/-/async-1.5.2.tgz#ec6a61ae56480c0c3cb241c95618e20892f9672a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-7GphrlZIDAw8skHJVhjiCJL5Zyo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
async@^2.0.0, async@^2.0.1, async@^2.1.2, async@^2.3.0, async@^2.4.0:
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
version "2.6.1"
resolved "https://registry.yarnpkg.com/async/-/async-2.6.1.tgz#b245a23ca71930044ec53fa46aa00a3e87c6a610"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-fNEiL2+AZt6AlAw/29Cr0UDe4sRAHCpEHh54WMz+Bb7QfNcFw4h3loofyJpLeQs4Yx7yuqu/2dLgM5hKOs6HlQ==
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
dependencies:
lodash "^4.17.10"
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
async@^2.6.2:
version "2.6.3"
resolved "https://registry.yarnpkg.com/async/-/async-2.6.3.tgz#d72625e2344a3656e3a3ad4fa749fa83299d82ff"
integrity sha512-zflvls11DCy+dQWzTW2dzuilv8Z5X/pjfmZOWba6TNIVDm+2UDaJmXSOXlasHKfNBs8oo3M0aT50fDEWfKZjXg==
dependencies:
lodash "^4.17.14"
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
async@~0.2.6:
version "0.2.10"
resolved "https://registry.yarnpkg.com/async/-/async-0.2.10.tgz#b6bbe0b0674b9d719708ca38de8c237cb526c3d1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-trvgsGdLnXGXCMo43owjfLUmw9E=
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
async@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/async/-/async-1.0.0.tgz#f8fc04ca3a13784ade9e1641af98578cfbd647a9"
integrity sha1-+PwEyjoTeErenhZBr5hXjPvWR6k=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
async@~2.4.1:
version "2.4.1"
resolved "https://registry.yarnpkg.com/async/-/async-2.4.1.tgz#62a56b279c98a11d0987096a01cc3eeb8eb7bbd7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-YqVrJ5yYoR0JhwlqAcw+6463u9c=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
lodash "^4.14.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
asynckit@^0.4.0:
version "0.4.0"
resolved "https://registry.yarnpkg.com/asynckit/-/asynckit-0.4.0.tgz#c79ed97f7f34cb8f2ba1bc9790bcc366474b4b79"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-x57Zf380y48robyXkLzDZkdLS3k=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
atob@^2.1.1:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "2.1.2"
resolved "https://registry.yarnpkg.com/atob/-/atob-2.1.2.tgz#6d9517eb9e030d2436666651e86bd9f6f13533c9"
integrity sha512-Wm6ukoaOGJi/73p/cl2GvLjTI5JM1k/O14isD73YML8StrH/7/lRFgmg8nICZgD3bZZvjwCGxtMOD3wWNAu8cg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
aws-sign2@~0.6.0:
version "0.6.0"
resolved "https://registry.yarnpkg.com/aws-sign2/-/aws-sign2-0.6.0.tgz#14342dd38dbcc94d0e5b87d763cd63612c0e794f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-FDQt0428yU0OW4fXY81jYSwOeU8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
aws-sign2@~0.7.0:
version "0.7.0"
resolved "https://registry.yarnpkg.com/aws-sign2/-/aws-sign2-0.7.0.tgz#b46e890934a9591f2d2f6f86d7e6a9f1b3fe76a8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-tG6JCTSpWR8tL2+G1+ap8bP+dqg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
aws4@^1.2.1, aws4@^1.6.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.7.0"
resolved "https://registry.yarnpkg.com/aws4/-/aws4-1.7.0.tgz#d4d0e9b9dbfca77bf08eeb0a8a471550fe39e289"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-32NDda82rhwD9/JBCCkB+MRYDp0oSvlo2IL6rQWA10PQi7tDUM3eqMSltXmY+Oyl/7N3P3qNtAlv7X0d9bI28w==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
aws4@^1.8.0:
version "1.8.0"
resolved "https://registry.yarnpkg.com/aws4/-/aws4-1.8.0.tgz#f0e003d9ca9e7f59c7a508945d7b2ef9a04a542f"
integrity sha512-ReZxvNHIOv88FlT7rxcXIIC0fPt4KZqZbOlivyWtXLt8ESx84zd3kMC6iK5jVeS2qt+g7ftS7ye4fi06X5rtRQ==
axios@^0.18.0:
version "0.18.0"
resolved "https://registry.yarnpkg.com/axios/-/axios-0.18.0.tgz#32d53e4851efdc0a11993b6cd000789d70c05102"
integrity sha1-MtU+SFHv3AoRmTts0AB4nXDAUQI=
dependencies:
follow-redirects "^1.3.0"
is-buffer "^1.1.5"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
babel-code-frame@^6.22.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "6.26.0"
resolved "https://registry.yarnpkg.com/babel-code-frame/-/babel-code-frame-6.26.0.tgz#63fd43f7dc1e3bb7ce35947db8fe369a3f58c74b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Y/1D99weO7fONZR9uP42mj9Yx0s=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
chalk "^1.1.3"
esutils "^2.0.2"
js-tokens "^3.0.2"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
babel-polyfill@6.16.0:
version "6.16.0"
resolved "https://registry.yarnpkg.com/babel-polyfill/-/babel-polyfill-6.16.0.tgz#2d45021df87e26a374b6d4d1a9c65964d17f2422"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-LUUCHfh+JqN0ttTRqcZZZNF/JCI=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
babel-runtime "^6.9.1"
core-js "^2.4.0"
regenerator-runtime "^0.9.5"
babel-runtime@^6.9.1:
version "6.26.0"
resolved "https://registry.yarnpkg.com/babel-runtime/-/babel-runtime-6.26.0.tgz#965c7058668e82b55d7bfe04ff2337bc8b5647fe"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-llxwWGaOgrVde/4E/yM3vItWR/4=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
core-js "^2.4.0"
regenerator-runtime "^0.11.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
backo2@1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/backo2/-/backo2-1.0.2.tgz#31ab1ac8b129363463e35b3ebb69f4dfcfba7947"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-MasayLEpNjRj41s+u2n038+6eUc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
balanced-match@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/balanced-match/-/balanced-match-1.0.0.tgz#89b4d199ab2bee49de164ea02b89ce462d71b767"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ibTRmasr7kneFk6gK4nORi1xt2c=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
base62@0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/base62/-/base62-0.1.1.tgz#7b4174c2f94449753b11c2651c083da841a7b084"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-e0F0wvlESXU7EcJlHAg9qEGnsIQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
base64-arraybuffer@0.1.5:
version "0.1.5"
resolved "https://registry.yarnpkg.com/base64-arraybuffer/-/base64-arraybuffer-0.1.5.tgz#73926771923b5a19747ad666aa5cd4bf9c6e9ce8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-c5JncZI7Whl0etZmqlzUv5xunOg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
base64-js@1.2.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.2.1"
resolved "https://registry.yarnpkg.com/base64-js/-/base64-js-1.2.1.tgz#a91947da1f4a516ea38e5b4ec0ec3773675e0886"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-dwVUVIXsBZXwTuwnXI9RK8sBmgq09NDHzyR9SAph9eqk76gKK2JSQmZARC2zRC81JC2QTtxD0ARU5qTS25gIGw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
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 14:57:36 -04:00
base64-js@^1.0.2, base64-js@^1.1.2:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.3.0"
resolved "https://registry.yarnpkg.com/base64-js/-/base64-js-1.3.0.tgz#cab1e6118f051095e58b5281aea8c1cd22bfc0e3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-ccav/yGvoa80BQDljCxsmmQ3Xvx60/UpBIij5QN21W3wBi/hhIC9OoO+KLpu9IJTS9j4DRVJ3aDDF9cMSoa2lw==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
base64-url@1.2.1:
version "1.2.1"
resolved "https://registry.yarnpkg.com/base64-url/-/base64-url-1.2.1.tgz#199fd661702a0e7b7dcae6e0698bb089c52f6d78"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-GZ/WYXAqDnt9yubgaYuwicUvbXg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
base64id@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/base64id/-/base64id-1.0.0.tgz#47688cb99bb6804f0e06d3e763b1c32e57d8e6b6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-R2iMuZu2gE8OBtPnY7HDLlfY5rY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
base@^0.11.1:
version "0.11.2"
resolved "https://registry.yarnpkg.com/base/-/base-0.11.2.tgz#7bde5ced145b6d551a90db87f83c558b4eb48a8f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-5T6P4xPgpp0YDFvSWwEZ4NoE3aM4QBQXDzmVbraCkFj8zHM+mba8SyqB5DbZWyR7mYHo6Y7BdQo3MoA4m0TeQg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
cache-base "^1.0.1"
class-utils "^0.3.5"
component-emitter "^1.2.1"
define-property "^1.0.0"
isobject "^3.0.1"
mixin-deep "^1.2.0"
pascalcase "^0.1.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
basic-auth-connect@1.0.0, basic-auth-connect@^1.0.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.0"
resolved "https://registry.yarnpkg.com/basic-auth-connect/-/basic-auth-connect-1.0.0.tgz#fdb0b43962ca7b40456a7c2bb48fe173da2d2122"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-/bC0OWLKe0BFanwrtI/hc9otISI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
basic-auth@~1.0.3:
version "1.0.4"
resolved "https://registry.yarnpkg.com/basic-auth/-/basic-auth-1.0.4.tgz#030935b01de7c9b94a824b29f3fccb750d3a5290"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Awk1sB3nyblKgksp8/zLdQ06UpA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
basic-auth@~2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/basic-auth/-/basic-auth-2.0.1.tgz#b998279bf47ce38344b4f3cf916d4679bbf51e3a"
integrity sha512-NF+epuEdnUYVlGuhaxbbq+dvJttwLnGY+YixlXlME5KpQ5W3CnXA5cVTneY3SPbPDRkcjMbifrwmFYcClgOZeg==
dependencies:
safe-buffer "5.1.2"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
batch@0.5.3:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.5.3"
resolved "https://registry.yarnpkg.com/batch/-/batch-0.5.3.tgz#3f3414f380321743bfc1042f9a83ff1d5824d464"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-PzQU84AyF0O/wQQvmoP/HVgk1GQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
bcrypt-pbkdf@^1.0.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/bcrypt-pbkdf/-/bcrypt-pbkdf-1.0.2.tgz#a4301d389b6a43f9b67ff3ca11a3f6637e360e9e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-pDAdOJtqQ/m2f/PKEaP2Y342Dp4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
tweetnacl "^0.14.3"
beeper@^1.0.0:
version "1.1.1"
resolved "https://registry.yarnpkg.com/beeper/-/beeper-1.1.1.tgz#e6d5ea8c5dad001304a70b22638447f69cb2f809"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-5tXqjF2tABMEpwsiY4RH9pyy+Ak=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
better-assert@~1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/better-assert/-/better-assert-1.0.2.tgz#40866b9e1b9e0b55b481894311e68faffaebc522"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-QIZrnhueC1W0gYlDEeaPr/rrxSI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
callsite "1.0.0"
big.js@^3.1.3:
version "3.2.0"
resolved "https://registry.yarnpkg.com/big.js/-/big.js-3.2.0.tgz#a5fc298b81b9e0dca2e458824784b65c52ba588e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-+hN/Zh2D08Mx65pZ/4g5bsmNiZUuChDiQfTUQ7qJr4/kuopCr88xZsAXv6mBoZEsUI4OuGHlX59qE94K2mMW8Q==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update version of Angular CLI and Build Optimizer used for tests (#28372) PR Close #28372
2019-01-25 11:33:22 -05:00
big.js@^5.2.2:
version "5.2.2"
resolved "https://registry.yarnpkg.com/big.js/-/big.js-5.2.2.tgz#65f0af382f578bcdc742bd9c281e9cb2d7768328"
integrity sha512-vyL2OymJxmarO8gxMr0mhChsO9QGwhynfuu4+MHTAW6czfq9humCB7rKpUjDd9YUiDPU4mzpyupFSvOClAwbmQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
binary-extensions@^1.0.0:
test(bazel): Upgrade CLI dependencies for schematics test (#28872) This commit makes the integration test for bazel-schematics more robust by removing package.json.replace. Instead of replacing the file, the test script now just overrides Angular packages with the local ones. This commit also fixes running the test locally by providing default argument for CI_CHROMEDRIVER_VERSION_ARG. PR Close #28872
2019-02-20 12:58:42 -05:00
version "1.13.0"
resolved "https://registry.yarnpkg.com/binary-extensions/-/binary-extensions-1.13.0.tgz#9523e001306a32444b907423f1de2164222f6ab1"
integrity sha512-EgmjVLMn22z7eGGv3kcnHwSnJXmFHjISTY9E/S5lIcTD3Oxw05QTcBLNkJFzcb3cNueUdF/IN4U+d78V0zO8Hw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"binary@>= 0.3.0 < 1", binary@^0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/binary/-/binary-0.3.0.tgz#9f60553bc5ce8c3386f3b553cff47462adecaa79"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-n2BVO8XOjDOG87VTz/R0Yq3sqnk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
buffers "~0.1.1"
chainsaw "~0.1.0"
bl@^1.0.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.2.2"
resolved "https://registry.yarnpkg.com/bl/-/bl-1.2.2.tgz#a160911717103c07410cef63ef51b397c025af9c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-e8tQYnZodmebYDWGH7KMRvtzKXaJHx3BbilrgZCfvyLUYdKpK1t5PSPmpkny/SgiTSCnjfLW7v5rlONXVFkQEA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
readable-stream "^2.3.5"
safe-buffer "^5.1.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
bl@~1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/bl/-/bl-1.1.2.tgz#fdca871a99713aa00d19e3bbba41c44787a65398"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-/cqHGplxOqANGeO7ukHER4emU5g=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
readable-stream "~2.0.5"
blob@0.0.4:
version "0.0.4"
resolved "https://registry.yarnpkg.com/blob/-/blob-0.0.4.tgz#bcf13052ca54463f30f9fc7e95b9a47630a94921"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-vPEwUspURj8w+fx+lbmkdjCpSSE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
blocking-proxy@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/blocking-proxy/-/blocking-proxy-1.0.1.tgz#81d6fd1fe13a4c0d6957df7f91b75e98dac40cb2"
integrity sha512-KE8NFMZr3mN2E0HcvCgRtX7DjhiIQrwle+nSVJVC/yqFb9+xznHl2ZcoBp2L9qzkI4t4cBFJ1efXF8Dwi132RA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
minimist "^1.2.0"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
bluebird@^3.3.0:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "3.5.1"
resolved "https://registry.yarnpkg.com/bluebird/-/bluebird-3.5.1.tgz#d9551f9de98f1fcda1e683d17ee91a0602ee2eb9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-MKiLiV+I1AA596t9w1sQJ8jkiSr5+ZKi0WKrYGUn6d1Fx+Ij4tIj+m2WMQSGczs5jZVxV339chE8iwk6F64wjA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Cleanup bazel-schematics integration test (#28351) PR Close #28351
2019-01-24 14:51:20 -05:00
bluebird@^3.5.1, bluebird@^3.5.3:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "3.5.3"
resolved "https://registry.yarnpkg.com/bluebird/-/bluebird-3.5.3.tgz#7d01c6f9616c9a51ab0f8c549a79dfe6ec33efa7"
integrity sha512-/qKPUQlaW1OyR51WeCPBvRnAlnZFUJkCSG5HzGnuIqhgyJtF+T94lFnn33eiazjRm2LAHVy2guNnaq48X9SJuw==
build: move zone.js to angular repo (#30962) PR Close #30962
2019-05-31 11:56:07 -04:00
bluebird@^3.5.5:
version "3.5.5"
resolved "https://registry.yarnpkg.com/bluebird/-/bluebird-3.5.5.tgz#a8d0afd73251effbbd5fe384a77d73003c17a71f"
integrity sha512-5am6HnnfN+urzt4yfg7IgTbotDjIT/u8AJpEt0sIU9FtXfVeezXAPKswrG+xKUCOYAINpSdgZVDU6QFh+cuH3w==
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
body-parser@1.18.3, body-parser@^1.16.1, body-parser@^1.18.3:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.18.3"
resolved "https://registry.yarnpkg.com/body-parser/-/body-parser-1.18.3.tgz#5b292198ffdd553b3a0f20ded0592b956955c8b4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-WykhmP/dVTs6DyDe0FkrlWlVyLQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
bytes "3.0.0"
content-type "~1.0.4"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
debug "2.6.9"
depd "~1.1.2"
http-errors "~1.6.3"
iconv-lite "0.4.23"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
on-finished "~2.3.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
qs "6.5.2"
raw-body "2.3.3"
type-is "~1.6.16"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
body-parser@~1.13.3:
version "1.13.3"
resolved "https://registry.yarnpkg.com/body-parser/-/body-parser-1.13.3.tgz#c08cf330c3358e151016a05746f13f029c97fa97"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wIzzMMM1jhUQFqBXRvE/ApyX+pc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
bytes "2.1.0"
content-type "~1.0.1"
debug "~2.2.0"
depd "~1.0.1"
http-errors "~1.3.1"
iconv-lite "0.4.11"
on-finished "~2.3.0"
qs "4.0.0"
raw-body "~2.1.2"
type-is "~1.6.6"
body-parser@~1.14.0:
version "1.14.2"
resolved "https://registry.yarnpkg.com/body-parser/-/body-parser-1.14.2.tgz#1015cb1fe2c443858259581db53332f8d0cf50f9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-EBXLH+LEQ4WCWVgdtTMy+NDPUPk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
bytes "2.2.0"
content-type "~1.0.1"
debug "~2.2.0"
depd "~1.1.0"
http-errors "~1.3.1"
iconv-lite "0.4.13"
on-finished "~2.3.0"
qs "5.2.0"
raw-body "~2.1.5"
type-is "~1.6.10"
boom@2.x.x:
version "2.10.1"
resolved "https://registry.yarnpkg.com/boom/-/boom-2.10.1.tgz#39c8918ceff5799f83f9492a848f625add0c766f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-OciRjO/1eZ+D+UkqhI9iWt0Mdm8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
hoek "2.x.x"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
boxen@^1.2.1:
version "1.3.0"
resolved "https://registry.yarnpkg.com/boxen/-/boxen-1.3.0.tgz#55c6c39a8ba58d9c61ad22cd877532deb665a20b"
integrity sha512-TNPjfTr432qx7yOjQyaXm3dSR0MH9vXp7eT1BFSl/C51g+EFnOR9hTg1IreahGBmDNCehscshe45f+C1TBZbLw==
dependencies:
ansi-align "^2.0.0"
camelcase "^4.0.0"
chalk "^2.0.1"
cli-boxes "^1.0.0"
string-width "^2.0.0"
term-size "^1.2.0"
widest-line "^2.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
brace-expansion@^1.0.0, brace-expansion@^1.1.7:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.1.11"
resolved "https://registry.yarnpkg.com/brace-expansion/-/brace-expansion-1.1.11.tgz#3c7fcbf529d87226f3d2f52b966ff5271eb441dd"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
balanced-match "^1.0.0"
concat-map "0.0.1"
braces@^0.1.2:
version "0.1.5"
resolved "https://registry.yarnpkg.com/braces/-/braces-0.1.5.tgz#c085711085291d8b75fdd74eab0f8597280711e6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wIVxEIUpHYt1/ddOqw+FlygHEeY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
expand-range "^0.1.0"
braces@^1.8.2:
version "1.8.5"
resolved "https://registry.yarnpkg.com/braces/-/braces-1.8.5.tgz#ba77962e12dff969d6b76711e914b737857bf6a7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-uneWLhLf+WnWt2cR6RS3N4V79qc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
expand-range "^1.8.1"
preserve "^0.2.0"
repeat-element "^1.1.2"
build(compiler-cli): upgrade chokidar to latest version (#28797) Fixes #28771 PR Close #28797
2019-02-18 08:11:03 -05:00
braces@^2.3.0, braces@^2.3.1, braces@^2.3.2:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "2.3.2"
resolved "https://registry.yarnpkg.com/braces/-/braces-2.3.2.tgz#5979fd3f14cd531565e5fa2df1abfff1dfaee729"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-aNdbnj9P8PjdXU4ybaWLK2IF3jc/EoDYbC7AazW6to3TRsfXxscC9UXOB5iDiEQrkyIbWp2SLQda4+QAa7nc3w==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
arr-flatten "^1.1.0"
array-unique "^0.3.2"
extend-shallow "^2.0.1"
fill-range "^4.0.0"
isobject "^3.0.1"
repeat-element "^1.1.2"
snapdragon "^0.8.1"
snapdragon-node "^2.0.1"
split-string "^3.0.2"
to-regex "^3.0.1"
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 14:57:36 -04:00
brotli@^1.3.2:
version "1.3.2"
resolved "https://registry.yarnpkg.com/brotli/-/brotli-1.3.2.tgz#525a9cad4fcba96475d7d388f6aecb13eed52f46"
integrity sha1-UlqcrU/LqWR119OI9q7LE+7VL0Y=
dependencies:
base64-js "^1.1.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
browserify-zlib@~0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/browserify-zlib/-/browserify-zlib-0.1.4.tgz#bb35f8a519f600e0fa6b8485241c979d0141fb2d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-uzX4pRn2AOD6a4SFJByXnQFB+y0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
pako "~0.2.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
browserstack@1.5.0:
version "1.5.0"
resolved "https://registry.yarnpkg.com/browserstack/-/browserstack-1.5.0.tgz#b565425ad62ed72c1082a1eb979d5313c7d4754f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-tWVCWtYu1ywQgqHrl51TE8fUdU8=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
https-proxy-agent "1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
browserstack@^1.5.1:
version "1.5.1"
resolved "https://registry.yarnpkg.com/browserstack/-/browserstack-1.5.1.tgz#e2dfa66ffee940ebad0a07f7e00fd4687c455d66"
integrity sha512-O8VMT64P9NOLhuIoD4YngyxBURefaSdR4QdhG8l6HZ9VxtU7jc3m6jLufFwKA5gaf7fetfB2TnRJnMxyob+heg==
dependencies:
https-proxy-agent "^2.2.1"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
browserstacktunnel-wrapper@2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/browserstacktunnel-wrapper/-/browserstacktunnel-wrapper-2.0.1.tgz#ffe1910d6e39fe86618183e826690041af53edae"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-/+GRDW45/oZhgYPoJmkAQa9T7a4=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
https-proxy-agent "^1.0.0"
unzip "~0.1.9"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
browserstacktunnel-wrapper@~2.0.1:
version "2.0.2"
resolved "https://registry.yarnpkg.com/browserstacktunnel-wrapper/-/browserstacktunnel-wrapper-2.0.2.tgz#3d11159c18cd202b2920b09830fbe4bd90f079b5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-7w7HYA00qjBtuQH0c5rqW7RbWPHyRROqTZofwNp5G0sKc2fYChsTfbHz3ul8Yd+ffkQvR81m+iPjEB004P6kxQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
https-proxy-agent "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
unzip "~0.1.9"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
buffer-alloc-unsafe@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/buffer-alloc-unsafe/-/buffer-alloc-unsafe-1.1.0.tgz#bd7dc26ae2972d0eda253be061dba992349c19f0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-TEM2iMIEQdJ2yjPJoSIsldnleVaAk1oW3DBVUykyOLsEsFmEc9kn+SFFPz+gl54KQNxlDnAwCXosOS9Okx2xAg==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
buffer-alloc@^1.1.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/buffer-alloc/-/buffer-alloc-1.2.0.tgz#890dd90d923a873e08e10e5fd51a57e5b7cce0ec"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-CFsHQgjtW1UChdXgbyJGtnm+O/uLQeZdtbDo8mfUgYXCHSM1wgrVxXm6bSyrUuErEb+4sYVGCzASBRot7zyrow==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
buffer-alloc-unsafe "^1.1.0"
buffer-fill "^1.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
buffer-crc32@^0.2.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.2.13"
resolved "https://registry.yarnpkg.com/buffer-crc32/-/buffer-crc32-0.2.13.tgz#0d333e3f00eac50aa1454abd30ef8c2a5d9a7242"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-DTM+PwDqxQqhRUq9MO+MKl2ackI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
buffer-equal-constant-time@1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/buffer-equal-constant-time/-/buffer-equal-constant-time-1.0.1.tgz#f8e71132f7ffe6e01a5c9697a4c6f3e48d5cc819"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+OcRMvf/5uAaXJaXpMbz5I1cyBk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
buffer-fill@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/buffer-fill/-/buffer-fill-1.0.0.tgz#f8f78b76789888ef39f205cd637f68e702122b2c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+PeLdniYiO858gXNY39o5wISKyw=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
buffer-from@^1.0.0:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "1.1.1"
resolved "https://registry.yarnpkg.com/buffer-from/-/buffer-from-1.1.1.tgz#32713bc028f75c02fdb710d7c7bcec1f2c6070ef"
integrity sha512-MQcXEUbCKtEo7bhqEs6560Hyd4XaovZlO/k9V3hjVUF/zwW7KBVdSK4gIt/bzwS9MbR5qob+F5jusZsb0YQK2A==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
buffer@^4.9.0:
version "4.9.1"
resolved "https://registry.yarnpkg.com/buffer/-/buffer-4.9.1.tgz#6d1bb601b07a4efced97094132093027c95bc298"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-bRu2AbB6TvztlwlBMgkwJ8lbwpg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
base64-js "^1.0.2"
ieee754 "^1.1.4"
isarray "^1.0.0"
buffers@~0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/buffers/-/buffers-0.1.1.tgz#b24579c3bed4d6d396aeee6d9a8ae7f5482ab7bb"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-skV5w77U1tOWru5tmorn9Ugqt7s=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
builtin-modules@^1.0.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.1.1"
resolved "https://registry.yarnpkg.com/builtin-modules/-/builtin-modules-1.1.1.tgz#270f076c5a72c02f5b65a47df94c5fe3a278892f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Jw8HbFpywC9bZaR9+Uxf46J4iS8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
builtin-modules@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/builtin-modules/-/builtin-modules-3.0.0.tgz#1e587d44b006620d90286cc7a9238bbc6129cab1"
integrity sha512-hMIeU4K2ilbXV6Uv93ZZ0Avg/M91RaKXucQ+4me2Do1txxBDyDZWCBa5bJSLqoNTRpXTLwEzIk1KmloenDDjhg==
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
builtin-modules@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/builtin-modules/-/builtin-modules-3.1.0.tgz#aad97c15131eb76b65b50ef208e7584cd76a7484"
integrity sha512-k0KL0aWZuBt2lrxrcASWDfwOLMnodeQjodT/1SxEQAXsHANgo6ZC/VEaSEHCXt7aSTZ4/4H5LKa+tBXmW7Vtvw==
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
builtins@^1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/builtins/-/builtins-1.0.3.tgz#cb94faeb61c8696451db36534e1422f94f0aee88"
integrity sha1-y5T662HIaWRR2zZTThQi+U8K7og=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
bytes@2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/bytes/-/bytes-2.1.0.tgz#ac93c410e2ffc9cc7cf4b464b38289067f5e47b4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-rJPEEOL/ycx89LRks4KJBn9eR7Q=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
bytes@2.2.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/bytes/-/bytes-2.2.0.tgz#fd35464a403f6f9117c2de3609ecff9cae000588"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-/TVGSkA/b5EXwt42Cez/nK4ABYg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
bytes@2.4.0:
version "2.4.0"
resolved "https://registry.yarnpkg.com/bytes/-/bytes-2.4.0.tgz#7d97196f9d5baf7f6935e25985549edd2a6c2339"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-fZcZb51br39pNeJZhVSe3SpsIzk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
bytes@3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/bytes/-/bytes-3.0.0.tgz#d32815404d689699f85a4ea4fa8755dd13a96048"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-0ygVQE1olpn4Wk6k+odV3ROpYEg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Cleanup bazel-schematics integration test (#28351) PR Close #28351
2019-01-24 14:51:20 -05:00
cacache@^11.0.1, cacache@^11.3.2:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "11.3.2"
resolved "https://registry.yarnpkg.com/cacache/-/cacache-11.3.2.tgz#2d81e308e3d258ca38125b676b98b2ac9ce69bfa"
integrity sha512-E0zP4EPGDOaT2chM08Als91eYnf8Z+eH1awwwVsngUmgppfM5jjJ8l3z5vO5p5w/I3LsiXawb1sW0VY65pQABg==
dependencies:
bluebird "^3.5.3"
chownr "^1.1.1"
figgy-pudding "^3.5.1"
glob "^7.1.3"
graceful-fs "^4.1.15"
lru-cache "^5.1.1"
mississippi "^3.0.0"
mkdirp "^0.5.1"
move-concurrently "^1.0.1"
promise-inflight "^1.0.1"
rimraf "^2.6.2"
ssri "^6.0.1"
unique-filename "^1.1.1"
y18n "^4.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
cache-base@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/cache-base/-/cache-base-1.0.1.tgz#0a7f46416831c8b662ee36fe4e7c59d76f666ab2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-AKcdTnFSWATd5/GCPRxr2ChwIJ85CeyrEyjRHlKxQ56d4XJMGym0uAiKn0xbLOGOl3+yRpOTi484dVCEc5AUzQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
collection-visit "^1.0.0"
component-emitter "^1.2.1"
get-value "^2.0.6"
has-value "^1.0.0"
isobject "^3.0.1"
set-value "^2.0.0"
to-object-path "^0.3.0"
union-value "^1.0.0"
unset-value "^1.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
cacheable-request@^2.1.1:
version "2.1.4"
resolved "https://registry.yarnpkg.com/cacheable-request/-/cacheable-request-2.1.4.tgz#0d808801b6342ad33c91df9d0b44dc09b91e5c3d"
integrity sha1-DYCIAbY0KtM8kd+dC0TcCbkeXD0=
dependencies:
clone-response "1.0.2"
get-stream "3.0.0"
http-cache-semantics "3.8.1"
keyv "3.0.0"
lowercase-keys "1.0.0"
normalize-url "2.0.1"
responselike "1.0.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
callsite@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/callsite/-/callsite-1.0.0.tgz#280398e5d664bd74038b6f0905153e6e8af1bc20"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-KAOY5dZkvXQDi28JBRU+borxvCA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
camelcase-keys@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/camelcase-keys/-/camelcase-keys-2.1.0.tgz#308beeaffdf28119051efa1d932213c91b8f92e7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-MIvur/3ygRkFHvodkyITyRuPkuc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
camelcase "^2.0.0"
map-obj "^1.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
camelcase-keys@^4.0.0:
version "4.2.0"
resolved "https://registry.yarnpkg.com/camelcase-keys/-/camelcase-keys-4.2.0.tgz#a2aa5fb1af688758259c32c141426d78923b9b77"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-oqpfsa9oh1glnDLBQUJteJI7m3c=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
camelcase "^4.1.0"
map-obj "^2.0.0"
quick-lru "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
camelcase@^1.0.2:
version "1.2.1"
resolved "https://registry.yarnpkg.com/camelcase/-/camelcase-1.2.1.tgz#9bb5304d2e0b56698b2c758b08a3eaa9daa58a39"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-m7UwTS4LVmmLLHWLCKPqqdqlijk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.10 (#29694) PR Close #29694
2019-04-03 19:56:20 -04:00
camelcase@^2.0.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.1.1"
resolved "https://registry.yarnpkg.com/camelcase/-/camelcase-2.1.1.tgz#7c1d16d679a1bbe59ca02cacecfb011e201f5a1f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-fB0W1nmhu+WcoCys7PsBHiAfWh8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
camelcase@^4.0.0, camelcase@^4.1.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "4.1.0"
resolved "https://registry.yarnpkg.com/camelcase/-/camelcase-4.1.0.tgz#d545635be1e33c542649c69173e5de6acfae34dd"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-1UVjW+HjPFQmScaRc+Xeas+uNN0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
camelcase@^5.0.0:
version "5.3.1"
resolved "https://registry.yarnpkg.com/camelcase/-/camelcase-5.3.1.tgz#e3c9b31569e106811df242f715725a1f4c494320"
integrity sha512-L28STB170nwWS63UjtlEOE3dldQApaJXZkOI1uMFfzf3rRuPegHaHesyee+YxQ+W6SvRDQV6UrdOdRiR153wJg==
build: update `canonical-path` dependency (#26719) This new version (1.0.0) provides a typings file! PR Close #26719
2018-10-24 08:24:14 -04:00
canonical-path@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/canonical-path/-/canonical-path-1.0.0.tgz#fcb470c23958def85081856be7a86e904f180d1d"
integrity sha512-feylzsbDxi1gPZ1IjystzIQZagYYLvfKrSuygUCgf7z6x790VEzze5QEkdSV1U58RA7Hi0+v6fv4K54atOzATg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
capture-stack-trace@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/capture-stack-trace/-/capture-stack-trace-1.0.1.tgz#a6c0bbe1f38f3aa0b92238ecb6ff42c344d4135d"
integrity sha512-mYQLZnx5Qt1JgB1WEiMCf2647plpGeQ2NMR/5L0HNZzGQo4fuSPnK+wjfPnKZV0aiJDgzmWqqkV/g7JD+DW0qw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
caseless@~0.11.0:
version "0.11.0"
resolved "https://registry.yarnpkg.com/caseless/-/caseless-0.11.0.tgz#715b96ea9841593cc33067923f5ec60ebda4f7d7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-cVuW6phBWTzDMGeSP17GDr2k99c=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
caseless@~0.12.0:
version "0.12.0"
resolved "https://registry.yarnpkg.com/caseless/-/caseless-0.12.0.tgz#1b681c21ff84033c826543090689420d187151dc"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-G2gcIf+EAzyCZUMJBolCDRhxUdw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
center-align@^0.1.1:
version "0.1.3"
resolved "https://registry.yarnpkg.com/center-align/-/center-align-0.1.3.tgz#aa0d32629b6ee972200411cbd4461c907bc2b7ad"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-qg0yYptu6XIgBBHL1EYckHvCt60=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
align-text "^0.1.3"
lazy-cache "^1.0.3"
build(bazel): remove @ts-api-guardian_deps yarn_install (#29799) PR Close #29799
2019-04-09 21:08:13 -04:00
chai@^4.1.2:
version "4.2.0"
resolved "https://registry.yarnpkg.com/chai/-/chai-4.2.0.tgz#760aa72cf20e3795e84b12877ce0e83737aa29e5"
integrity sha512-XQU3bhBukrOsQCuwZndwGcCVQHyZi53fQ6Ys1Fym7E4olpIqqZZhhoFJoaKVvV17lWQoXYwgWN2nF5crA8J2jw==
dependencies:
assertion-error "^1.1.0"
check-error "^1.0.2"
deep-eql "^3.0.1"
get-func-name "^2.0.0"
pathval "^1.1.0"
type-detect "^4.0.5"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"chainsaw@>=0.0.7 <0.1":
version "0.0.9"
resolved "https://registry.yarnpkg.com/chainsaw/-/chainsaw-0.0.9.tgz#11a05102d1c4c785b6d0415d336d5a3a1612913e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-EaBRAtHEx4W20EFdM21aOhYSkT4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
traverse ">=0.3.0 <0.4"
chainsaw@~0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/chainsaw/-/chainsaw-0.1.0.tgz#5eab50b28afe58074d0d58291388828b5e5fbc98"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-XqtQsor+WAdNDVgpE4iCi15fvJg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
traverse ">=0.3.0 <0.4"
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
chalk@^1.0.0, chalk@^1.1.1, chalk@^1.1.3:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.1.3"
resolved "https://registry.yarnpkg.com/chalk/-/chalk-1.1.3.tgz#a8115c55e4a702fe4d150abd3872822a7e09fc98"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-qBFcVeSnAv5NFQq9OHKCKn4J/Jg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
ansi-styles "^2.2.1"
escape-string-regexp "^1.0.2"
has-ansi "^2.0.0"
strip-ansi "^3.0.0"
supports-color "^2.0.0"
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
chalk@^2.0.0, chalk@^2.0.1, chalk@^2.3.1, chalk@^2.4.2:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "2.4.2"
resolved "https://registry.yarnpkg.com/chalk/-/chalk-2.4.2.tgz#cd42541677a54333cf541a49108c1432b44c9424"
integrity sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==
dependencies:
ansi-styles "^3.2.1"
escape-string-regexp "^1.0.5"
supports-color "^5.3.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
char-spinner@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/char-spinner/-/char-spinner-1.0.1.tgz#e6ea67bd247e107112983b7ab0479ed362800081"
integrity sha1-5upnvSR+EHESmDt6sEee02KAAIE=
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
chardet@^0.7.0:
version "0.7.0"
resolved "https://registry.yarnpkg.com/chardet/-/chardet-0.7.0.tgz#90094849f0937f2eedc2425d0d28a9e5f0cbad9e"
integrity sha512-mT8iDcrh03qDGRRmoA2hmBJnxpllMR+0/0qlzjqZES6NdiWDcZkCNAk4rPFZ9Q85r27unkiNNg8ZOiwZXBHwcA==
build(bazel): remove @ts-api-guardian_deps yarn_install (#29799) PR Close #29799
2019-04-09 21:08:13 -04:00
check-error@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/check-error/-/check-error-1.0.2.tgz#574d312edd88bb5dd8912e9286dd6c0aed4aac82"
integrity sha1-V00xLt2Iu13YkS6Sht1sCu1KrII=
test: update side-effects test to be more descriptive (#31005) This test will now list diffs for failed expectations and the full command to update them. Fix #30570 PR Close #31005
2019-06-12 11:11:14 -04:00
check-side-effects@0.0.21:
version "0.0.21"
resolved "https://registry.yarnpkg.com/check-side-effects/-/check-side-effects-0.0.21.tgz#6127c933d329e0806df940701f9cd62f51bffb19"
integrity sha512-tv64B+krepm3P4v5L76LngaiD0YSDpNepRoMLGQ9yOGVQKe1XrYLk7EpynEG8z5YNKxhC7uzt1kCSspM3Kei0Q==
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
dependencies:
"@angular-devkit/build-optimizer" "0.14.0-beta.5"
test: update side-effects test to be more descriptive (#31005) This test will now list diffs for failed expectations and the full command to update them. Fix #30570 PR Close #31005
2019-06-12 11:11:14 -04:00
diff "^4.0.1"
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
minimist "~1.2.0"
rollup "~1.11.3"
rollup-plugin-node-resolve "~4.2.3"
rollup-plugin-terser "~4.0.4"
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
chokidar@^1.0.0:
version "1.7.0"
resolved "https://registry.yarnpkg.com/chokidar/-/chokidar-1.7.0.tgz#798e689778151c8076b4b360e5edd28cda2bb468"
integrity sha1-eY5ol3gVHIB2tLNg5e3SjNortGg=
dependencies:
anymatch "^1.3.0"
async-each "^1.0.0"
glob-parent "^2.0.0"
inherits "^2.0.1"
is-binary-path "^1.0.0"
is-glob "^2.0.0"
path-is-absolute "^1.0.0"
readdirp "^2.0.0"
optionalDependencies:
fsevents "^1.0.0"
chokidar@^2.0.3:
build(compiler-cli): upgrade chokidar to latest version (#28797) Fixes #28771 PR Close #28797
2019-02-18 08:11:03 -05:00
version "2.0.4"
resolved "https://registry.yarnpkg.com/chokidar/-/chokidar-2.0.4.tgz#356ff4e2b0e8e43e322d18a372460bbcf3accd26"
integrity sha512-z9n7yt9rOvIJrMhvDtDictKrkFHeihkNl6uWMmZlmL6tJtX9Cs+87oK+teBx+JIgzvbX3yZHT3eF8vpbDxHJXQ==
dependencies:
anymatch "^2.0.0"
async-each "^1.0.0"
braces "^2.3.0"
glob-parent "^3.1.0"
inherits "^2.0.1"
is-binary-path "^1.0.0"
is-glob "^4.0.0"
lodash.debounce "^4.0.8"
normalize-path "^2.1.1"
path-is-absolute "^1.0.0"
readdirp "^2.0.0"
upath "^1.0.5"
optionalDependencies:
fsevents "^1.2.2"
chokidar@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/chokidar/-/chokidar-2.1.1.tgz#adc39ad55a2adf26548bd2afa048f611091f9184"
integrity sha512-gfw3p2oQV2wEt+8VuMlNsPjCxDxvvgnm/kz+uATu805mWVF8IJN7uz9DN7iBz+RMJISmiVbCOBFs9qBGMjtPfQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
anymatch "^2.0.0"
build(compiler-cli): upgrade chokidar to latest version (#28797) Fixes #28771 PR Close #28797
2019-02-18 08:11:03 -05:00
async-each "^1.0.1"
braces "^2.3.2"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
glob-parent "^3.1.0"
build(compiler-cli): upgrade chokidar to latest version (#28797) Fixes #28771 PR Close #28797
2019-02-18 08:11:03 -05:00
inherits "^2.0.3"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
is-binary-path "^1.0.0"
is-glob "^4.0.0"
build(compiler-cli): upgrade chokidar to latest version (#28797) Fixes #28771 PR Close #28797
2019-02-18 08:11:03 -05:00
normalize-path "^3.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
path-is-absolute "^1.0.0"
build(compiler-cli): upgrade chokidar to latest version (#28797) Fixes #28771 PR Close #28797
2019-02-18 08:11:03 -05:00
readdirp "^2.2.1"
upath "^1.1.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
optionalDependencies:
build(compiler-cli): upgrade chokidar to latest version (#28797) Fixes #28771 PR Close #28797
2019-02-18 08:11:03 -05:00
fsevents "^1.2.7"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
chownr@^1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/chownr/-/chownr-1.1.1.tgz#54726b8b8fff4df053c42187e801fb4412df1494"
integrity sha512-j38EvO5+LHX84jlo6h4UzmOwi0UgW61WRyPtJz4qaadK5eY3BTS5TY/S1Stc3Uk2lIM6TPevAlULiEJwie860g==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
refactor: add a commit-msg git hook to check commit messages (#22969) The commit command will fail if the commit message header does not follow the Angular convetions as defined in /CONTRIBUTING.md. You can force the commit by adding the `--no-verify` option. NOTE: You should remove all unused hooks (in <angular>/.git/hooks) before running `yarn` so that husky hooks are installed correctly. PR Close #22969
2018-03-23 19:07:33 -04:00
ci-info@^1.0.0:
version "1.1.3"
resolved "https://registry.yarnpkg.com/ci-info/-/ci-info-1.1.3.tgz#710193264bb05c77b8c90d02f5aaf22216a667b2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-SK/846h/Rcy8q9Z9CAwGBLfCJ6EkjJWdpelWDufQpqVDYq2Wnnv8zlSO6AMQap02jvhVruKKpEtQOufo3pFhLg==
refactor: add a commit-msg git hook to check commit messages (#22969) The commit command will fail if the commit message header does not follow the Angular convetions as defined in /CONTRIBUTING.md. You can force the commit by adding the `--no-verify` option. NOTE: You should remove all unused hooks (in <angular>/.git/hooks) before running `yarn` so that husky hooks are installed correctly. PR Close #22969
2018-03-23 19:07:33 -04:00
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
circular-json@^0.5.5:
version "0.5.9"
resolved "https://registry.yarnpkg.com/circular-json/-/circular-json-0.5.9.tgz#932763ae88f4f7dead7a0d09c8a51a4743a53b1d"
integrity sha512-4ivwqHpIFJZBuhN3g/pEcdbnGUywkBblloGbkglyloVjjR3uT6tieI89MVOfbP2tHX5sgb01FuLgAOzebNlJNQ==
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
cjson@^0.3.1:
version "0.3.3"
resolved "https://registry.yarnpkg.com/cjson/-/cjson-0.3.3.tgz#a92d9c786e5bf9b930806329ee05d5d3261b4afa"
integrity sha1-qS2ceG5b+bkwgGMp7gXV0yYbSvo=
dependencies:
json-parse-helpfulerror "^1.0.3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
clang-format@1.0.41:
version "1.0.41"
resolved "https://registry.yarnpkg.com/clang-format/-/clang-format-1.0.41.tgz#28552e50b0c9e44d23f85aebe3d2fbd06c93620c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-KFUuULDJ5E0j+Frr49L70GyTYgw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
async "^1.5.2"
glob "^7.0.0"
resolve "^1.1.6"
clang-format@^1.0.32:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.2.3"
resolved "https://registry.yarnpkg.com/clang-format/-/clang-format-1.2.3.tgz#2763561aa7449c43737480f8df3a2b5b66e6cf37"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-x90Hac4ERacGDcZSvHKK58Ga0STuMD+Doi5g0iG2zf7wlJef5Huvhs/3BvMRFxwRYyYSdl6mpQNrtfMxE8MQzw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
async "^1.5.2"
glob "^7.0.0"
resolve "^1.1.6"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
class-utils@^0.3.5:
version "0.3.6"
resolved "https://registry.yarnpkg.com/class-utils/-/class-utils-0.3.6.tgz#f93369ae8b9a7ce02fd41faad0ca83033190c463"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-qOhPa/Fj7s6TY8H8esGu5QNpMMQxz79h+urzrNYN6mn+9BnxlDGf5QZ+XeCDsxSjPqsSR56XOZOJmpeurnLMeg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
arr-union "^3.1.0"
define-property "^0.2.5"
isobject "^3.0.0"
static-extend "^0.1.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
cldr-data-downloader@0.3.2:
version "0.3.2"
resolved "https://registry.yarnpkg.com/cldr-data-downloader/-/cldr-data-downloader-0.3.2.tgz#8d0c98346d16486252fdc9afa36a46542fe4652f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-jQyYNG0WSGJS/cmvo2pGVC/kZS8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
adm-zip "0.4.4"
mkdirp "0.5.0"
nopt "3.0.x"
npmconf "2.0.9"
progress "1.1.8"
q "1.0.1"
request "~2.74.0"
request-progress "0.3.1"
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
cldr@4.10.0:
version "4.10.0"
resolved "https://registry.yarnpkg.com/cldr/-/cldr-4.10.0.tgz#5a72a693728eca491bc8ee027d60fa4dc750a24f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-c5IVGFyPNs0qiTKTBJxYBVh9WK+Vz5RHATJEtjKCkrBUZkj6wAl79dYxqdiFEOD4JlUVDHCpZRnYbz2y6A0JnA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
lodash "^4.17.10"
memoizeasync "^1.1.0"
passerror "^1.1.1"
pegjs "^0.10.0"
seq "^0.3.5"
uglify-js "^1.3.3"
unicoderegexp "^0.4.1"
xmldom "^0.1.27"
xpath "^0.0.27"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
cldrjs@0.5.0:
version "0.5.0"
resolved "https://registry.yarnpkg.com/cldrjs/-/cldrjs-0.5.0.tgz#37be92d8d1a8e66c8ee12f1303ed316d85d8eb37"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-N76S2NGo5myO4S8TA+0xbYXY6zc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
cli-boxes@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/cli-boxes/-/cli-boxes-1.0.0.tgz#4fa917c3e59c94a004cd61f8ee509da651687143"
integrity sha1-T6kXw+WclKAEzWH47lCdplFocUM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
cli-color@^1.0.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/cli-color/-/cli-color-1.2.0.tgz#3a5ae74fd76b6267af666e69e2afbbd01def34d1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-OlrnT9drYmevZm5p4q+70B3vNNE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
ansi-regex "^2.1.1"
d "1"
es5-ext "^0.10.12"
es6-iterator "2"
memoizee "^0.4.3"
timers-ext "0.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
cli-color@^1.2.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/cli-color/-/cli-color-1.4.0.tgz#7d10738f48526824f8fe7da51857cb0f572fe01f"
integrity sha512-xu6RvQqqrWEo6MPR1eixqGPywhYBHRs653F9jfXB2Hx4jdM/3WxiNE1vppRmxtMIfl16SFYTpYlrnqH/HsK/2w==
dependencies:
ansi-regex "^2.1.1"
d "1"
es5-ext "^0.10.46"
es6-iterator "^2.0.3"
memoizee "^0.4.14"
timers-ext "^0.1.5"
cli-cursor@^1.0.1, cli-cursor@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/cli-cursor/-/cli-cursor-1.0.2.tgz#64da3f7d56a54412e59794bd62dc35295e8f2987"
integrity sha1-ZNo/fValRBLll5S9Ytw1KV6PKYc=
dependencies:
restore-cursor "^1.0.1"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
cli-cursor@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/cli-cursor/-/cli-cursor-2.1.0.tgz#b35dac376479facc3e94747d41d0d0f5238ffcb5"
integrity sha1-s12sN2R5+sw+lHR9QdDQ9SOP/LU=
dependencies:
restore-cursor "^2.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
cli-spinners@^0.1.2:
version "0.1.2"
resolved "https://registry.yarnpkg.com/cli-spinners/-/cli-spinners-0.1.2.tgz#bb764d88e185fb9e1e6a2a1f19772318f605e31c"
integrity sha1-u3ZNiOGF+54eaiofGXcjGPYF4xw=
cli-table2@0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/cli-table2/-/cli-table2-0.2.0.tgz#2d1ef7f218a0e786e214540562d4bd177fe32d97"
integrity sha1-LR738hig54biFFQFYtS9F3/jLZc=
dependencies:
lodash "^3.10.1"
string-width "^1.0.1"
optionalDependencies:
colors "^1.1.2"
cli-table@^0.3.1:
version "0.3.1"
resolved "https://registry.yarnpkg.com/cli-table/-/cli-table-0.3.1.tgz#f53b05266a8b1a0b934b3d0821e6e2dc5914ae23"
integrity sha1-9TsFJmqLGguTSz0IIebi3FkUriM=
dependencies:
colors "1.0.3"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
cli-width@^2.0.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/cli-width/-/cli-width-2.2.0.tgz#ff19ede8a9a5e579324147b0c11f0fbcbabed639"
integrity sha1-/xnt6Kml5XkyQUewwR8PvLq+1jk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
cliui@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/cliui/-/cliui-2.1.0.tgz#4b475760ff80264c762c3a1719032e91c7fea0d1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-S0dXYP+AJkx2LDoXGQMukcf+oNE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
center-align "^0.1.1"
right-align "^0.1.1"
wordwrap "0.0.2"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
cliui@^4.0.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/cliui/-/cliui-4.1.0.tgz#348422dbe82d800b3022eef4f6ac10bf2e4d1b49"
integrity sha512-4FG+RSG9DL7uEwRUZXZn3SS34DiDPfzP0VOiEwtUWlE+AR2EIg+hSyvrIgUUfhdgR/UkAeW2QHgeP+hWrXs7jQ==
dependencies:
string-width "^2.1.1"
strip-ansi "^4.0.0"
wrap-ansi "^2.0.0"
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
clone-buffer@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/clone-buffer/-/clone-buffer-1.0.0.tgz#e3e25b207ac4e701af721e2cb5a16792cac3dc58"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-4+JbIHrE5wGvch4staFnksrD3Fg=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
clone-response@1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/clone-response/-/clone-response-1.0.2.tgz#d1dc973920314df67fbeb94223b4ee350239e96b"
integrity sha1-0dyXOSAxTfZ/vrlCI7TuNQI56Ws=
dependencies:
mimic-response "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
clone-stats@^0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/clone-stats/-/clone-stats-0.0.1.tgz#b88f94a82cf38b8791d58046ea4029ad88ca99d1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-uI+UqCzzi4eR1YBG6kAprYjKmdE=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
clone-stats@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/clone-stats/-/clone-stats-1.0.0.tgz#b3782dff8bb5474e18b9b6bf0fdfe782f8777680"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-s3gt/4u1R04Yuba/D9/ngvh3doA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
clone@^0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/clone/-/clone-0.2.0.tgz#c6126a90ad4f72dbf5acdb243cc37724fe93fc1f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-xhJqkK1Pctv1rNskPMN3JP6T/B8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
clone@^1.0.0, clone@^1.0.2:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.0.4"
resolved "https://registry.yarnpkg.com/clone/-/clone-1.0.4.tgz#da309cc263df15994c688ca902179ca3c7cd7c7e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-2jCcwmPfFZlMaIypAheco8fNfH4=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
clone@^2.1.1:
version "2.1.2"
resolved "https://registry.yarnpkg.com/clone/-/clone-2.1.2.tgz#1b7f4b9f591f1e8f83670401600345a02887435f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-G39Ln1kfHo+DZwQBYANFoCiHQ18=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
cloneable-readable@^1.0.0:
version "1.1.2"
resolved "https://registry.yarnpkg.com/cloneable-readable/-/cloneable-readable-1.1.2.tgz#d591dee4a8f8bc15da43ce97dceeba13d43e2a65"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-Bq6+4t+lbM8vhTs/Bef5c5AdEMtapp/iFb6+s4/Hh9MVTt8OLKH7ZOOZSCT+Ys7hsHvqv0GuMPJ1lnQJVHvxpg==
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
inherits "^2.0.1"
process-nextick-args "^2.0.0"
readable-stream "^2.3.5"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
co@^4.6.0:
version "4.6.0"
resolved "https://registry.yarnpkg.com/co/-/co-4.6.0.tgz#6ea6bdf3d853ae54ccb8e47bfa0bf3f9031fb184"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-bqa989hTrlTMuOR7+gvz+QMfsYQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
code-point-at@^1.0.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/code-point-at/-/code-point-at-1.1.0.tgz#0d070b4d043a5bea33a2f1a40e2edb3d9a4ccf77"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-DQcLTQQ6W+ozovGkDi7bPZpMz3c=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
coffee-script@1.3.3:
version "1.3.3"
resolved "https://registry.yarnpkg.com/coffee-script/-/coffee-script-1.3.3.tgz#150d6b4cb522894369efed6a2101c20bc7f4a4f4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-FQ1rTLUiiUNp7+1qIQHCC8f0pPQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
collection-visit@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/collection-visit/-/collection-visit-1.0.0.tgz#4bc0373c164bc3291b4d368c829cf1a80a59dca0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-S8A3PBZLwykbTTaMgpzxqApZ3KA=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
map-visit "^1.0.0"
object-visit "^1.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
color-convert@^1.9.0:
version "1.9.3"
resolved "https://registry.yarnpkg.com/color-convert/-/color-convert-1.9.3.tgz#bb71850690e1f136567de629d2d5471deda4c1e8"
integrity sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg==
dependencies:
color-name "1.1.3"
color-name@1.1.3:
version "1.1.3"
resolved "https://registry.yarnpkg.com/color-name/-/color-name-1.1.3.tgz#a7d0558bd89c42f795dd42328f740831ca53bc25"
integrity sha1-p9BVi9icQveV3UIyj3QIMcpTvCU=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
color-support@^1.1.3:
version "1.1.3"
resolved "https://registry.yarnpkg.com/color-support/-/color-support-1.1.3.tgz#93834379a1cc9a0c61f82f52f0d04322251bd5a2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-qiBjkpbMLO/HL68y+lh4q0/O1MZFj2RX6X/KmMa3+gJD3z+WwI1ZzDHysvqHGS3mP6mznPckpXmw1nI9cJjyRg==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
colors@0.6.0-1:
version "0.6.0-1"
resolved "https://registry.yarnpkg.com/colors/-/colors-0.6.0-1.tgz#6dbb68ceb8bc60f2b313dcc5ce1599f06d19e67a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-bbtozri8YPKzE9zFzhWZ8G0Z5no=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
colors@1.0.3, colors@1.0.x:
version "1.0.3"
resolved "https://registry.yarnpkg.com/colors/-/colors-1.0.3.tgz#0433f44d809680fdeb60ed260f1b0c262e82a40b"
integrity sha1-BDP0TYCWgP3rYO0mDxsMJi6CpAs=
colors@1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/colors/-/colors-1.1.2.tgz#168a4701756b6a7f51a12ce0c97bfa28c084ed63"
integrity sha1-FopHAXVran9RoSzgyXv6KMCE7WM=
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
colors@^1.1.0, colors@^1.1.2:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.3.0"
resolved "https://registry.yarnpkg.com/colors/-/colors-1.3.0.tgz#5f20c9fef6945cb1134260aab33bfbdc8295e04e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-EDpX3a7wHMWFA7PUHWPHNWqOxIIRSJetuwl0AS5Oi/5FMV8kWm69RTlgm00GKjBO1xFHMtBbL49yRtMMdticBw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
colors@~1.2.1:
version "1.2.5"
resolved "https://registry.yarnpkg.com/colors/-/colors-1.2.5.tgz#89c7ad9a374bc030df8013241f68136ed8835afc"
integrity sha512-erNRLao/Y3Fv54qUa0LBB+//Uf3YwMUmdJinN20yMXm9zdKKqH9wt7R9IIVZ+K7ShzfpLV/Zg8+VyrBJYB4lpg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
combine-lists@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/combine-lists/-/combine-lists-1.0.1.tgz#458c07e09e0d900fc28b70a3fec2dacd1d2cb7f6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-RYwH4J4NkA/Ci3Cj/sLazR0st/Y=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
lodash "^4.5.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
combined-stream@1.0.6, combined-stream@^1.0.5, combined-stream@~1.0.5:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.0.6"
resolved "https://registry.yarnpkg.com/combined-stream/-/combined-stream-1.0.6.tgz#723e7df6e801ac5613113a7e445a9b69cb632818"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-cj599ugBrFYTETp+RFqbactjKBg=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
delayed-stream "~1.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
combined-stream@^1.0.6, combined-stream@~1.0.6:
version "1.0.7"
resolved "https://registry.yarnpkg.com/combined-stream/-/combined-stream-1.0.7.tgz#2d1d24317afb8abe95d6d2c0b07b57813539d828"
integrity sha512-brWl9y6vOB1xYPZcpZde3N9zDByXTosAeMDo4p1wzo6UMOX4vumB+TP1RZ76sfE6Md68Q0NJSrE/gbezd4Ul+w==
dependencies:
delayed-stream "~1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
commander@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/commander/-/commander-1.0.0.tgz#5e6a88e7070ff5908836ead19169548c30f90bcd"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-XmqI5wcP9ZCINurRkWlUjDD5C80=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
commander@2.9.0:
version "2.9.0"
resolved "https://registry.yarnpkg.com/commander/-/commander-2.9.0.tgz#9c99094176e12240cb22d6c5146098400fe0f7d4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nJkJQXbhIkDLItbFFGCYQA/g99Q=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
graceful-readlink ">= 1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
commander@^2.13.0, commander@^2.7.1, commander@^2.8.1, commander@~2.19.0:
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
version "2.19.0"
resolved "https://registry.yarnpkg.com/commander/-/commander-2.19.0.tgz#f6198aa84e5b83c46054b94ddedbfed5ee9ff12a"
integrity sha512-6tvAOO+D6OENvRAh524Dh9jcfKTYDQAqvqezbCW82xj5X0pSrcpxtvRKHLG0yBY6SD7PSDrJaj+0AiOcKVd1Xg==
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
commander@^2.19.0:
version "2.20.0"
resolved "https://registry.yarnpkg.com/commander/-/commander-2.20.0.tgz#d58bb2b5c1ee8f87b0d340027e9e94e222c5a422"
integrity sha512-7j2y+40w61zy6YC2iRNpUe/NwhNyoXrYpHMrSunaMG64nRnaf96zO/KMQR4OyN/UnE5KLyEBnKHd4aG3rskjpQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
commander@^2.5.0, commander@^2.9.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "2.16.0"
resolved "https://registry.yarnpkg.com/commander/-/commander-2.16.0.tgz#f16390593996ceb4f3eeb020b31d78528f7f8a50"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-sVXqklSaotK9at437sFlFpyOcJonxe0yST/AG9DkQKUdIE6IqGIMv4SfAQSKaJbSdVEJYItASCrBiVQHq1HQew==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
commondir@0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/commondir/-/commondir-0.0.1.tgz#89f00fdcd51b519c578733fec563e6a6da7f5be2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ifAP3NUbUZxXhzP+xWPmptp/W+I=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
commoner@^0.10.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.10.8"
resolved "https://registry.yarnpkg.com/commoner/-/commoner-0.10.8.tgz#34fc3672cd24393e8bb47e70caa0293811f4f2c5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-NPw2cs0kOT6LtH5wyqApOBH08sU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
commander "^2.5.0"
detective "^4.3.1"
glob "^5.0.15"
graceful-fs "^4.1.2"
iconv-lite "^0.4.5"
mkdirp "^0.5.0"
private "^0.1.6"
q "^1.1.2"
recast "^0.11.17"
compare-func@^1.3.1:
version "1.3.2"
resolved "https://registry.yarnpkg.com/compare-func/-/compare-func-1.3.2.tgz#99dd0ba457e1f9bc722b12c08ec33eeab31fa648"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-md0LpFfh+bxyKxLAjsM+6rMfpkg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
array-ify "^1.0.0"
dot-prop "^3.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
compare-semver@^1.0.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/compare-semver/-/compare-semver-1.1.0.tgz#7c0a79a27bb80b6c6994445f82958259d3d02153"
integrity sha1-fAp5onu4C2xplERfgpWCWdPQIVM=
dependencies:
semver "^5.0.1"
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
comparify@^0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/comparify/-/comparify-0.2.0.tgz#c1fd6aa1e1df222bbf10b0bbf17198397e70c66d"
integrity sha1-wf1qoeHfIiu/ELC78XGYOX5wxm0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
component-bind@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/component-bind/-/component-bind-1.0.0.tgz#00c608ab7dcd93897c0009651b1d3a8e1e73bbd1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-AMYIq33Nk4l8AAllGx06jh5zu9E=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
component-emitter@1.2.1, component-emitter@^1.2.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.2.1"
resolved "https://registry.yarnpkg.com/component-emitter/-/component-emitter-1.2.1.tgz#137918d6d78283f7df7a6b7c5a63e140e69425e6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-E3kY1teCg/ffemt8WmPhQOaUJeY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
component-inherit@0.0.3:
version "0.0.3"
resolved "https://registry.yarnpkg.com/component-inherit/-/component-inherit-0.0.3.tgz#645fc4adf58b72b649d5cae65135619db26ff143"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ZF/ErfWLcrZJ1crmUTVhnbJv8UM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
compress-commons@^1.2.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.2.2"
resolved "https://registry.yarnpkg.com/compress-commons/-/compress-commons-1.2.2.tgz#524a9f10903f3a813389b0225d27c48bb751890f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-UkqfEJA/OoEzibAiXSfEi7dRiQ8=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
buffer-crc32 "^0.2.1"
crc32-stream "^2.0.0"
normalize-path "^2.0.0"
readable-stream "^2.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
compressible@^2.0.12, compressible@~2.0.14:
version "2.0.15"
resolved "https://registry.yarnpkg.com/compressible/-/compressible-2.0.15.tgz#857a9ab0a7e5a07d8d837ed43fe2defff64fe212"
integrity sha512-4aE67DL33dSW9gw4CI2H/yTxqHLNcxp0yS6jB+4h+wr3e43+1z7vm0HU9qXOH8j+qjKuL8+UtkOxYQSMq60Ylw==
dependencies:
mime-db ">= 1.36.0 < 2"
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
compressible@~2.0.5:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "2.0.14"
resolved "https://registry.yarnpkg.com/compressible/-/compressible-2.0.14.tgz#326c5f507fbb055f54116782b969a81b67a29da7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-MmxfUH+7BV9UEWeCuWmoG2einac=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
mime-db ">= 1.34.0 < 2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
compression@^1.7.0:
version "1.7.3"
resolved "https://registry.yarnpkg.com/compression/-/compression-1.7.3.tgz#27e0e176aaf260f7f2c2813c3e440adb9f1993db"
integrity sha512-HSjyBG5N1Nnz7tF2+O7A9XUhyjru71/fwgNb7oIsEVHR0WShfs2tIS/EySLgiTe98aOK18YDlMXpzjCXY/n9mg==
dependencies:
accepts "~1.3.5"
bytes "3.0.0"
compressible "~2.0.14"
debug "2.6.9"
on-headers "~1.0.1"
safe-buffer "5.1.2"
vary "~1.1.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
compression@~1.5.2:
version "1.5.2"
build: secure yarn lock files (#31640) See https://yarnpkg.com/blog/2019/07/12/recommended-security-update/ PR Close #31640
2019-07-18 20:34:37 -04:00
resolved "https://registry.npmjs.org/compression/-/compression-1.5.2.tgz#b03b8d86e6f8ad29683cba8df91ddc6ffc77b395"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-sDuNhub4rSloPLqN+R3cb/x3s5U=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
accepts "~1.2.12"
bytes "2.1.0"
compressible "~2.0.5"
debug "~2.2.0"
on-headers "~1.0.0"
vary "~1.0.1"
concat-map@0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/concat-map/-/concat-map-0.0.1.tgz#d8a96bd77fd68df7793a73036a3ba0d5405d477b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-2Klr13/Wjfd5OnMDajug1UBdR3s=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
concat-stream@^1.4.7, concat-stream@^1.5.0, concat-stream@^1.6.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.6.2"
resolved "https://registry.yarnpkg.com/concat-stream/-/concat-stream-1.6.2.tgz#904bdf194cd3122fc675c77fc4ac3d4ff0fd1a34"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-27HBghJxjiZtIk3Ycvn/4kbJk/1uZuJFfuPEns6LaEvpvG1f0hTea8lilrouyo9mVc2GWdcEZ8OLoGmSADlrCw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
buffer-from "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
inherits "^2.0.3"
readable-stream "^2.2.2"
typedarray "^0.0.6"
config-chain@~1.1.8:
version "1.1.11"
resolved "https://registry.yarnpkg.com/config-chain/-/config-chain-1.1.11.tgz#aba09747dfbe4c3e70e766a6e41586e1859fc6f2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-q6CXR9++TD5w52am5BWG4YWfxvI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
ini "^1.3.4"
proto-list "~1.2.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
configstore@^1.2.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/configstore/-/configstore-1.4.0.tgz#c35781d0501d268c25c54b8b17f6240e8a4fb021"
integrity sha1-w1eB0FAdJowlxUuLF/YkDopPsCE=
dependencies:
graceful-fs "^4.1.2"
mkdirp "^0.5.0"
object-assign "^4.0.1"
os-tmpdir "^1.0.0"
osenv "^0.1.0"
uuid "^2.0.1"
write-file-atomic "^1.1.2"
xdg-basedir "^2.0.0"
configstore@^3.0.0, configstore@^3.1.2:
version "3.1.2"
resolved "https://registry.yarnpkg.com/configstore/-/configstore-3.1.2.tgz#c6f25defaeef26df12dd33414b001fe81a543f8f"
integrity sha512-vtv5HtGjcYUgFrXc6Kx747B83MRRVS5R1VTEQoXvuP+kMI+if6uywV0nDGoiydJRy4yk7h9od5Og0kxx4zUXmw==
dependencies:
dot-prop "^4.1.0"
graceful-fs "^4.1.2"
make-dir "^1.0.0"
unique-string "^1.0.0"
write-file-atomic "^2.0.0"
xdg-basedir "^3.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
connect-livereload@^0.5.4:
version "0.5.4"
resolved "https://registry.yarnpkg.com/connect-livereload/-/connect-livereload-0.5.4.tgz#80157d1371c9f37cc14039ab1895970d119dc3bc"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-gBV9E3HJ83zBQDmrGJWXDRGdw7w=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
connect-query@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/connect-query/-/connect-query-1.0.0.tgz#de44f577209da2404d1fc04692d1a4118e582119"
integrity sha1-3kT1dyCdokBNH8BGktGkEY5YIRk=
dependencies:
qs "~6.4.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
connect-timeout@~1.6.2:
version "1.6.2"
resolved "https://registry.yarnpkg.com/connect-timeout/-/connect-timeout-1.6.2.tgz#de9a5ec61e33a12b6edaab7b5f062e98c599b88e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-3ppexh4zoStu2qt7XwYumMWZuI4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
debug "~2.2.0"
http-errors "~1.3.1"
ms "0.7.1"
on-headers "~1.0.0"
connect@^2.30.0:
version "2.30.2"
resolved "https://registry.yarnpkg.com/connect/-/connect-2.30.2.tgz#8da9bcbe8a054d3d318d74dfec903b5c39a1b609"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-jam8vooFTT0xjXTf7JA7XDmhtgk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
basic-auth-connect "1.0.0"
body-parser "~1.13.3"
bytes "2.1.0"
compression "~1.5.2"
connect-timeout "~1.6.2"
content-type "~1.0.1"
cookie "0.1.3"
cookie-parser "~1.3.5"
cookie-signature "1.0.6"
csurf "~1.8.3"
debug "~2.2.0"
depd "~1.0.1"
errorhandler "~1.4.2"
express-session "~1.11.3"
finalhandler "0.4.0"
fresh "0.3.0"
http-errors "~1.3.1"
method-override "~2.3.5"
morgan "~1.6.1"
multiparty "3.3.2"
on-headers "~1.0.0"
parseurl "~1.3.0"
pause "0.1.0"
qs "4.0.0"
response-time "~2.3.1"
serve-favicon "~2.3.0"
serve-index "~1.7.2"
serve-static "~1.10.0"
type-is "~1.6.6"
utils-merge "1.0.0"
vhost "~3.0.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
connect@^3.6.0, connect@^3.6.2:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "3.6.6"
resolved "https://registry.yarnpkg.com/connect/-/connect-3.6.6.tgz#09eff6c55af7236e137135a72574858b6786f524"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Ce/2xVr3I24TcTWnJXSFi2eG9SQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
debug "2.6.9"
finalhandler "1.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
parseurl "~1.3.2"
utils-merge "1.0.1"
console-browserify@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/console-browserify/-/console-browserify-1.1.0.tgz#f0241c45730a9fc6323b206dbf38edc741d0bb10"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8CQcRXMKn8YyOyBtvzjtx0HQuxA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
date-now "^0.1.4"
console-control-strings@^1.0.0, console-control-strings@~1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/console-control-strings/-/console-control-strings-1.1.0.tgz#3d7cf4464db6446ea644bf4b39507f9851008e8e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-PXz0Rk22RG6mRL9LOVB/mFEAjo4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
constants-browserify@0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/constants-browserify/-/constants-browserify-0.0.1.tgz#92577db527ba6c4cf0a4568d84bc031f441e21f2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-kld9tSe6bEzwpFaNhLwDH0QeIfI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
content-disposition@0.5.2:
version "0.5.2"
resolved "https://registry.yarnpkg.com/content-disposition/-/content-disposition-0.5.2.tgz#0cf68bb9ddf5f2be7961c3a85178cb85dba78cb4"
integrity sha1-DPaLud318r55YcOoUXjLhdunjLQ=
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
content-type@~1.0.1, content-type@~1.0.4:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.4"
resolved "https://registry.yarnpkg.com/content-type/-/content-type-1.0.4.tgz#e138cc75e040c727b1966fe5e5f8c9aee256fe3b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-hIP3EEPs8tB9AT1L+NUqtwOAps4mk2Zob89MWXMHjHWg9milF/j4osnnQLXBCBFBk/tvIG/tUc9mOUJiPBhPXA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-changelog-angular@^1.6.6:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.6.6"
resolved "https://registry.yarnpkg.com/conventional-changelog-angular/-/conventional-changelog-angular-1.6.6.tgz#b27f2b315c16d0a1f23eb181309d0e6a4698ea0f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-suQnFSqCxRwyBxY68pYTsFkG0taIdinHLNEAX5ivtw8bCRnIgnpvcHmlR/yjUyZIrNPYAoXlY1WiEKWgSE4BNg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
compare-func "^1.3.1"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
q "^1.5.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-changelog-atom@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/conventional-changelog-atom/-/conventional-changelog-atom-2.0.0.tgz#cd6453469cfb8fc345af3391b92990251c95558b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-ygwkwyTQYAm4S0tsDt+1yg8tHhRrv7qu9SOWPhNQlVrInFLsfKc0FActCA3de2ChknxpVPY2B53yhKvCAtkBCg==
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
q "^1.5.1"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-changelog-codemirror@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/conventional-changelog-codemirror/-/conventional-changelog-codemirror-2.0.0.tgz#bfb61ccabacdd3bf8425a5cbe92276c86c5a0c1e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-pZt/YynJ5m8C9MGV5wkBuhM1eX+8a84fmNrdOylxg/lJV+lgtAiNhnpskNuixtf71iKVWSlEqMQ6z6CH7/Uo5A==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
q "^1.5.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-changelog-core@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/conventional-changelog-core/-/conventional-changelog-core-3.1.0.tgz#96a81bb3301b4b2a3dc2851cc54c5fb674ac1942"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-bcZkcFXkqVgG2W8m/1wjlp2wn/BKDcrPgw3/mvSEQtzs8Pax8JbAPFpEQReHY92+EKNNXC67wLA8y2xcNx0rDA==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-changelog-writer "^4.0.0"
conventional-commits-parser "^3.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dateformat "^3.0.0"
get-pkg-repo "^1.0.0"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
git-raw-commits "^2.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
git-remote-origin-url "^2.0.0"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
git-semver-tags "^2.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
lodash "^4.2.1"
normalize-package-data "^2.3.5"
q "^1.5.1"
read-pkg "^1.1.0"
read-pkg-up "^1.0.1"
through2 "^2.0.0"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-changelog-ember@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/conventional-changelog-ember/-/conventional-changelog-ember-2.0.1.tgz#5a5595b9ed50a6daca4bd3508a47ffe4a1a7152f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-Ym1xLi7YLGooLUpHCJhlXJW5V7u/g+hlYD/+HKt0KqG2qbiBi7e7/HO9aScXTEKUBGMm7m4C443R+eCWQI2ynA==
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
q "^1.5.1"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-changelog-eslint@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/conventional-changelog-eslint/-/conventional-changelog-eslint-3.0.0.tgz#cc5376cb29a622c1ade197e155bf054640c05cd3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-Acn20v+13c+o1OAWKvc9sCCl73Nj2vOMyn+G82euiMZwgYNE9CcBkTnw/GKdBi9KiZMK9uy+SCQ/QyAEE+8vZA==
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
q "^1.5.1"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-changelog-express@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/conventional-changelog-express/-/conventional-changelog-express-2.0.0.tgz#d3d020118fbfce21a75e025ec097101e355a2361"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-2svPjeXCrjwwqnzu/f3qU5LWoLO0jmUIEbtbbSRXAAP9Ag+137b484eJsiRt9DPYXSVzog0Eoek3rvCzfHcphQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
q "^1.5.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
conventional-changelog-jquery@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/conventional-changelog-jquery/-/conventional-changelog-jquery-0.1.0.tgz#0208397162e3846986e71273b6c79c5b5f80f510"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Agg5cWLjhGmG5xJztsecW1+A9RA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
q "^1.4.1"
conventional-changelog-jscs@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/conventional-changelog-jscs/-/conventional-changelog-jscs-0.1.0.tgz#0479eb443cc7d72c58bf0bcf0ef1d444a92f0e5c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-BHnrRDzH1yxYvwvPDvHURKkvDlw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
q "^1.4.1"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-changelog-jshint@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/conventional-changelog-jshint/-/conventional-changelog-jshint-2.0.0.tgz#7a038330f485082e489f47f5d07539036949f87d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-+4fCln755N0ZzRUEdcDWR5Due71Dsqkbov6K/UmVCnljZvhVh0/wpT4YROoSsAnhfZO8shyWDPFKm6EP20pLQg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
compare-func "^1.3.1"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
q "^1.5.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-changelog-preset-loader@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/conventional-changelog-preset-loader/-/conventional-changelog-preset-loader-2.0.1.tgz#d134734e0cc1b91b88b30586c5991f31442029f1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-HiSfhXNzAzG9klIqJaA97MMiNBR4js+53g4Px0k7tgKeCNVXmrDrm+CY+nIqcmG5NVngEPf8rAr7iji1TWW7zg==
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-changelog-writer@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/conventional-changelog-writer/-/conventional-changelog-writer-4.0.0.tgz#3ed983c8ef6a3aa51fe44e82c9c75e86f1b5aa42"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-hMZPe0AQ6Bi05epeK/7hz80xxk59nPA5z/b63TOHq2wigM0/akreOc8N4Jam5b9nFgKWX1e9PdPv2ewgW6bcfg==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
compare-func "^1.3.1"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-commits-filter "^2.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dateformat "^3.0.0"
handlebars "^4.0.2"
json-stringify-safe "^5.0.1"
lodash "^4.2.1"
meow "^4.0.0"
semver "^5.5.0"
split "^1.0.0"
through2 "^2.0.0"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-changelog@^2.0.3:
version "2.0.3"
resolved "https://registry.yarnpkg.com/conventional-changelog/-/conventional-changelog-2.0.3.tgz#779cff582c0091d2b24574003eaa82ef5ddf653d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-4bcII9cJHSKb2qi9e8qGF6aJHLf/AB0dokhyR+X6QILTMl77s4l163vK+reXhajvfOYbbHQvsrWybr5+PKZwNA==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
conventional-changelog-angular "^1.6.6"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-changelog-atom "^2.0.0"
conventional-changelog-codemirror "^2.0.0"
conventional-changelog-core "^3.1.0"
conventional-changelog-ember "^2.0.1"
conventional-changelog-eslint "^3.0.0"
conventional-changelog-express "^2.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
conventional-changelog-jquery "^0.1.0"
conventional-changelog-jscs "^0.1.0"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-changelog-jshint "^2.0.0"
conventional-changelog-preset-loader "^2.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-commits-filter@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/conventional-commits-filter/-/conventional-commits-filter-2.0.0.tgz#a0ce1d1ff7a1dd7fab36bee8e8256d348d135651"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-Cfl0j1/NquB/TMVx7Wrmyq7uRM+/rPQbtVVGwzfkhZ6/yH6fcMmP0Q/9044TBZPTNdGzm46vXFXL14wbET0/Mg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-subset "^0.1.1"
modify-values "^1.0.0"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
conventional-commits-parser@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/conventional-commits-parser/-/conventional-commits-parser-3.0.0.tgz#7f604549a50bd8f60443fbe515484b1c2f06a5c4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-GWh71U26BLWgMykCp+VghZ4s64wVbtseECcKQ/PvcPZR2cUnz+FUc2J9KjxNl7/ZbCxST8R03c9fc+Vi0umS9Q==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
JSONStream "^1.0.4"
is-text-path "^1.0.0"
lodash "^4.2.1"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
meow "^4.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
split2 "^2.0.0"
through2 "^2.0.0"
trim-off-newlines "^1.0.0"
build: add dependencies to be used by ngcc (#24897) PR Close #24897
2018-07-16 02:08:48 -04:00
convert-source-map@^1.5.1:
version "1.5.1"
resolved "https://registry.yarnpkg.com/convert-source-map/-/convert-source-map-1.5.1.tgz#b8278097b9bc229365de5c62cf5fcaed8b5599e5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-uCeAl7m8IpNl3lxiz1/K7YtVmeU=
build: add dependencies to be used by ngcc (#24897) PR Close #24897
2018-07-16 02:08:48 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
cookie-parser@~1.3.5:
version "1.3.5"
resolved "https://registry.yarnpkg.com/cookie-parser/-/cookie-parser-1.3.5.tgz#9d755570fb5d17890771227a02314d9be7cf8356"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nXVVcPtdF4kHcSJ6AjFNm+fPg1Y=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
cookie "0.1.3"
cookie-signature "1.0.6"
cookie-signature@1.0.6:
version "1.0.6"
resolved "https://registry.yarnpkg.com/cookie-signature/-/cookie-signature-1.0.6.tgz#e303a882b342cc3ee8ca513a79999734dab3ae2c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-4wOogrNCzD7oylE6eZmXNNqzriw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
cookie@0.1.3:
version "0.1.3"
resolved "https://registry.yarnpkg.com/cookie/-/cookie-0.1.3.tgz#e734a5c1417fce472d5aef82c381cabb64d1a435"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-5zSlwUF/zkctWu+Cw4HKu2TRpDU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
cookie@0.3.1:
version "0.3.1"
resolved "https://registry.yarnpkg.com/cookie/-/cookie-0.3.1.tgz#e7e0a1f9ef43b4c8ba925c5c5a96e806d16873bb"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-5+Ch+e9DtMi6klxcWpboBtFoc7s=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
copy-concurrently@^1.0.0:
version "1.0.5"
resolved "https://registry.yarnpkg.com/copy-concurrently/-/copy-concurrently-1.0.5.tgz#92297398cae34937fcafd6ec8139c18051f0b5e0"
integrity sha512-f2domd9fsVDFtaFcbaRZuYXwtdmnzqbADSwhSWYxYB/Q8zsdUUFMXVRwXGDMWmbEzAn1kdRrtI1T/KTFOL4X2A==
dependencies:
aproba "^1.1.1"
fs-write-stream-atomic "^1.0.8"
iferr "^0.1.5"
mkdirp "^0.5.1"
rimraf "^2.5.4"
run-queue "^1.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
copy-descriptor@^0.1.0:
version "0.1.1"
resolved "https://registry.yarnpkg.com/copy-descriptor/-/copy-descriptor-0.1.1.tgz#676f6eb3c39997c2ee1ac3a924fd6124748f578d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Z29us8OZl8LuGsOpJP1hJHSPV40=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
core-js@^2.2.0, core-js@^2.4.0, core-js@^2.4.1:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "2.5.7"
resolved "https://registry.yarnpkg.com/core-js/-/core-js-2.5.7.tgz#f972608ff0cead68b841a16a932d0b183791814e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-RszJCAxg/PP6uzXVXL6BsxSXx/B05oJAQ2vkJRjyjrEcNVycaqOmNb5OTxZPE3xa5gwZduqza6L9JOCenh/Ecw==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
core-js@~2.3.0:
version "2.3.0"
resolved "https://registry.yarnpkg.com/core-js/-/core-js-2.3.0.tgz#fab83fbb0b2d8dc85fa636c4b9d34c75420c6d65"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+rg/uwstjchfpjbEudNMdUIMbWU=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
core-util-is@1.0.2, core-util-is@~1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/core-util-is/-/core-util-is-1.0.2.tgz#b5fd54220aa2bc5ab57aab7140c940754503c1a7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-tf1UIgqivFq1eqtxQMlAdUUDwac=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
cors@2.8.4:
version "2.8.4"
resolved "https://registry.yarnpkg.com/cors/-/cors-2.8.4.tgz#2bd381f2eb201020105cd50ea59da63090694686"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-K9OB8usgECAQXNUOpZ2mMJBpRoY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
object-assign "^4"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
vary "^1"
build: update to rules_nodejs 0.38 (#32889) PR Close #32889
2019-09-27 18:49:59 -04:00
corser@~2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/corser/-/corser-2.0.1.tgz#8eda252ecaab5840dcd975ceb90d9370c819ff87"
integrity sha1-jtolLsqrWEDc2XXOuQ2TcMgZ/4c=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
crc32-stream@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/crc32-stream/-/crc32-stream-2.0.0.tgz#e3cdd3b4df3168dd74e3de3fbbcb7b297fe908f4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-483TtN8xaN10494/u8t7KX/pCPQ=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
crc "^3.4.4"
readable-stream "^2.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
crc@3.3.0:
version "3.3.0"
resolved "https://registry.yarnpkg.com/crc/-/crc-3.3.0.tgz#fa622e1bc388bf257309082d6b65200ce67090ba"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+mIuG8OIvyVzCQgta2UgDOZwkLo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
crc@^3.4.4:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "3.5.0"
resolved "https://registry.yarnpkg.com/crc/-/crc-3.5.0.tgz#98b8ba7d489665ba3979f59b21381374101a1964"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-mLi6fUiWZbo5efWbITgTdBAaGWQ=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
create-error-class@^3.0.0, create-error-class@^3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/create-error-class/-/create-error-class-3.0.2.tgz#06be7abef947a3f14a30fd610671d401bca8b7b6"
integrity sha1-Br56vvlHo/FKMP1hBnHUAbyot7Y=
dependencies:
capture-stack-trace "^1.0.0"
cross-env@^5.1.3:
version "5.2.0"
resolved "https://registry.yarnpkg.com/cross-env/-/cross-env-5.2.0.tgz#6ecd4c015d5773e614039ee529076669b9d126f2"
integrity sha512-jtdNFfFW1hB7sMhr/H6rW1Z45LFqyI431m3qU6bFXcQ3Eh7LtBuG3h74o7ohHZ3crrRkkqHlo4jYHFPcjroANg==
dependencies:
cross-spawn "^6.0.5"
is-windows "^1.0.0"
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
cross-spawn@^4, cross-spawn@^4.0.0:
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
version "4.0.2"
resolved "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-4.0.2.tgz#7b9247621c23adfdd3856004a823cbe397424d41"
integrity sha1-e5JHYhwjrf3ThWAEqCPL45dCTUE=
dependencies:
lru-cache "^4.0.1"
which "^1.2.9"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
cross-spawn@^5.0.1:
version "5.1.0"
resolved "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-5.1.0.tgz#e8bd0efee58fcff6f8f94510a0a554bbfa235449"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-6L0O/uWPz/b4+UUQoKVUu/ojVEk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
lru-cache "^4.0.1"
shebang-command "^1.2.0"
which "^1.2.9"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
cross-spawn@^6.0.0, cross-spawn@^6.0.5:
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
version "6.0.5"
resolved "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-6.0.5.tgz#4a5ec7c64dfae22c3a14124dbacdee846d80cbc4"
integrity sha512-eTVLrBSt7fjbDygz805pMnstIs2VTBNkRm0qxZd+M7A5XDdxVRWO5MxGBXZhjY4cqLYLdtrGqRf8mBPmzwSpWQ==
dependencies:
nice-try "^1.0.4"
path-key "^2.0.1"
semver "^5.5.0"
shebang-command "^1.2.0"
which "^1.2.9"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
cryptiles@2.x.x:
version "2.0.5"
resolved "https://registry.yarnpkg.com/cryptiles/-/cryptiles-2.0.5.tgz#3bdfecdc608147c1c67202fa291e7dca59eaa3b8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-O9/s3GCBR8HGcgL6KR59ylnqo7g=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
boom "2.x.x"
crypto-browserify@~3.2.6:
version "3.2.8"
resolved "https://registry.yarnpkg.com/crypto-browserify/-/crypto-browserify-3.2.8.tgz#b9b11dbe6d9651dd882a01e6cc467df718ecf189"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ubEdvm2WUd2IKgHmzEZ99xjs8Yk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
pbkdf2-compat "2.0.1"
ripemd160 "0.2.0"
sha.js "2.2.6"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
crypto-random-string@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/crypto-random-string/-/crypto-random-string-1.0.0.tgz#a230f64f568310e1498009940790ec99545bca7e"
integrity sha1-ojD2T1aDEOFJgAmUB5DsmVRbyn4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
csrf@~3.0.0:
version "3.0.6"
resolved "https://registry.yarnpkg.com/csrf/-/csrf-3.0.6.tgz#b61120ddceeafc91e76ed5313bb5c0b2667b710a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-thEg3c7q/JHnbtUxO7XAsmZ7cQo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
rndm "1.2.0"
tsscmp "1.0.5"
uid-safe "2.1.4"
csurf@~1.8.3:
version "1.8.3"
resolved "https://registry.yarnpkg.com/csurf/-/csurf-1.8.3.tgz#23f2a13bf1d8fce1d0c996588394442cba86a56a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-I/KhO/HY/OHQyZZYg5RELLqGpWo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
cookie "0.1.3"
cookie-signature "1.0.6"
csrf "~3.0.0"
http-errors "~1.3.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
csv-streamify@^3.0.4:
version "3.0.4"
resolved "https://registry.yarnpkg.com/csv-streamify/-/csv-streamify-3.0.4.tgz#4cb614c57e3f299cca17b63fdcb4ad167777f47a"
integrity sha1-TLYUxX4/KZzKF7Y/3LStFnd39Ho=
dependencies:
through2 "2.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
currently-unhandled@^0.4.1:
version "0.4.1"
resolved "https://registry.yarnpkg.com/currently-unhandled/-/currently-unhandled-0.4.1.tgz#988df33feab191ef799a61369dd76c17adf957ea"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-mI3zP+qxke95mmE2nddsF635V+o=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
array-find-index "^1.0.1"
custom-event@~1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/custom-event/-/custom-event-1.0.1.tgz#5d02a46850adf1b4a317946a3928fccb5bfd0425"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-XQKkaFCt8bSjF5RqOSj8y1v9BCU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
cycle@1.0.x:
version "1.0.3"
resolved "https://registry.yarnpkg.com/cycle/-/cycle-1.0.3.tgz#21e80b2be8580f98b468f379430662b046c34ad2"
integrity sha1-IegLK+hYD5i0aPN5QwZisEbDStI=
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
cyclist@~0.2.2:
version "0.2.2"
resolved "https://registry.yarnpkg.com/cyclist/-/cyclist-0.2.2.tgz#1b33792e11e914a2fd6d6ed6447464444e5fa640"
integrity sha1-GzN5LhHpFKL9bW7WRHRkRE5fpkA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
d@1:
version "1.0.0"
resolved "https://registry.yarnpkg.com/d/-/d-1.0.0.tgz#754bb5bfe55451da69a58b94d45f4c5b0462d58f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-dUu1v+VUUdpppYuU1F9MWwRi1Y8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
es5-ext "^0.10.9"
dargs@^4.0.1:
version "4.1.0"
resolved "https://registry.yarnpkg.com/dargs/-/dargs-4.1.0.tgz#03a9dbb4b5c2f139bf14ae53f0b8a2a6a86f4e17"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-A6nbtLXC8Tm/FK5T8LiipqhvThc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
number-is-nan "^1.0.0"
dashdash@^1.12.0:
version "1.14.1"
resolved "https://registry.yarnpkg.com/dashdash/-/dashdash-1.14.1.tgz#853cfa0f7cbe2fed5de20326b8dd581035f6e2f0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-hTz6D3y+L+1d4gMmuN1YEDX24vA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
assert-plus "^1.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
date-format@^1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/date-format/-/date-format-1.2.0.tgz#615e828e233dd1ab9bb9ae0950e0ceccfa6ecad8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-YV6CjiM90aubua4JUODOzPpuytg=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
date-format@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/date-format/-/date-format-2.1.0.tgz#31d5b5ea211cf5fd764cd38baf9d033df7e125cf"
integrity sha512-bYQuGLeFxhkxNOF3rcMtiZxvCBAquGzZm6oWA1oZ0g2THUzivaRhv8uOhdr19LmoobSOLoIAxeUK2RdbM8IFTA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
date-now@^0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/date-now/-/date-now-0.1.4.tgz#eaf439fd4d4848ad74e5cc7dbef200672b9e345b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-6vQ5/U1ISK105cx9vvIAZyueNFs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dateformat@^2.0.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/dateformat/-/dateformat-2.2.0.tgz#4065e2013cf9fb916ddfd82efb506ad4c6769062"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-QGXiATz5+5Ft39gu+1Bq1MZ2kGI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dateformat@^3.0.0:
version "3.0.3"
resolved "https://registry.yarnpkg.com/dateformat/-/dateformat-3.0.3.tgz#a6e37499a4d9a9cf85ef5872044d62901c9889ae"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-jyCETtSl3VMZMWeRo7iY1FL19ges1t55hMo5yaam4Jrsm5EPL89UQkoQRyiI+Yf4k8r2ZpdngkV8hr1lIdjb3Q==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
debug@2, debug@2.6.9, debug@^2.1.2, debug@^2.2.0, debug@^2.3.3:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "2.6.9"
resolved "https://registry.yarnpkg.com/debug/-/debug-2.6.9.tgz#5d128515df134ff327e90a4c93f4e077a536341f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
ms "2.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
debug@3.1.0, debug@=3.1.0, debug@~3.1.0:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "3.1.0"
resolved "https://registry.yarnpkg.com/debug/-/debug-3.1.0.tgz#5bb5a0672628b64149566ba16819e61518c67261"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-OX8XqP7/1a9cqkxYw2yXss15f26NKWBpDXQd0/uK/KPqdQhxbPa994hnzjcE2VqQpDslf55723cKPUOGSmMY3g==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
ms "2.0.0"
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
debug@^3.0.0, debug@^3.1.0, debug@^3.2.6:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "3.2.6"
resolved "https://registry.yarnpkg.com/debug/-/debug-3.2.6.tgz#e83d17de16d8a7efb7717edbe5fb10135eee629b"
integrity sha512-mel+jf7nrtEl5Pn1Qx46zARXKDpBbvzezse7p7LqINmdoIk8PYP5SySaxEmYv6TZ0JyEKA1hsCId6DIhgITtWQ==
dependencies:
ms "^2.1.1"
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
debug@^4.1.1:
version "4.1.1"
resolved "https://registry.yarnpkg.com/debug/-/debug-4.1.1.tgz#3b72260255109c6b589cee050f1d516139664791"
integrity sha512-pYAIzeRo8J6KPEaJ0VWOh5Pzkbw/RetuzehGM7QRRX5he4fPHx2rdKMB256ehJCkX+XRQm16eZLqLNS8RSZXZw==
dependencies:
ms "^2.1.1"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
debug@~2.2.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/debug/-/debug-2.2.0.tgz#f87057e995b1a1f6ae6a4960664137bc56f039da"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+HBX6ZWxofauaklgZkE3vFbwOdo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
ms "0.7.1"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
decamelize-keys@^1.0.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/decamelize-keys/-/decamelize-keys-1.1.0.tgz#d171a87933252807eb3cb61dc1c1445d078df2d9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-0XGoeTMlKAfrPLYdwcFEXQeN8tk=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
decamelize "^1.1.0"
map-obj "^1.0.0"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
decamelize@^1.0.0, decamelize@^1.1.0, decamelize@^1.1.1, decamelize@^1.1.2, decamelize@^1.2.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/decamelize/-/decamelize-1.2.0.tgz#f6534d15148269b20352e7bee26f501f9a191290"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-9lNNFRSCabIDUue+4m9QH5oZEpA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
decode-uri-component@^0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/decode-uri-component/-/decode-uri-component-0.2.0.tgz#eb3913333458775cb84cd1a1fae062106bb87545"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-6zkTMzRYd1y4TNGh+uBiEGu4dUU=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
decompress-response@^3.3.0:
version "3.3.0"
resolved "https://registry.yarnpkg.com/decompress-response/-/decompress-response-3.3.0.tgz#80a4dd323748384bfa248083622aedec982adff3"
integrity sha1-gKTdMjdIOEv6JICDYirt7Jgq3/M=
dependencies:
mimic-response "^1.0.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
decompress-zip@0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/decompress-zip/-/decompress-zip-0.3.0.tgz#ae3bcb7e34c65879adfe77e19c30f86602b4bdb0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-rjvLfjTGWHmt/nfhnDD4ZgK0vbA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
binary "^0.3.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
graceful-fs "^4.1.3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
mkpath "^0.1.0"
nopt "^3.0.1"
q "^1.1.2"
readable-stream "^1.1.8"
touch "0.0.3"
build(bazel): remove @ts-api-guardian_deps yarn_install (#29799) PR Close #29799
2019-04-09 21:08:13 -04:00
deep-eql@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/deep-eql/-/deep-eql-3.0.1.tgz#dfc9404400ad1c8fe023e7da1df1c147c4b444df"
integrity sha512-+QeIQyN5ZuO+3Uk5DYh6/1eKO0m0YmJFGNmFHGACpf1ClL1nmlV/p4gNgbl2pJGxgXb4faqo6UE+M5ACEMyVcw==
dependencies:
type-detect "^4.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
deep-equal@~0.2.1:
version "0.2.2"
resolved "https://registry.yarnpkg.com/deep-equal/-/deep-equal-0.2.2.tgz#84b745896f34c684e98f2ce0e42abaf43bba017d"
integrity sha1-hLdFiW80xoTpjyzg5Cq69Du6AX0=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
deep-extend@^0.6.0:
version "0.6.0"
resolved "https://registry.yarnpkg.com/deep-extend/-/deep-extend-0.6.0.tgz#c4fa7c95404a17a9c3e8ca7e1537312b736330ac"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-LOHxIOaPYdHlJRtCQfDIVZtfw/ufM8+rVj649RIHzcm/vGwQRXFt6OPqIFWsm2XEMrNIEtWR64sY1LEKD2vAOA==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
deep-is@~0.1.3:
version "0.1.3"
resolved "https://registry.yarnpkg.com/deep-is/-/deep-is-0.1.3.tgz#b369d6fb5dbc13eecf524f91b070feedc357cf34"
integrity sha1-s2nW+128E+7PUk+RsHD+7cNXzzQ=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
deepcopy@0.6.3:
version "0.6.3"
resolved "https://registry.yarnpkg.com/deepcopy/-/deepcopy-0.6.3.tgz#634780f2f8656ab771af8fa8431ed1ccee55c7b0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Y0eA8vhlardxr4+oQx7RzO5Vx7A=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
defaults@^1.0.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.3"
resolved "https://registry.yarnpkg.com/defaults/-/defaults-1.0.3.tgz#c656051e9817d9ff08ed881477f3fe4019f3ef7d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-xlYFHpgX2f8I7YgUd/P+QBnz730=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
clone "^1.0.2"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
define-property@^0.2.5:
version "0.2.5"
resolved "https://registry.yarnpkg.com/define-property/-/define-property-0.2.5.tgz#c35b1ef918ec3c990f9a5bc57be04aacec5c8116"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-w1se+RjsPJkPmlvFe+BKrOxcgRY=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
is-descriptor "^0.1.0"
define-property@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/define-property/-/define-property-1.0.0.tgz#769ebaaf3f4a63aad3af9e8d304c9bbe79bfb0e6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-dp66rz9KY6rTr56NMEybvnm/sOY=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
is-descriptor "^1.0.0"
define-property@^2.0.2:
version "2.0.2"
resolved "https://registry.yarnpkg.com/define-property/-/define-property-2.0.2.tgz#d459689e8d654ba77e02a817f8710d702cb16e9d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-jwK2UV4cnPpbcG7+VRARKTZPUWowwXA8bzH5NP6ud0oeAxyYPuGZUAC7hMugpCdz4BeSZl2Dl9k66CHJ/46ZYQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
is-descriptor "^1.0.2"
isobject "^3.0.1"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
defined@^1.0.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.0"
resolved "https://registry.yarnpkg.com/defined/-/defined-1.0.0.tgz#c98d9bcef75674188e110969151199e39b1fa693"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-yY2bzvdWdBiOEQlpFRGZ45sfppM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
del@^2.2.0:
version "2.2.2"
resolved "https://registry.yarnpkg.com/del/-/del-2.2.2.tgz#c12c981d067846c84bcaf862cff930d907ffd1a8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wSyYHQZ4RshLyvhiz/kw2Qf/0ag=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
globby "^5.0.0"
is-path-cwd "^1.0.0"
is-path-in-cwd "^1.0.0"
object-assign "^4.0.1"
pify "^2.0.0"
pinkie-promise "^2.0.0"
rimraf "^2.2.8"
delayed-stream@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/delayed-stream/-/delayed-stream-1.0.0.tgz#df3ae199acadfb7d440aaae0b29e2272b24ec619"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-3zrhmayt+31ECqrgsp4icrJOxhk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
delegates@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/delegates/-/delegates-1.0.0.tgz#84c6e159b81904fdca59a0ef44cd870d31250f9a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-hMbhWbgZBP3KWaDvRM2HDTElD5o=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
depd@~1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/depd/-/depd-1.0.1.tgz#80aec64c9d6d97e65cc2a9caa93c0aa6abf73aaa"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-gK7GTJ1tl+ZcwqnKqTwKpqv3Oqo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
depd@~1.1.0, depd@~1.1.2:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.1.2"
resolved "https://registry.yarnpkg.com/depd/-/depd-1.1.2.tgz#9bcd52e14c097763e749b274c4346ed2e560b5a9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-m81S4UwJd2PnSbJ0xDRu0uVgtak=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
fix(ivy): ngcc should compile entry-points in the correct order (#25862) The compiler should process all an entry-points dependencies before processing that entry-point. PR Close #25862
2018-08-09 10:59:10 -04:00
dependency-graph@^0.7.2:
version "0.7.2"
resolved "https://registry.yarnpkg.com/dependency-graph/-/dependency-graph-0.7.2.tgz#91db9de6eb72699209d88aea4c1fd5221cac1c49"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-KqtH4/EZdtdfWX0p6MGP9jljvxSY6msy/pRUD4jgNwVpv3v1QmNLlsB3LDSSUg79BRVSn7jI1QPRtArGABovAQ==
fix(ivy): ngcc should compile entry-points in the correct order (#25862) The compiler should process all an entry-points dependencies before processing that entry-point. PR Close #25862
2018-08-09 10:59:10 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
deprecated@^0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/deprecated/-/deprecated-0.0.1.tgz#f9c9af5464afa1e7a971458a8bdef2aa94d5bb19"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+cmvVGSvoeepcUWKi97yqpTVuxk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
destroy@^1.0.4, destroy@~1.0.4:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.4"
resolved "https://registry.yarnpkg.com/destroy/-/destroy-1.0.4.tgz#978857442c44749e4206613e37946205826abd80"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-l4hXRCxEdJ5CBmE+N5RiBYJqvYA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
detect-file@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/detect-file/-/detect-file-1.0.0.tgz#f0d66d03672a825cb1b73bdb3fe62310c8e552b7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8NZtA2cqglyxtzvbP+YjEMjlUrc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
detect-libc@^1.0.2:
version "1.0.3"
resolved "https://registry.yarnpkg.com/detect-libc/-/detect-libc-1.0.3.tgz#fa137c4bd698edf55cd5cd02ac559f91a4c4ba9b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+hN8S9aY7fVc1c0CrFWfkaTEups=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
detective-es6@1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/detective-es6/-/detective-es6-1.1.0.tgz#7c036e1f9469a848a527201edf6ec5a2eef3adab"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-fANuH5RpqEilJyAe327Fou7zras=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
node-source-walk "~1.4.0"
detective@0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/detective/-/detective-0.1.1.tgz#f1e04fe973754c8907ae51edd3e230e380d76fe9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8eBP6XN1TIkHrlHt0+Iw44DXb+k=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
uglify-js "~1.2.5"
detective@^4.3.1:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "4.7.1"
resolved "https://registry.yarnpkg.com/detective/-/detective-4.7.1.tgz#0eca7314338442febb6d65da54c10bb1c82b246e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-H6PmeeUcZloWtdt4DAkFyzFL94arpHr3NOwwmVILFiy+9Qd4JTxxXrzfyGk/lmct2qVGBwTSwSXagqu2BxmWig==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
acorn "^5.2.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
defined "^1.0.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
di@^0.0.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.0.1"
resolved "https://registry.yarnpkg.com/di/-/di-0.0.1.tgz#806649326ceaa7caa3306d75d985ea2748ba913c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-gGZJMmzqp8qjMG112YXqJ0i6kTw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
didyoumean@^1.2.1:
version "1.2.1"
resolved "https://registry.yarnpkg.com/didyoumean/-/didyoumean-1.2.1.tgz#e92edfdada6537d484d73c0172fd1eba0c4976ff"
integrity sha1-6S7f2tplN9SE1zwBcv0eugxJdv8=
build: update ts-api-guardian version (#22402) PR Close #22402
2018-02-27 11:05:09 -05:00
diff@^2.0.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.2.3"
resolved "https://registry.yarnpkg.com/diff/-/diff-2.2.3.tgz#60eafd0d28ee906e4e8ff0a52c1229521033bf99"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-YOr9DSjukG5Oj/ClLBIpUhAzv5k=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
diff@^3.2.0, diff@^3.5.0:
test: display a diff when example_apckage.spec.ts fails to ease debugging (#22933) PR Close #22933
2018-03-22 13:37:43 -04:00
version "3.5.0"
resolved "https://registry.yarnpkg.com/diff/-/diff-3.5.0.tgz#800c0dd1e0a8bfbc95835c202ad220fe317e5a12"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-A46qtFgd+g7pDZinpnwiRJtxbC1hpgf0uzP3iG89scHk0AUC7A1TGxf5OiiOUv/JMZR8GOt8hL900hV0bOy5xA==
test: display a diff when example_apckage.spec.ts fails to ease debugging (#22933) PR Close #22933
2018-03-22 13:37:43 -04:00
test: update side-effects test to be more descriptive (#31005) This test will now list diffs for failed expectations and the full command to update them. Fix #30570 PR Close #31005
2019-06-12 11:11:14 -04:00
diff@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/diff/-/diff-4.0.1.tgz#0c667cb467ebbb5cea7f14f135cc2dba7780a8ff"
integrity sha512-s2+XdvhPCOF01LRQBC8hf4vhbVmI2CGS5aZnxLJlT5FtdhPCDFq80q++zK2KlrVorVDdL5BOGZ/VfLrVtYNF+Q==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
doctrine@^0.7.2:
version "0.7.2"
resolved "https://registry.yarnpkg.com/doctrine/-/doctrine-0.7.2.tgz#7cb860359ba3be90e040b26b729ce4bfa654c523"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-fLhgNZujvpDgQLJrcpzkv6ZUxSM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
esutils "^1.1.6"
isarray "0.0.1"
dom-serialize@^2.2.0:
version "2.2.1"
resolved "https://registry.yarnpkg.com/dom-serialize/-/dom-serialize-2.2.1.tgz#562ae8999f44be5ea3076f5419dcd59eb43ac95b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ViromZ9Evl6jB29UGdzVnrQ6yVs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
custom-event "~1.0.0"
ent "~2.2.0"
extend "^3.0.0"
void-elements "^2.0.0"
domain-browser@^1.1.1:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/domain-browser/-/domain-browser-1.2.0.tgz#3d31f50191a6749dd1375a7f522e823d42e54eda"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-jnjyiM6eRyZl2H+W8Q/zLMA481hzi0eszAaBUzIVnmYVDBbnLxVNnfu1HgEBvCbL+71FrxMl3E6lpKH7Ge3OXA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
feat: upgrade domino to v2.1.2 (#28767) PR Close #28767
2019-02-15 16:18:44 -05:00
domino@2.1.2:
version "2.1.2"
resolved "https://registry.yarnpkg.com/domino/-/domino-2.1.2.tgz#70e8367839ee8ad8bde3aeb4857cf3d93bd98b85"
integrity sha512-nzg76s4Smji9teyLwOnqqUCdFVOho+OQFqUwp+42Wo+SEZ1FGw7uhemv6OKk2qp8YIgnGB3jVt0sJWU96wbPgA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dot-prop@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/dot-prop/-/dot-prop-3.0.0.tgz#1b708af094a49c9a0e7dbcad790aba539dac1177"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-G3CK8JSknJoOfbyteQq6U52sEXc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-obj "^1.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
dot-prop@^4.1.0:
version "4.2.0"
resolved "https://registry.yarnpkg.com/dot-prop/-/dot-prop-4.2.0.tgz#1f19e0c2e1aa0e32797c49799f2837ac6af69c57"
integrity sha512-tUMXrxlExSW6U2EXiiKGSBVdYgtV8qlHL+C10TsW4PURY/ic+eaysnSkwB4kA/mBlCyy/IKDJ+Lc3wbWeaXtuQ==
dependencies:
is-obj "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
duplexer2@0.0.2:
version "0.0.2"
resolved "https://registry.yarnpkg.com/duplexer2/-/duplexer2-0.0.2.tgz#c614dcf67e2fb14995a91711e5a617e8a60a31db"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-xhTc9n4vsUmVqRcR5aYX6KYKMds=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
readable-stream "~1.1.9"
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
duplexer2@~0.1.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.1.4"
resolved "https://registry.yarnpkg.com/duplexer2/-/duplexer2-0.1.4.tgz#8b12dab878c0d69e3e7891051662a32fc6bddcc1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ixLauHjA1p4+eJEFFmKjL8a93ME=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
readable-stream "^2.0.2"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
duplexer3@^0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/duplexer3/-/duplexer3-0.1.4.tgz#ee01dd1cac0ed3cbc7fdbea37dc0a8f1ce002ce2"
integrity sha1-7gHdHKwO08vH/b6jfcCo8c4ALOI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
duplexer@~0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/duplexer/-/duplexer-0.1.1.tgz#ace6ff808c1ce66b57d1ebf97977acb02334cfc1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-rOb/gIwc5mtX0ev5eXessCM0z8E=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
duplexify@^3.4.2, duplexify@^3.6.0:
version "3.6.1"
resolved "https://registry.yarnpkg.com/duplexify/-/duplexify-3.6.1.tgz#b1a7a29c4abfd639585efaecce80d666b1e34125"
integrity sha512-vM58DwdnKmty+FSPzT14K9JXb90H+j5emaR4KYbr2KTIz00WHGbWOe5ghQTx233ZCLZtrGDALzKwcjEtSt35mA==
dependencies:
end-of-stream "^1.0.0"
inherits "^2.0.1"
readable-stream "^2.0.0"
stream-shift "^1.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
duplexify@^3.5.0:
version "3.7.1"
resolved "https://registry.yarnpkg.com/duplexify/-/duplexify-3.7.1.tgz#2a4df5317f6ccfd91f86d6fd25d8d8a103b88309"
integrity sha512-07z8uv2wMyS51kKhD1KsdXJg5WQ6t93RneqRxUHnskXVtlYYkLqM0gqStQZ3pj073g687jPCHrqNfCzawLYh5g==
dependencies:
end-of-stream "^1.0.0"
inherits "^2.0.1"
readable-stream "^2.0.0"
stream-shift "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ecc-jsbn@~0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/ecc-jsbn/-/ecc-jsbn-0.1.1.tgz#0fc73a9ed5f0d53c38193398523ef7e543777505"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-D8c6ntXw1Tw4GTOYUj735UN3dQU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
jsbn "~0.1.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
ecdsa-sig-formatter@1.0.10:
version "1.0.10"
resolved "https://registry.yarnpkg.com/ecdsa-sig-formatter/-/ecdsa-sig-formatter-1.0.10.tgz#1c595000f04a8897dfb85000892a0f4c33af86c3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-HFlQAPBKiJffuFAAiSoPTDOvhsM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
safe-buffer "^5.0.1"
build: update to rules_nodejs 0.38 (#32889) PR Close #32889
2019-09-27 18:49:59 -04:00
ecstatic@^3.0.0:
version "3.3.2"
resolved "https://registry.yarnpkg.com/ecstatic/-/ecstatic-3.3.2.tgz#6d1dd49814d00594682c652adb66076a69d46c48"
integrity sha512-fLf9l1hnwrHI2xn9mEDT7KIi22UDqA2jaCwyCbSUJh9a1V+LEUSL/JO/6TIz/QyuBURWUHrFL5Kg2TtO1bkkog==
dependencies:
he "^1.1.1"
mime "^1.6.0"
minimist "^1.1.0"
url-join "^2.0.5"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ee-first@1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/ee-first/-/ee-first-1.1.1.tgz#590c61156b0ae2f4f0255732a158b266bc56b21d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-WQxhFWsK4vTwJVcyoViyZrxWsh0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
emoji-regex@^7.0.1:
version "7.0.3"
resolved "https://registry.yarnpkg.com/emoji-regex/-/emoji-regex-7.0.3.tgz#933a04052860c85e83c122479c4748a8e4c72156"
integrity sha512-CwBLREIQ7LvYFB0WyRvwhq5N5qPhc6PMjD6bYggFlI5YyDgl+0vxq5VHbMOFqLg7hfWzmu8T5Z1QofhmTIhItA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
emojis-list@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/emojis-list/-/emojis-list-2.1.0.tgz#4daa4d9db00f9819880c79fa457ae5b09a1fd389"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-TapNnbAPmBmIDHn6RXrlsJof04k=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
encodeurl@~1.0.1, encodeurl@~1.0.2:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/encodeurl/-/encodeurl-1.0.2.tgz#ad3ff4c86ec2d029322f5a02c3a9a606c95b3f59"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-rT/0yG7C0CkyL1oCw6mmBslbP1k=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
encoding@^0.1.11:
version "0.1.12"
resolved "https://registry.yarnpkg.com/encoding/-/encoding-0.1.12.tgz#538b66f3ee62cd1ab51ec323829d1f9480c74beb"
integrity sha1-U4tm8+5izRq1HsMjgp0flIDHS+s=
dependencies:
iconv-lite "~0.4.13"
end-of-stream@^1.0.0, end-of-stream@^1.1.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.4.1"
resolved "https://registry.yarnpkg.com/end-of-stream/-/end-of-stream-1.4.1.tgz#ed29634d19baba463b6ce6b80a37213eab71ec43"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-1MkrZNvWTKCaigbn+W15elq2BB/L22nqrSY5DKlo3X6+vclJm8Bb5djXJBmEX6fS3+zCh/F4VBK5Z2KxJt4s2Q==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
once "^1.4.0"
end-of-stream@~0.1.5:
version "0.1.5"
resolved "https://registry.yarnpkg.com/end-of-stream/-/end-of-stream-0.1.5.tgz#8e177206c3c80837d85632e8b9359dfe8b2f6eaf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-jhdyBsPICDfYVjLouTWd/osvbq8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
once "~1.3.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
end-of-stream@~1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/end-of-stream/-/end-of-stream-1.1.0.tgz#e9353258baa9108965efc41cb0ef8ade2f3cfb07"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-6TUyWLqpEIll78QcsO+K3i88+wc=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
once "~1.3.0"
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
engine.io-client@~3.2.0:
version "3.2.1"
resolved "https://registry.yarnpkg.com/engine.io-client/-/engine.io-client-3.2.1.tgz#6f54c0475de487158a1a7c77d10178708b6add36"
integrity sha512-y5AbkytWeM4jQr7m/koQLc5AxpRKC1hEVUb/s1FUAWEJq5AzJJ4NLvzuKPuxtDi5Mq755WuDvZ6Iv2rXj4PTzw==
dependencies:
component-emitter "1.2.1"
component-inherit "0.0.3"
debug "~3.1.0"
engine.io-parser "~2.1.1"
has-cors "1.1.0"
indexof "0.0.1"
parseqs "0.0.5"
parseuri "0.0.5"
ws "~3.3.1"
xmlhttprequest-ssl "~1.5.4"
yeast "0.1.2"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
engine.io-parser@~2.1.0, engine.io-parser@~2.1.1:
version "2.1.2"
resolved "https://registry.yarnpkg.com/engine.io-parser/-/engine.io-parser-2.1.2.tgz#4c0f4cff79aaeecbbdcfdea66a823c6085409196"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-dInLFzr80RijZ1rGpx1+56/uFoH7/7InhH3kZt+Ms6hT8tNx3NGW/WNSA/f8As1WkOfkuyb3tnRyuXGxusclMw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
after "0.8.2"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
arraybuffer.slice "~0.0.7"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
base64-arraybuffer "0.1.5"
blob "0.0.4"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
has-binary2 "~1.0.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
engine.io@~3.2.0:
version "3.2.1"
resolved "https://registry.yarnpkg.com/engine.io/-/engine.io-3.2.1.tgz#b60281c35484a70ee0351ea0ebff83ec8c9522a2"
integrity sha512-+VlKzHzMhaU+GsCIg4AoXF1UdDFjHHwMmMKqMJNDNLlUlejz58FCy4LBqB2YVJskHGYl06BatYWKP2TVdVXE5w==
dependencies:
accepts "~1.3.4"
base64id "1.0.0"
cookie "0.3.1"
debug "~3.1.0"
engine.io-parser "~2.1.0"
ws "~3.3.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
enhanced-resolve@~0.9.0:
version "0.9.1"
resolved "https://registry.yarnpkg.com/enhanced-resolve/-/enhanced-resolve-0.9.1.tgz#4d6e689b3725f86090927ccc86cd9f1635b89e2e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-TW5omzcl+GCQknzMhs2fFjW4ni4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
graceful-fs "^4.1.2"
memory-fs "^0.2.0"
tapable "^0.1.8"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
ent@^2.2.0, ent@~2.2.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/ent/-/ent-2.2.0.tgz#e964219325a21d05f44466a2f686ed6ce5f5dd1d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-6WQhkyWiHQX0RGai9obtbOX13R0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
entities@1.1.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.1.1"
resolved "https://registry.yarnpkg.com/entities/-/entities-1.1.1.tgz#6e5c2d0a5621b5dadaecef80b90edfb5cd7772f0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-blwtClYhtdra7O+AuQ7ftc13cvA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
err-code@^1.0.0:
version "1.1.2"
resolved "https://registry.yarnpkg.com/err-code/-/err-code-1.1.2.tgz#06e0116d3028f6aef4806849eb0ea6a748ae6960"
integrity sha1-BuARbTAo9q70gGhJ6w6mp0iuaWA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
errno@^0.1.3:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.1.7"
resolved "https://registry.yarnpkg.com/errno/-/errno-0.1.7.tgz#4684d71779ad39af177e3f007996f7c67c852618"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-MfrRBDWzIWifgq6tJj60gkAwtLNb6sQPlcFrSOflcP1aFmmruKQ2wRnze/8V6kgyz7H3FF8Npzv78mZ7XLLflg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
prr "~1.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
error-ex@^1.2.0, error-ex@^1.3.1:
version "1.3.2"
resolved "https://registry.yarnpkg.com/error-ex/-/error-ex-1.3.2.tgz#b4ac40648107fdcdcfae242f428bea8a14d4f1bf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-7dFHNmqeFSEt2ZBsCriorKnn3Z2pj+fd9kmI6QoWw4//DL+icEBfc0U7qJCisqrTsKTjw4fNFy2pW9OqStD84g==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-arrayish "^0.2.1"
errorhandler@~1.4.2:
version "1.4.3"
resolved "https://registry.yarnpkg.com/errorhandler/-/errorhandler-1.4.3.tgz#b7b70ed8f359e9db88092f2d20c0f831420ad83f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-t7cO2PNZ6duICS8tIMD4MUIK2D8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
accepts "~1.3.0"
escape-html "~1.0.3"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
es5-ext@^0.10.12, es5-ext@^0.10.14, es5-ext@^0.10.30, es5-ext@^0.10.35, es5-ext@^0.10.9, es5-ext@~0.10.14, es5-ext@~0.10.2:
version "0.10.45"
resolved "https://registry.yarnpkg.com/es5-ext/-/es5-ext-0.10.45.tgz#0bfdf7b473da5919d5adf3bd25ceb754fccc3653"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-FkfM6Vxxfmztilbxxz5UKSD4ICMf5tSpRFtDNtkAhOxZ0EKtX6qwmXNyH/sFyIbX2P/nU5AMiA9jilWsUGJzCQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
es6-iterator "~2.0.3"
es6-symbol "~3.1.1"
next-tick "1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
es5-ext@^0.10.45, es5-ext@^0.10.46, es5-ext@~0.10.46:
version "0.10.47"
resolved "https://registry.yarnpkg.com/es5-ext/-/es5-ext-0.10.47.tgz#d24232e1380daad5449a817be19bde9729024a11"
integrity sha512-/1TItLfj+TTfWoeRcDn/0FbGV6SNo4R+On2GGVucPU/j3BWnXE2Co8h8CTo4Tu34gFJtnmwS9xiScKs4EjZhdw==
dependencies:
es6-iterator "~2.0.3"
es6-symbol "~3.1.1"
next-tick "1"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
es6-error@4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/es6-error/-/es6-error-4.0.0.tgz#f094c7041f662599bb12720da059d6b9c7ff0f40"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8JTHBB9mJZm7EnINoFnWucf/D0A=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
es6-iterator@2, es6-iterator@^2.0.1, es6-iterator@^2.0.3, es6-iterator@~2.0.1, es6-iterator@~2.0.3:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "2.0.3"
resolved "https://registry.yarnpkg.com/es6-iterator/-/es6-iterator-2.0.3.tgz#a7de889141a05a94b0854403b2d0a0fbfa98f3b7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-p96IkUGgWpSwhUQDstCg+/qY87c=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
d "1"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
es5-ext "^0.10.35"
es6-symbol "^3.1.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
es6-module-loader@^0.17.4:
version "0.17.11"
resolved "https://registry.yarnpkg.com/es6-module-loader/-/es6-module-loader-0.17.11.tgz#094f042e3b4d3086bcfd17380affabdfc99f35d7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-CU8ELjtNMIa8/Rc4Cv+r38mfNdc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
when "^3.7.2"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
es6-promise@^4.0.3:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "4.2.5"
resolved "https://registry.yarnpkg.com/es6-promise/-/es6-promise-4.2.5.tgz#da6d0d5692efb461e082c14817fe2427d8f5d054"
integrity sha512-n6wvpdE43VFtJq+lUDYDBFUwV8TZbuGXLV4D6wKafg13ldznKsyEvatubnmUe31zcvelSzOHF+XbaT+Bl9ObDg==
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
es6-promise@~3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/es6-promise/-/es6-promise-3.0.2.tgz#010d5858423a5f118979665f46486a95c6ee2bb6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-AQ1YWEI6XxGJeWZfRkhqlcbuK7Y=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
es6-promisify@5.0.0, es6-promisify@^5.0.0:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
version "5.0.0"
resolved "https://registry.yarnpkg.com/es6-promisify/-/es6-promisify-5.0.0.tgz#5109d62f3e56ea967c4b63505aef08291c8a5203"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-UQnWLz5W6pZ8S2NQWu8IKRyKUgM=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
es6-promise "^4.0.3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
es6-set@^0.1.4:
version "0.1.5"
resolved "https://registry.yarnpkg.com/es6-set/-/es6-set-0.1.5.tgz#d2b3ec5d4d800ced818db538d28974db0a73ccb1"
integrity sha1-0rPsXU2ADO2BjbU40ol02wpzzLE=
dependencies:
d "1"
es5-ext "~0.10.14"
es6-iterator "~2.0.1"
es6-symbol "3.1.1"
event-emitter "~0.3.5"
es6-symbol@3.1.1, es6-symbol@^3.1.1, es6-symbol@~3.1.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "3.1.1"
resolved "https://registry.yarnpkg.com/es6-symbol/-/es6-symbol-3.1.1.tgz#bf00ef4fdab6ba1b46ecb7b629b4c7ed5715cc77"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-vwDvT9q2uhtG7Le2KbTH7VcVzHc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
d "1"
es5-ext "~0.10.14"
es6-weak-map@^2.0.2:
version "2.0.2"
resolved "https://registry.yarnpkg.com/es6-weak-map/-/es6-weak-map-2.0.2.tgz#5e3ab32251ffd1538a1f8e5ffa1357772f92d96f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-XjqzIlH/0VOKH45f+hNXdy+S2W8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
d "1"
es5-ext "^0.10.14"
es6-iterator "^2.0.1"
es6-symbol "^3.1.1"
escape-html@1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/escape-html/-/escape-html-1.0.2.tgz#d77d32fa98e38c2f41ae85e9278e0e0e6ba1022c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-130y+pjjjC9BroXpJ44ODmuhAiw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
escape-html@~1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/escape-html/-/escape-html-1.0.3.tgz#0258eae4d3d0c0974de1c169188ef0051d1d1988"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Aljq5NPQwJdN4cFpGI7wBR0dGYg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
escape-string-regexp@^1.0.2, escape-string-regexp@^1.0.5:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.5"
resolved "https://registry.yarnpkg.com/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz#1b61c0562190a8dff6ae3bb2cf0200ca130b86d4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-G2HAViGQqN/2rjuyzwIAyhMLhtQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
escodegen@^1.9.0:
version "1.11.1"
resolved "https://registry.yarnpkg.com/escodegen/-/escodegen-1.11.1.tgz#c485ff8d6b4cdb89e27f4a856e91f118401ca510"
integrity sha512-JwiqFD9KdGVVpeuRa68yU3zZnBEOcPs0nKW7wZzXky8Z7tffdYUHbe11bPCV5jYlK6DVdKLWLm0f5I/QlL0Kmw==
dependencies:
esprima "^3.1.3"
estraverse "^4.2.0"
esutils "^2.0.2"
optionator "^0.8.1"
optionalDependencies:
source-map "~0.6.1"
espree@^3.5.1:
version "3.5.4"
resolved "https://registry.yarnpkg.com/espree/-/espree-3.5.4.tgz#b0f447187c8a8bed944b815a660bddf5deb5d1a7"
integrity sha512-yAcIQxtmMiB/jL32dzEp2enBeidsB7xWPLNiw3IIkpVds1P+h7qF9YwJq1yUNzp2OKXgAprs4F61ih66UsoD1A==
dependencies:
acorn "^5.5.0"
acorn-jsx "^3.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
esprima-fb@8001.1001.0-dev-harmony-fb:
version "8001.1001.0-dev-harmony-fb"
resolved "https://registry.yarnpkg.com/esprima-fb/-/esprima-fb-8001.1001.0-dev-harmony-fb.tgz#c3190b05341d45643e093af70485ab4988e34d5e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wxkLBTQdRWQ+CTr3BIWrSYjjTV4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
esprima@^2.1.0, esprima@^2.5.0, esprima@^2.7.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.7.3"
resolved "https://registry.yarnpkg.com/esprima/-/esprima-2.7.3.tgz#96e3b70d5779f6ad49cd032673d1c312767ba581"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-luO3DVd59q1JzQMmc9HDEnZ7pYE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
esprima@^3.1.3, esprima@~3.1.0:
version "3.1.3"
resolved "https://registry.yarnpkg.com/esprima/-/esprima-3.1.3.tgz#fdca51cee6133895e3c88d535ce49dbff62a4633"
integrity sha1-/cpRzuYTOJXjyI1TXOSdv/YqRjM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
esprima@~1.2.2:
version "1.2.5"
resolved "https://registry.yarnpkg.com/esprima/-/esprima-1.2.5.tgz#0993502feaf668138325756f30f9a51feeec11e9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-CZNQL+r2aBODJXVvMPmlH+7sEek=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
esquery@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/esquery/-/esquery-1.0.1.tgz#406c51658b1f5991a5f9b62b1dc25b00e3e5c708"
integrity sha512-SmiyZ5zIWH9VM+SRUReLS5Q8a7GxtRdxEBVZpm98rJM7Sb+A9DVCndXfkeFUd3byderg+EbDkfnevfCwynWaNA==
dependencies:
estraverse "^4.0.0"
estemplate@^0.5.1:
version "0.5.1"
resolved "https://registry.yarnpkg.com/estemplate/-/estemplate-0.5.1.tgz#1714a9d46190738ac958bcafd49e029cda56a39e"
integrity sha1-FxSp1GGQc4rJWLyv1J4CnNpWo54=
dependencies:
esprima "^2.7.2"
estraverse "^4.1.1"
estraverse@^4.0.0, estraverse@^4.1.1, estraverse@^4.2.0:
version "4.2.0"
resolved "https://registry.yarnpkg.com/estraverse/-/estraverse-4.2.0.tgz#0dee3fed31fcd469618ce7342099fc1afa0bdb13"
integrity sha1-De4/7TH81GlhjOc0IJn8GvoL2xM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
estree-walker@^0.5.2:
version "0.5.2"
resolved "https://registry.yarnpkg.com/estree-walker/-/estree-walker-0.5.2.tgz#d3850be7529c9580d815600b53126515e146dd39"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-XpCnW/AE10ws/kDAs37cngSkvgIR8aN3G0MS85m7dUpuK2EREo9VJ00uvw6Dg/hXEpfsE1I1TvJOJr+Z+TL+ig==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: update to nodejs rules 0.27 (#29210) PR Close #29210
2019-03-14 22:35:00 -04:00
estree-walker@^0.6.0:
version "0.6.0"
resolved "https://registry.yarnpkg.com/estree-walker/-/estree-walker-0.6.0.tgz#5d865327c44a618dde5699f763891ae31f257dae"
integrity sha512-peq1RfVAVzr3PU/jL31RaOjUKLoZJpObQWJJ+LgfcxDUifyLZ1RjPQZTl0pzj2uJ45b7A7XpyppXvxdEqzo4rw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
esutils@^1.1.6:
version "1.1.6"
resolved "https://registry.yarnpkg.com/esutils/-/esutils-1.1.6.tgz#c01ccaa9ae4b897c6d0c3e210ae52f3c7a844375"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wBzKqa5LiXxtDD4hCuUvPHqEQ3U=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
esutils@^2.0.2:
version "2.0.2"
resolved "https://registry.yarnpkg.com/esutils/-/esutils-2.0.2.tgz#0abf4f1caa5bcb1f7a9d8acc6dea4faaa04bac9b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Cr9PHKpbyx96nYrMbepPqqBLrJs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
etag@~1.7.0:
version "1.7.0"
resolved "https://registry.yarnpkg.com/etag/-/etag-1.7.0.tgz#03d30b5f67dd6e632d2945d30d6652731a34d5d8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-A9MLX2fdbmMtKUXTDWZScxo01dg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
etag@~1.8.1:
version "1.8.1"
resolved "https://registry.yarnpkg.com/etag/-/etag-1.8.1.tgz#41ae2eeb65efa62268aebfea83ac7d79299b0887"
integrity sha1-Qa4u62XvpiJorr/qg6x9eSmbCIc=
event-emitter@^0.3.5, event-emitter@~0.3.5:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.3.5"
resolved "https://registry.yarnpkg.com/event-emitter/-/event-emitter-0.3.5.tgz#df8c69eef1647923c7157b9ce83840610b02cc39"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-34xp7vFkeSPHFXuc6DhAYQsCzDk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
d "1"
es5-ext "~0.10.14"
event-stream@^3.1.5, event-stream@^3.3.2:
version "3.3.4"
build: secure yarn lock files (#31640) See https://yarnpkg.com/blog/2019/07/12/recommended-security-update/ PR Close #31640
2019-07-18 20:34:37 -04:00
resolved "https://registry.npmjs.org/event-stream/-/event-stream-3.3.4.tgz#4ab4c9a0f5a54db9338b4c34d86bfce8f4b35571"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-SrTJoPWlTbkzi0w02Gv86PSzVXE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
duplexer "~0.1.1"
from "~0"
map-stream "~0.1.0"
pause-stream "0.0.11"
split "0.3"
stream-combiner "~0.0.4"
through "~2.3.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
eventemitter3@1.x.x:
version "1.2.0"
resolved "https://registry.yarnpkg.com/eventemitter3/-/eventemitter3-1.2.0.tgz#1c86991d816ad1e504750e73874224ecf3bec508"
integrity sha1-HIaZHYFq0eUEdQ5zh0Ik7PO+xQg=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
eventemitter3@^3.0.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/eventemitter3/-/eventemitter3-3.1.0.tgz#090b4d6cdbd645ed10bf750d4b5407942d7ba163"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-ivIvhpq/Y0uSjcHDcOIccjmYjGLcP09MFGE7ysAwkAvkXfpZlC985pH2/ui64DKazbTW/4kN3yqozUxlXzI6cA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to rules_nodejs 0.38 (#32889) PR Close #32889
2019-09-27 18:49:59 -04:00
eventemitter3@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/eventemitter3/-/eventemitter3-4.0.0.tgz#d65176163887ee59f386d64c82610b696a4a74eb"
integrity sha512-qerSRB0p+UDEssxTtm6EDKcE7W4OaoisfIMl4CngyEhjpYglocpNg6UEqCvemdGhosAsg4sO2dXJOdyBifPGCg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
events@^1.0.0:
version "1.1.1"
resolved "https://registry.yarnpkg.com/events/-/events-1.1.1.tgz#9ebdb7635ad099c70dcc4c2a1f5004288e8bd924"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nr23Y1rQmccNzEwqH1AEKI6L2SQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
execa@^0.7.0:
version "0.7.0"
resolved "https://registry.yarnpkg.com/execa/-/execa-0.7.0.tgz#944becd34cc41ee32a63a9faf27ad5a65fc59777"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-lEvs00zEHuMqY6n68nrVpl/Fl3c=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
cross-spawn "^5.0.1"
get-stream "^3.0.0"
is-stream "^1.1.0"
npm-run-path "^2.0.0"
p-finally "^1.0.0"
signal-exit "^3.0.0"
strip-eof "^1.0.0"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
execa@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/execa/-/execa-1.0.0.tgz#c6236a5bb4df6d6f15e88e7f017798216749ddd8"
integrity sha512-adbxcyWV46qiHyvSp50TKt05tB4tK3HcmF7/nxfAdhnox83seTDbwnaqKO4sXRy7roHAIFqJP/Rw/AuEbX61LA==
dependencies:
cross-spawn "^6.0.0"
get-stream "^4.0.0"
is-stream "^1.1.0"
npm-run-path "^2.0.0"
p-finally "^1.0.0"
signal-exit "^3.0.0"
strip-eof "^1.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
exit-code@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/exit-code/-/exit-code-1.0.2.tgz#ce165811c9f117af6a5f882940b96ae7f9aecc34"
integrity sha1-zhZYEcnxF69qX4gpQLlq5/muzDQ=
exit-hook@^1.0.0:
version "1.1.1"
resolved "https://registry.yarnpkg.com/exit-hook/-/exit-hook-1.1.1.tgz#f05ca233b48c05d54fff07765df8507e95c02ff8"
integrity sha1-8FyiM7SMBdVP/wd2XfhQfpXAL/g=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
exit@^0.1.2:
version "0.1.2"
resolved "https://registry.yarnpkg.com/exit/-/exit-0.1.2.tgz#0632638f8d877cc82107d30a0fff1a17cba1cd0c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-BjJjj42HfMghB9MKD/8aF8uhzQw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
expand-braces@^0.1.1:
version "0.1.2"
resolved "https://registry.yarnpkg.com/expand-braces/-/expand-braces-0.1.2.tgz#488b1d1d2451cb3d3a6b192cfc030f44c5855fea"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-SIsdHSRRyz06axks/AMPRMWFX+o=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
array-slice "^0.2.3"
array-unique "^0.2.1"
braces "^0.1.2"
expand-brackets@^0.1.4:
version "0.1.5"
resolved "https://registry.yarnpkg.com/expand-brackets/-/expand-brackets-0.1.5.tgz#df07284e342a807cd733ac5af72411e581d1177b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-3wcoTjQqgHzXM6xa9yQR5YHRF3s=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-posix-bracket "^0.1.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
expand-brackets@^2.1.4:
version "2.1.4"
resolved "https://registry.yarnpkg.com/expand-brackets/-/expand-brackets-2.1.4.tgz#b77735e315ce30f6b6eff0f83b04151a22449622"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-t3c14xXOMPa27/D4OwQVGiJEliI=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
debug "^2.3.3"
define-property "^0.2.5"
extend-shallow "^2.0.1"
posix-character-classes "^0.1.0"
regex-not "^1.0.0"
snapdragon "^0.8.1"
to-regex "^3.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
expand-range@^0.1.0:
version "0.1.1"
resolved "https://registry.yarnpkg.com/expand-range/-/expand-range-0.1.1.tgz#4cb8eda0993ca56fa4f41fc42f3cbb4ccadff044"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-TLjtoJk8pW+k9B/ELzy7TMrf8EQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-number "^0.1.1"
repeat-string "^0.2.2"
expand-range@^1.8.1:
version "1.8.2"
resolved "https://registry.yarnpkg.com/expand-range/-/expand-range-1.8.2.tgz#a299effd335fe2721ebae8e257ec79644fc85337"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-opnv/TNf4nIeuujiV+x5ZE/IUzc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
fill-range "^2.1.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
expand-tilde@^2.0.0, expand-tilde@^2.0.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.0.2"
resolved "https://registry.yarnpkg.com/expand-tilde/-/expand-tilde-2.0.2.tgz#97e801aa052df02454de46b02bf621642cdc8502"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-l+gBqgUt8CRU3kawK/YhZCzchQI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
homedir-polyfill "^1.0.1"
express-session@~1.11.3:
version "1.11.3"
resolved "https://registry.yarnpkg.com/express-session/-/express-session-1.11.3.tgz#5cc98f3f5ff84ed835f91cbf0aabd0c7107400af"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-XMmPP1/4Ttg1+Ry/CqvQxxB0AK8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
cookie "0.1.3"
cookie-signature "1.0.6"
crc "3.3.0"
debug "~2.2.0"
depd "~1.0.1"
on-headers "~1.0.0"
parseurl "~1.3.0"
uid-safe "~2.0.0"
utils-merge "1.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
express@^4.16.3:
version "4.16.4"
resolved "https://registry.yarnpkg.com/express/-/express-4.16.4.tgz#fddef61926109e24c515ea97fd2f1bdbf62df12e"
integrity sha512-j12Uuyb4FMrd/qQAm6uCHAkPtO8FDTRJZBDd5D2KOL2eLaz1yUNdUB/NOIyq0iU4q4cFarsUCrnFDPBcnksuOg==
dependencies:
accepts "~1.3.5"
array-flatten "1.1.1"
body-parser "1.18.3"
content-disposition "0.5.2"
content-type "~1.0.4"
cookie "0.3.1"
cookie-signature "1.0.6"
debug "2.6.9"
depd "~1.1.2"
encodeurl "~1.0.2"
escape-html "~1.0.3"
etag "~1.8.1"
finalhandler "1.1.1"
fresh "0.5.2"
merge-descriptors "1.0.1"
methods "~1.1.2"
on-finished "~2.3.0"
parseurl "~1.3.2"
path-to-regexp "0.1.7"
proxy-addr "~2.0.4"
qs "6.5.2"
range-parser "~1.2.0"
safe-buffer "5.1.2"
send "0.16.2"
serve-static "1.13.2"
setprototypeof "1.1.0"
statuses "~1.4.0"
type-is "~1.6.16"
utils-merge "1.0.1"
vary "~1.1.2"
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
extend-shallow@^1.1.2:
version "1.1.4"
resolved "https://registry.yarnpkg.com/extend-shallow/-/extend-shallow-1.1.4.tgz#19d6bf94dfc09d76ba711f39b872d21ff4dd9071"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Gda/lN/AnXa6cR85uHLSH/TdkHE=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
kind-of "^1.1.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
extend-shallow@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/extend-shallow/-/extend-shallow-2.0.1.tgz#51af7d614ad9a9f610ea1bafbb989d6b1c56890f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
is-extendable "^0.1.0"
extend-shallow@^3.0.0, extend-shallow@^3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/extend-shallow/-/extend-shallow-3.0.2.tgz#26a71aaf073b39fb2127172746131c2704028db8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Jqcarwc7OfshJxcnRhMcJwQCjbg=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
assign-symbols "^1.0.0"
is-extendable "^1.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
extend@3, extend@^3.0.0, extend@~3.0.0, extend@~3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/extend/-/extend-3.0.1.tgz#a755ea7bc1adfcc5a31ce7e762dbaadc5e636444"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-p1Xqe8Gt/MWjHOfnYtuq3F5jZEQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
extend@^3.0.1, extend@^3.0.2, extend@~3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/extend/-/extend-3.0.2.tgz#f8b1136b4071fbd8eb140aff858b1019ec2915fa"
integrity sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
external-editor@^3.0.3:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "3.0.3"
resolved "https://registry.yarnpkg.com/external-editor/-/external-editor-3.0.3.tgz#5866db29a97826dbe4bf3afd24070ead9ea43a27"
integrity sha512-bn71H9+qWoOQKyZDo25mOMVpSmXROAsTJVVVYzrrtol3d4y+AsKjf4Iwl2Q+IuT0kFSQ1qo166UuIwqYq7mGnA==
dependencies:
chardet "^0.7.0"
iconv-lite "^0.4.24"
tmp "^0.0.33"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
extglob@^0.3.1:
version "0.3.2"
resolved "https://registry.yarnpkg.com/extglob/-/extglob-0.3.2.tgz#2e18ff3d2f49ab2765cec9023f011daa8d8349a1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Lhj/PS9JqydlzskCPwEdqo2DSaE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-extglob "^1.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
extglob@^2.0.4:
version "2.0.4"
resolved "https://registry.yarnpkg.com/extglob/-/extglob-2.0.4.tgz#ad00fe4dc612a9232e8718711dc5cb5ab0285543"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-Nmb6QXkELsuBr24CJSkilo6UHHgbekK5UiZgfE6UHD3Eb27YC6oD+bhcT+tJ6cl8dmsgdQxnWlcry8ksBIBLpw==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
array-unique "^0.3.2"
define-property "^1.0.0"
expand-brackets "^2.1.4"
extend-shallow "^2.0.1"
fragment-cache "^0.2.1"
regex-not "^1.0.0"
snapdragon "^0.8.1"
to-regex "^3.0.1"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
extsprintf@1.3.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.3.0"
resolved "https://registry.yarnpkg.com/extsprintf/-/extsprintf-1.3.0.tgz#96918440e3041a7a414f8c52e3c574eb3c3e1e05"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-lpGEQOMEGnpBT4xS48V06zw+HgU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
extsprintf@^1.2.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/extsprintf/-/extsprintf-1.4.0.tgz#e2689f8f356fad62cca65a3a91c5df5f9551692f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-4mifjzVvrWLMplo6kcXfX5VRaS8=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
eyes@0.1.x:
version "0.1.8"
resolved "https://registry.yarnpkg.com/eyes/-/eyes-0.1.8.tgz#62cf120234c683785d902348a800ef3e0cc20bc0"
integrity sha1-Ys8SAjTGg3hdkCNIqADvPgzCC8A=
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
fancy-log@^1.1.0, fancy-log@^1.3.2:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.3.2"
resolved "https://registry.yarnpkg.com/fancy-log/-/fancy-log-1.3.2.tgz#f41125e3d84f2e7d89a43d06d958c8f78be16be1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-9BEl49hPLn2JpD0G2VjI94vha+E=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
ansi-gray "^0.1.1"
color-support "^1.1.3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
time-stamp "^1.0.0"
fast-deep-equal@^1.0.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.1.0"
resolved "https://registry.yarnpkg.com/fast-deep-equal/-/fast-deep-equal-1.1.0.tgz#c053477817c86b51daa853c81e059b733d023614"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wFNHeBfIa1HaqFPIHgWbcz0CNhQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
feat(bazel): Bazel workspace schematics (#26971) This commit creates a schematics for Bazel workspace. PR Close #26971
2018-09-14 10:03:29 -04:00
fast-deep-equal@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/fast-deep-equal/-/fast-deep-equal-2.0.1.tgz#7b05218ddf9667bf7f370bf7fdb2cb15fdd0aa49"
integrity sha1-ewUhjd+WZ79/Nwv3/bLLFf3Qqkk=
fast-json-stable-stringify@2.0.0, fast-json-stable-stringify@^2.0.0:
feat(elements): add schematics (#23298) PR Close #23298
2018-04-03 17:52:33 -04:00
version "2.0.0"
resolved "https://registry.yarnpkg.com/fast-json-stable-stringify/-/fast-json-stable-stringify-2.0.0.tgz#d5142c0caee6b1189f87d3a76111064f86c8bbf2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-1RQsDK7msRifh9OnYREGT4bIu/I=
feat(elements): add schematics (#23298) PR Close #23298
2018-04-03 17:52:33 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
fast-levenshtein@~2.0.4:
version "2.0.6"
resolved "https://registry.yarnpkg.com/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz#3d8a5c66883a16a30ca8643e851f19baa7797917"
integrity sha1-PYpcZog6FqMMqGQ+hR8Zuqd5eRc=
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
fast-url-parser@^1.1.3:
version "1.1.3"
resolved "https://registry.yarnpkg.com/fast-url-parser/-/fast-url-parser-1.1.3.tgz#f4af3ea9f34d8a271cf58ad2b3759f431f0b318d"
integrity sha1-9K8+qfNNiicc9YrSs3WfQx8LMY0=
dependencies:
punycode "^1.3.2"
faye-websocket@>=0.6.0:
version "0.11.1"
resolved "https://registry.yarnpkg.com/faye-websocket/-/faye-websocket-0.11.1.tgz#f0efe18c4f56e4f40afc7e06c719fd5ee6188f38"
integrity sha1-8O/hjE9W5PQK/H4Gxxn9XuYYjzg=
dependencies:
websocket-driver ">=0.5.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
faye-websocket@~0.10.0:
version "0.10.0"
resolved "https://registry.yarnpkg.com/faye-websocket/-/faye-websocket-0.10.0.tgz#4e492f8d04dfb6f89003507f6edbf2d501e7c6f4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-TkkvjQTftviQA1B/btvy1QHnxvQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
websocket-driver ">=0.5.1"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
figgy-pudding@^3.4.1, figgy-pudding@^3.5.1:
version "3.5.1"
resolved "https://registry.yarnpkg.com/figgy-pudding/-/figgy-pudding-3.5.1.tgz#862470112901c727a0e495a80744bd5baa1d6790"
integrity sha512-vNKxJHTEKNThjfrdJwHc7brvM6eVevuO5nTj6ez8ZQ1qbXTvGthucRF7S4vf2cr71QVnT70V34v0S1DyQsti0w==
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
figures@^1.3.5:
version "1.7.0"
resolved "https://registry.yarnpkg.com/figures/-/figures-1.7.0.tgz#cbe1e3affcf1cd44b80cadfed28dc793a9701d2e"
integrity sha1-y+Hjr/zxzUS4DK3+0o3Hk6lwHS4=
dependencies:
escape-string-regexp "^1.0.5"
object-assign "^4.1.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
figures@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/figures/-/figures-2.0.0.tgz#3ab1a2d2a62c8bfb431a0c94cb797a2fce27c962"
integrity sha1-OrGi0qYsi/tDGgyUy3l6L84nyWI=
dependencies:
escape-string-regexp "^1.0.5"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
filename-regex@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/filename-regex/-/filename-regex-2.0.1.tgz#c1c4b9bee3e09725ddb106b75c1e301fe2f18b26"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wcS5vuPglyXdsQa3XB4wH+LxiyY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
filesize@^3.1.3:
version "3.6.1"
resolved "https://registry.yarnpkg.com/filesize/-/filesize-3.6.1.tgz#090bb3ee01b6f801a8a8be99d31710b3422bb317"
integrity sha512-7KjR1vv6qnicaPMi1iiTcI85CyYwRO/PSFCu6SvqL8jN2Wjt/NIYQTFtFs7fSDCYOstUkEWIQGFUg5YZQfjlcg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
fill-range@^2.1.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "2.2.4"
resolved "https://registry.yarnpkg.com/fill-range/-/fill-range-2.2.4.tgz#eb1e773abb056dcd8df2bfdf6af59b8b3a936565"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-cnrcCbj01+j2gTG921VZPnHbjmdAf8oQV/iGeV2kZxGSyfYjjTyY79ErsK1WJWMpw6DaApEX72binqJE+/d+5Q==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-number "^2.1.0"
isobject "^2.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
randomatic "^3.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
repeat-element "^1.1.2"
repeat-string "^1.5.2"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
fill-range@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/fill-range/-/fill-range-4.0.0.tgz#d544811d428f98eb06a63dc402d2403c328c38f7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-1USBHUKPmOsGpj3EAtJAPDKMOPc=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
extend-shallow "^2.0.1"
is-number "^3.0.0"
repeat-string "^1.6.1"
to-regex-range "^2.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
finalhandler@0.4.0:
version "0.4.0"
resolved "https://registry.yarnpkg.com/finalhandler/-/finalhandler-0.4.0.tgz#965a52d9e8d05d2b857548541fb89b53a2497d9b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-llpS2ejQXSuFdUhUH7ibU6JJfZs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
debug "~2.2.0"
escape-html "1.0.2"
on-finished "~2.3.0"
unpipe "~1.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
finalhandler@1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/finalhandler/-/finalhandler-1.1.0.tgz#ce0b6855b45853e791b2fcc680046d88253dd7f5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-zgtoVbRYU+eRsvzGgARtiCU91/U=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
debug "2.6.9"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
encodeurl "~1.0.1"
escape-html "~1.0.3"
on-finished "~2.3.0"
parseurl "~1.3.2"
statuses "~1.3.1"
unpipe "~1.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
finalhandler@1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/finalhandler/-/finalhandler-1.1.1.tgz#eebf4ed840079c83f4249038c9d703008301b105"
integrity sha512-Y1GUDo39ez4aHAw7MysnUD5JzYX+WaIj8I57kO3aEPT1fFRL4sr7mjei97FgnwhAyyzRYmQZaTHb2+9uZ1dPtg==
dependencies:
debug "2.6.9"
encodeurl "~1.0.2"
escape-html "~1.0.3"
on-finished "~2.3.0"
parseurl "~1.3.2"
statuses "~1.4.0"
unpipe "~1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
find-index@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/find-index/-/find-index-0.1.1.tgz#675d358b2ca3892d795a1ab47232f8b6e2e0dde4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Z101iyyjiS15Whq0cjL4tuLg3eQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
find-up@^1.0.0:
version "1.1.2"
resolved "https://registry.yarnpkg.com/find-up/-/find-up-1.1.2.tgz#6b2e9822b1a2ce0a60ab64d610eccad53cb24d0f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ay6YIrGizgpgq2TWEOzK1TyyTQ8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
path-exists "^2.0.0"
pinkie-promise "^2.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
find-up@^2.0.0, find-up@^2.1.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.1.0"
resolved "https://registry.yarnpkg.com/find-up/-/find-up-2.1.0.tgz#45d1b7e506c717ddd482775a2b77920a3c0c57a7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-RdG35QbHF93UgndaK3eSCjwMV6c=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
locate-path "^2.0.0"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
find-up@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/find-up/-/find-up-3.0.0.tgz#49169f1d7993430646da61ecc5ae355c21c97b73"
integrity sha512-1yD6RmLI1XBfxugvORwlck6f75tYL+iR0jqwsOrOxMZyGYqUuDhJ0l4AXdO1iX/FTs9cBAMEk1gWSEx1kSbylg==
dependencies:
locate-path "^3.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
findup-sync@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/findup-sync/-/findup-sync-2.0.0.tgz#9326b1488c22d1a6088650a86901b2d9a90a2cbc"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-kyaxSIwi0aYIhlCoaQGy2akKLLw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
detect-file "^1.0.0"
is-glob "^3.1.0"
micromatch "^3.0.4"
resolve-dir "^1.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
findup-sync@~0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/findup-sync/-/findup-sync-0.3.0.tgz#37930aa5d816b777c03445e1966cc6790a4c0b16"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-N5MKpdgWt3fANEXhlmzGeQpMCxY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
glob "~5.0.0"
fined@^1.0.1:
version "1.1.0"
resolved "https://registry.yarnpkg.com/fined/-/fined-1.1.0.tgz#b37dc844b76a2f5e7081e884f7c0ae344f153476"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-s33IRLdqL15wgeiE98CuNE8VNHY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
expand-tilde "^2.0.2"
is-plain-object "^2.0.3"
object.defaults "^1.1.0"
object.pick "^1.2.0"
parse-filepath "^1.0.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
firebase-tools@5.1.1:
version "5.1.1"
resolved "https://registry.yarnpkg.com/firebase-tools/-/firebase-tools-5.1.1.tgz#0e693c6197bdc4562fd3040d7bbb7e23b5dc415c"
integrity sha512-xmg5yO5ro1uUTEjHBCMxkA8tcNh+E2y5CAJLL3mXL/3CjrsDId519Yan2kX+x5MWNNwS0Clm4MznaYWJF7E7nQ==
dependencies:
JSONStream "^1.2.1"
archiver "^2.1.1"
cjson "^0.3.1"
cli-color "^1.2.0"
cli-table "^0.3.1"
commander "^2.8.1"
configstore "^1.2.0"
cross-env "^5.1.3"
cross-spawn "^4.0.0"
csv-streamify "^3.0.4"
didyoumean "^1.2.1"
es6-set "^0.1.4"
exit-code "^1.0.2"
filesize "^3.1.3"
firebase "2.x.x"
fs-extra "^0.23.1"
glob "^7.1.2"
google-auto-auth "^0.7.2"
inquirer "^0.12.0"
is "^3.2.1"
jsonschema "^1.0.2"
jsonwebtoken "^8.2.1"
lodash "^4.17.10"
minimatch "^3.0.4"
opn "^5.3.0"
ora "0.2.3"
portfinder "^1.0.13"
progress "^2.0.0"
request "^2.87.0"
semver "^5.0.3"
superstatic "^6.0.1"
tar "^4.3.0"
tmp "0.0.33"
universal-analytics "^0.4.16"
update-notifier "^2.5.0"
user-home "^2.0.0"
uuid "^3.0.0"
winston "^1.0.1"
optionalDependencies:
"@google-cloud/functions-emulator" "^1.0.0-beta.5"
firebase@2.x.x:
version "2.4.2"
resolved "https://registry.yarnpkg.com/firebase/-/firebase-2.4.2.tgz#4e1119ec0396ca561d8a7acbff1630feac6c0a31"
integrity sha1-ThEZ7AOWylYdinrL/xYw/qxsCjE=
dependencies:
faye-websocket ">=0.6.0"
firefox-profile@0.4.0:
version "0.4.0"
resolved "https://registry.yarnpkg.com/firefox-profile/-/firefox-profile-0.4.0.tgz#84468c13c09a65fcf36a837e6daab5956e4baad1"
integrity sha1-hEaME8CaZfzzaoN+baq1lW5LqtE=
dependencies:
adm-zip "~0.4.x"
archiver "~1.0.0"
async "~1.5.2"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
fs-extra "~0.30.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ini "~1.3.3"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
jetpack-id "1.0.0"
lazystream "~1.0.0"
lodash "~4.12.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
minimist "^1.1.1"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
node-uuid "~1.4.7"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
xml2js "~0.4.4"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
firefox-profile@1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/firefox-profile/-/firefox-profile-1.0.3.tgz#5a656116885a86558384fa11d102fb11eff45cf1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-WmVhFohahlWDhPoR0QL7Ee/0XPE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
adm-zip "~0.4.x"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
archiver "~1.3.0"
async "~2.4.1"
fs-extra "~2.1.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ini "~1.3.3"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
jetpack-id "1.0.0"
lazystream "~1.0.0"
lodash "~4.17.2"
minimist "^1.1.1"
uuid "^3.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
xml2js "~0.4.4"
first-chunk-stream@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/first-chunk-stream/-/first-chunk-stream-1.0.0.tgz#59bfb50cd905f60d7c394cd3d9acaab4e6ad934e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Wb+1DNkF9g18OUzT2ayqtOatk04=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
first-chunk-stream@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/first-chunk-stream/-/first-chunk-stream-2.0.0.tgz#1bdecdb8e083c0664b91945581577a43a9f31d70"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-G97NuOCDwGZLkZRVgVd6Q6nzHXA=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
readable-stream "^2.0.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
flagged-respawn@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/flagged-respawn/-/flagged-respawn-1.0.0.tgz#4e79ae9b2eb38bf86b3bb56bf3e0a56aa5fcabd7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Tnmumy6zi/hrO7Vr8+ClaqX8q9c=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
flat-arguments@^1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/flat-arguments/-/flat-arguments-1.0.2.tgz#9baa780adf0501f282d726c9c6a038dba44ea76f"
integrity sha1-m6p4Ct8FAfKC1ybJxqA426ROp28=
dependencies:
array-flatten "^1.0.0"
as-array "^1.0.0"
lodash.isarguments "^3.0.0"
lodash.isobject "^3.0.0"
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
flatted@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/flatted/-/flatted-2.0.0.tgz#55122b6536ea496b4b44893ee2608141d10d9916"
integrity sha512-R+H8IZclI8AAkSBRQJLVOsxwAoHd6WC40b4QTNWIjzAa6BXOBfQcM587MXDTVPeYaopFNWHUFLx7eNmHDSxMWg==
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
flush-write-stream@^1.0.0:
version "1.0.3"
resolved "https://registry.yarnpkg.com/flush-write-stream/-/flush-write-stream-1.0.3.tgz#c5d586ef38af6097650b49bc41b55fabb19f35bd"
integrity sha512-calZMC10u0FMUqoiunI2AiGIIUtUIvifNwkHhNupZH4cbNnW1Itkoh/Nf5HFYmDrwWPjrUxpkZT0KhuCq0jmGw==
dependencies:
inherits "^2.0.1"
readable-stream "^2.0.4"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
follow-redirects@^1.0.0:
version "1.5.1"
resolved "https://registry.yarnpkg.com/follow-redirects/-/follow-redirects-1.5.1.tgz#67a8f14f5a1f67f962c2c46469c79eaec0a90291"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-v9GI1hpaqq1ZZR6pBD1+kI7O24PhDvNGNodjS3MdcEqyrahCp8zbtpv+2B/krUnSmUH80lbAS7MrdeK5IylgKg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
debug "^3.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
follow-redirects@^1.3.0:
version "1.6.1"
resolved "https://registry.yarnpkg.com/follow-redirects/-/follow-redirects-1.6.1.tgz#514973c44b5757368bad8bddfe52f81f015c94cb"
integrity sha512-t2JCjbzxQpWvbhts3l6SH1DKzSrx8a+SsaVf4h6bG4kOXUuPYS/kg2Lr4gQSb7eemaHqJkOThF1BGyjlUkO1GQ==
dependencies:
debug "=3.1.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
for-in@^1.0.1, for-in@^1.0.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/for-in/-/for-in-1.0.2.tgz#81068d295a8142ec0ac726c6e2200c30fb6d5e80"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-gQaNKVqBQuwKxybG4iAMMPttXoA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
for-own@^0.1.4:
version "0.1.5"
resolved "https://registry.yarnpkg.com/for-own/-/for-own-0.1.5.tgz#5265c681a4f294dabbf17c9509b6763aa84510ce"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-UmXGgaTylNq78XyVCbZ2OqhFEM4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
for-in "^1.0.1"
for-own@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/for-own/-/for-own-1.0.0.tgz#c63332f415cedc4b04dbfe70cf836494c53cb44b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-xjMy9BXO3EsE2/5wz4NklMU8tEs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
for-in "^1.0.1"
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
foreground-child@^1.5.6:
version "1.5.6"
resolved "https://registry.yarnpkg.com/foreground-child/-/foreground-child-1.5.6.tgz#4fd71ad2dfde96789b980a5c0a295937cb2f5ce9"
integrity sha1-T9ca0t/elnibmApcCilZN8svXOk=
dependencies:
cross-spawn "^4"
signal-exit "^3.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
forever-agent@~0.6.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.6.1"
resolved "https://registry.yarnpkg.com/forever-agent/-/forever-agent-0.6.1.tgz#fbc71f0c41adeb37f96c577ad1ed42d8fdacca91"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+8cfDEGt6zf5bFd60e1C2P2sypE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
form-data@~1.0.0-rc4:
version "1.0.1"
resolved "https://registry.yarnpkg.com/form-data/-/form-data-1.0.1.tgz#ae315db9a4907fa065502304a66d7733475ee37c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-rjFduaSQf6BlUCMEpm13M0de43w=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
async "^2.0.1"
combined-stream "^1.0.5"
mime-types "^2.1.11"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
form-data@~2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/form-data/-/form-data-2.0.0.tgz#6f0aebadcc5da16c13e1ecc11137d85f9b883b25"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-bwrrrcxdoWwT4ezBETfYX5uIOyU=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
asynckit "^0.4.0"
combined-stream "^1.0.5"
mime-types "^2.1.11"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
form-data@~2.3.1:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "2.3.2"
resolved "https://registry.yarnpkg.com/form-data/-/form-data-2.3.2.tgz#4970498be604c20c005d4f5c23aecd21d6b49099"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-SXBJi+YEwgwAXU9cI67NIda0kJk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
asynckit "^0.4.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
combined-stream "1.0.6"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
mime-types "^2.1.12"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
form-data@~2.3.2:
version "2.3.3"
resolved "https://registry.yarnpkg.com/form-data/-/form-data-2.3.3.tgz#dcce52c05f644f298c6a7ab936bd724ceffbf3a6"
integrity sha512-1lLKB2Mu3aGP1Q/2eCOx0fNbRMe7XdwktwOruhfqqd0rIJWwN4Dh+E3hrPSlDCXnSR7UtZ1N38rVXm+6+MEhJQ==
dependencies:
asynckit "^0.4.0"
combined-stream "^1.0.6"
mime-types "^2.1.12"
forwarded@~0.1.2:
version "0.1.2"
resolved "https://registry.yarnpkg.com/forwarded/-/forwarded-0.1.2.tgz#98c23dab1175657b8c0573e8ceccd91b0ff18c84"
integrity sha1-mMI9qxF1ZXuMBXPozszZGw/xjIQ=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
fragment-cache@^0.2.1:
version "0.2.1"
resolved "https://registry.yarnpkg.com/fragment-cache/-/fragment-cache-0.2.1.tgz#4290fad27f13e89be7f33799c6bc5a0abfff0d19"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-QpD60n8T6Jvn8zeZxrxaCr//DRk=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
map-cache "^0.2.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
fresh@0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/fresh/-/fresh-0.3.0.tgz#651f838e22424e7566de161d8358caa199f83d4f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ZR+DjiJCTnVm3hYdg1jKoZn4PU8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
fresh@0.5.2:
version "0.5.2"
resolved "https://registry.yarnpkg.com/fresh/-/fresh-0.5.2.tgz#3d8cadd90d976569fa835ab1f8e4b23a105605a7"
integrity sha1-PYyt2Q2XZWn6g1qx+OSyOhBWBac=
from2@^2.1.0, from2@^2.1.1:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "2.3.0"
resolved "https://registry.yarnpkg.com/from2/-/from2-2.3.0.tgz#8bfb5502bde4a4d36cfdeea007fcca21d7e382af"
integrity sha1-i/tVAr3kpNNs/e6gB/zKIdfjgq8=
dependencies:
inherits "^2.0.1"
readable-stream "^2.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
from@~0:
version "0.1.7"
resolved "https://registry.yarnpkg.com/from/-/from-0.1.7.tgz#83c60afc58b9c56997007ed1a768b3ab303a44fe"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-g8YK/Fi5xWmXAH7Rp2izqzA6RP4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
fs-access@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/fs-access/-/fs-access-1.0.1.tgz#d6a87f262271cefebec30c553407fb995da8777a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-1qh/JiJxzv6+wwxVNAf7mV2od3o=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
null-check "^1.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
fs-constants@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/fs-constants/-/fs-constants-1.0.0.tgz#6be0de9be998ce16af8afc24497b9ee9b7ccd9ad"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-y6OAwoSIf7FyjMIv94u+b5rdheZEjzR63GTyZJm5qh4Bi+2YgwLCcI/fPFZkL5PSixOt6ZNKm+w+Hfp/Bciwow==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
fs-extra@0.30.0, fs-extra@^0.30.0, fs-extra@~0.30.0:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
version "0.30.0"
resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-0.30.0.tgz#f233ffcc08d4da7d432daa449776989db1df93f0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8jP/zAjU2n1DLapEl3aYnbHfk/A=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
graceful-fs "^4.1.2"
jsonfile "^2.1.0"
klaw "^1.0.0"
path-is-absolute "^1.0.0"
rimraf "^2.2.8"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
fs-extra@4.0.2:
version "4.0.2"
resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-4.0.2.tgz#f91704c53d1b461f893452b0c307d9997647ab6b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+RcExT0bRh+JNFKwwwfZmXZHq2s=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
graceful-fs "^4.1.2"
jsonfile "^4.0.0"
universalify "^0.1.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
fs-extra@^0.23.1:
version "0.23.1"
resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-0.23.1.tgz#6611dba6adf2ab8dc9c69fab37cddf8818157e3d"
integrity sha1-ZhHbpq3yq43Jxp+rN83fiBgVfj0=
dependencies:
graceful-fs "^4.1.2"
jsonfile "^2.1.0"
path-is-absolute "^1.0.0"
rimraf "^2.2.8"
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
fs-extra@^7.0.1, fs-extra@~7.0.1:
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
version "7.0.1"
resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-7.0.1.tgz#4f189c44aa123b895f722804f55ea23eadc348e9"
integrity sha512-YJDaCJZEnBmcbw13fvdAM9AwNOJwOzrE4pqMqBq5nFiEqXUqHwlK4B+3pUw6JNvfSPtX05xFHtYy/1ni01eGCw==
dependencies:
graceful-fs "^4.1.2"
jsonfile "^4.0.0"
universalify "^0.1.0"
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
fs-extra@~2.1.2:
version "2.1.2"
resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-2.1.2.tgz#046c70163cef9aad46b0e4a7fa467fb22d71de35"
integrity sha1-BGxwFjzvmq1GsOSn+kZ/si1x3jU=
dependencies:
graceful-fs "^4.1.2"
jsonfile "^2.1.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
fs-minipass@^1.2.5:
version "1.2.5"
resolved "https://registry.yarnpkg.com/fs-minipass/-/fs-minipass-1.2.5.tgz#06c277218454ec288df77ada54a03b8702aacb9d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-JhBl0skXjUPCFH7x6x61gQxrKyXsxB5gcgePLZCwfyCGGsTISMoIeObbrvVeP6Xmyaudw4TT43qV2Gz+iyd2oQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
minipass "^2.2.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
fs-promise@0.3.1:
version "0.3.1"
resolved "https://registry.yarnpkg.com/fs-promise/-/fs-promise-0.3.1.tgz#bf34050368f24d6dc9dfc6688ab5cead8f86842a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-vzQFA2jyTW3J38ZoirXOrY+GhCo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
any-promise "~0.1.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
fs-write-stream-atomic@^1.0.8:
version "1.0.10"
resolved "https://registry.yarnpkg.com/fs-write-stream-atomic/-/fs-write-stream-atomic-1.0.10.tgz#b47df53493ef911df75731e70a9ded0189db40c9"
integrity sha1-tH31NJPvkR33VzHnCp3tAYnbQMk=
dependencies:
graceful-fs "^4.1.2"
iferr "^0.1.5"
imurmurhash "^0.1.4"
readable-stream "1 || 2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
fs.realpath@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/fs.realpath/-/fs.realpath-1.0.0.tgz#1504ad2523158caa40db4a2787cb01411994ea4f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-FQStJSMVjKpA20onh8sBQRmU6k8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: to fsevents@2.0.1 (#27469) the old version was failing to compile on MacOS Mojave 10.14.1. PR Close #27469
2018-12-05 13:10:58 -05:00
fsevents@2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/fsevents/-/fsevents-2.0.1.tgz#cdc8dc0145fa4198f4500ec09df35e79e5e52cf7"
integrity sha512-p+CXqK/iLvDESUWdn3NA3JVO9HxdfI+iXx8xR3DqWgKZvQNiEVpAyUQo0lmwz8rqksb4xaGerG291xuwwhX2kA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Upgrade CLI dependencies for schematics test (#28872) This commit makes the integration test for bazel-schematics more robust by removing package.json.replace. Instead of replacing the file, the test script now just overrides Angular packages with the local ones. This commit also fixes running the test locally by providing default argument for CI_CHROMEDRIVER_VERSION_ARG. PR Close #28872
2019-02-20 12:58:42 -05:00
fsevents@^1.0.0:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.2.4"
resolved "https://registry.yarnpkg.com/fsevents/-/fsevents-1.2.4.tgz#f41dcb1af2582af3692da36fc55cbd8e1041c426"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-z8H8/diyk76B7q5wg+Ud0+CqzcAF3mBBI/bA5ne5zrRUUIvNkJY//D3BqyH571KuAC4Nr7Rw7CjWX4r0y9DvNg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
nan "^2.9.2"
node-pre-gyp "^0.10.0"
test(bazel): Upgrade CLI dependencies for schematics test (#28872) This commit makes the integration test for bazel-schematics more robust by removing package.json.replace. Instead of replacing the file, the test script now just overrides Angular packages with the local ones. This commit also fixes running the test locally by providing default argument for CI_CHROMEDRIVER_VERSION_ARG. PR Close #28872
2019-02-20 12:58:42 -05:00
fsevents@^1.2.2, fsevents@^1.2.7:
build(compiler-cli): upgrade chokidar to latest version (#28797) Fixes #28771 PR Close #28797
2019-02-18 08:11:03 -05:00
version "1.2.7"
resolved "https://registry.yarnpkg.com/fsevents/-/fsevents-1.2.7.tgz#4851b664a3783e52003b3c66eb0eee1074933aa4"
integrity sha512-Pxm6sI2MeBD7RdD12RYsqaP0nMiwx8eZBXCa6z2L+mRHm2DYrOYwihmhjpkdjUHwQhslWQjRpEgNq4XvBmaAuw==
dependencies:
nan "^2.9.2"
node-pre-gyp "^0.10.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"fstream@>= 0.1.30 < 1":
version "0.1.31"
resolved "https://registry.yarnpkg.com/fstream/-/fstream-0.1.31.tgz#7337f058fbbbbefa8c9f561a28cab0849202c988"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-czfwWPu7vvqMn1YaKMqwhJICyYg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
graceful-fs "~3.0.2"
inherits "~2.0.0"
mkdirp "0.5"
rimraf "2"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
fx-runner@1.0.5:
version "1.0.5"
resolved "https://registry.yarnpkg.com/fx-runner/-/fx-runner-1.0.5.tgz#713519aca7598a8319e03fa1110b89b97ef1063f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-cTUZrKdZioMZ4D+hEQuJuX7xBj8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
commander "2.9.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
fs-promise "0.3.1"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
lodash "3.10.1"
shell-quote "1.6.1"
spawn-sync "1.0.15"
when "3.7.7"
which "1.2.4"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
winreg "0.0.12"
gauge@~2.7.3:
version "2.7.4"
resolved "https://registry.yarnpkg.com/gauge/-/gauge-2.7.4.tgz#2c03405c7538c39d7eb37b317022e325fb018bf7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-LANAXHU4w51+s3sxcCLjJfsBi/c=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
aproba "^1.0.3"
console-control-strings "^1.0.0"
has-unicode "^2.0.0"
object-assign "^4.1.0"
signal-exit "^3.0.0"
string-width "^1.0.1"
strip-ansi "^3.0.1"
wide-align "^1.1.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
gaxios@^1.0.4:
version "1.4.0"
resolved "https://registry.yarnpkg.com/gaxios/-/gaxios-1.4.0.tgz#4f5c2def1abcaa64b5fe45dbf188fb72b246bc7d"
integrity sha512-qW0q08OcvFwaSmwUiELnif+q5NvAAoQfUN6iq8lx/HnmgMcJ9U+jiB+c+5C1muSBGsQ3D3PiLFpJ9jjO8BRCDg==
dependencies:
extend "^3.0.2"
https-proxy-agent "^2.2.1"
node-fetch "^2.2.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
gaze@^0.5.1:
version "0.5.2"
resolved "https://registry.yarnpkg.com/gaze/-/gaze-0.5.2.tgz#40b709537d24d1d45767db5a908689dfe69ac44f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-QLcJU30k0dRXZ9takIaJ3+aaxE8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
globule "~0.1.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
gcp-metadata@^0.3.0:
version "0.3.1"
resolved "https://registry.yarnpkg.com/gcp-metadata/-/gcp-metadata-0.3.1.tgz#313814456e7c3d0eeb8f8b084b33579e886f829a"
integrity sha512-5kJPX/RXuqoLmHiOOgkSDk/LI0QaXpEvZ3pvQP4ifjGGDKZKVSOjL/GcDjXA5kLxppFCOjmmsu0Uoop9d1upaQ==
dependencies:
extend "^3.0.0"
retry-request "^3.0.0"
gcp-metadata@^0.6.1, gcp-metadata@^0.6.3:
version "0.6.3"
resolved "https://registry.yarnpkg.com/gcp-metadata/-/gcp-metadata-0.6.3.tgz#4550c08859c528b370459bd77a7187ea0bdbc4ab"
integrity sha512-MSmczZctbz91AxCvqp9GHBoZOSbJKAICV7Ow/AIWSJZRrRchUd5NL1b2P4OfP+4m490BEUPhhARfpHdqCxuCvg==
dependencies:
axios "^0.18.0"
extend "^3.0.1"
retry-axios "0.3.2"
gcs-resumable-upload@^0.10.2:
version "0.10.2"
resolved "https://registry.yarnpkg.com/gcs-resumable-upload/-/gcs-resumable-upload-0.10.2.tgz#7f29b3ee23dcec4170367c0711418249c660545f"
integrity sha1-fymz7iPc7EFwNnwHEUGCScZgVF8=
dependencies:
configstore "^3.1.2"
google-auto-auth "^0.10.0"
pumpify "^1.4.0"
request "^2.85.0"
stream-events "^1.0.3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
generate-function@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/generate-function/-/generate-function-2.0.0.tgz#6858fe7c0969b7d4e9093337647ac79f60dfbe74"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-aFj+fAlpt9TpCTM3ZHrHn2DfvnQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
generate-object-property@^1.1.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/generate-object-property/-/generate-object-property-1.2.0.tgz#9c0e1c40308ce804f4783618b937fa88f99d50d0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nA4cQDCM6AT0eDYYuTf6iPmdUNA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-property "^1.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
genfun@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/genfun/-/genfun-5.0.0.tgz#9dd9710a06900a5c4a5bf57aca5da4e52fe76537"
integrity sha512-KGDOARWVga7+rnB3z9Sd2Letx515owfk0hSxHGuqjANb1M+x2bGZGqHLiozPsYMdM2OubeMni/Hpwmjq6qIUhA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
get-caller-file@^1.0.1:
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
version "1.0.3"
resolved "https://registry.yarnpkg.com/get-caller-file/-/get-caller-file-1.0.3.tgz#f978fa4c90d1dfe7ff2d6beda2a515e713bdcf4a"
integrity sha512-3t6rVToeoZfYSGd8YoLFR2DJkiQrIiUrGcjvFX2mDw3bn6k2OtwHN0TNCLbBO+w8qTvimhDkv+LSscbJY1vE6w==
get-caller-file@^2.0.1:
version "2.0.5"
resolved "https://registry.yarnpkg.com/get-caller-file/-/get-caller-file-2.0.5.tgz#4f94412a82db32f36e3b0b9741f8a97feb031f7e"
integrity sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
build(bazel): remove @ts-api-guardian_deps yarn_install (#29799) PR Close #29799
2019-04-09 21:08:13 -04:00
get-func-name@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/get-func-name/-/get-func-name-2.0.0.tgz#ead774abee72e20409433a066366023dd6887a41"
integrity sha1-6td0q+5y4gQJQzoGY2YCPdaIekE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
get-pkg-repo@^1.0.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/get-pkg-repo/-/get-pkg-repo-1.4.0.tgz#c73b489c06d80cc5536c2c853f9e05232056972d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-xztInAbYDMVTbCyFP54FIyBWly0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
hosted-git-info "^2.1.4"
meow "^3.3.0"
normalize-package-data "^2.3.0"
parse-github-repo-url "^1.3.0"
through2 "^2.0.0"
get-stdin@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/get-stdin/-/get-stdin-4.0.1.tgz#b968c6b0a04384324902e8bf1a5df32579a450fe"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-uWjGsKBDhDJJAui/Gl3zJXmkUP4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
get-stream@3.0.0, get-stream@^3.0.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "3.0.0"
resolved "https://registry.yarnpkg.com/get-stream/-/get-stream-3.0.0.tgz#8e943d1358dc37555054ecbe2edb05aa174ede14"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-jpQ9E1jcN1VQVOy+LtsFqhdO3hQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
get-stream@^4.0.0, get-stream@^4.1.0:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "4.1.0"
resolved "https://registry.yarnpkg.com/get-stream/-/get-stream-4.1.0.tgz#c1b255575f3dc21d59bfc79cd3d2b46b1c3a54b5"
integrity sha512-GMat4EJ5161kIy2HevLlr4luNjBgvmj413KaQA7jt4V8B4RDsfpHk7WQ9GVqfYyyx8OS/L66Kox+rJRNklLK7w==
dependencies:
pump "^3.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
get-value@^2.0.3, get-value@^2.0.6:
version "2.0.6"
resolved "https://registry.yarnpkg.com/get-value/-/get-value-2.0.6.tgz#dc15ca1c672387ca76bd37ac0a395ba2042a2c28"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-3BXKHGcjh8p2vTesCjlbogQqLCg=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
getpass@^0.1.1:
version "0.1.7"
resolved "https://registry.yarnpkg.com/getpass/-/getpass-0.1.7.tgz#5eff8e3e684d569ae4cb2b1282604e8ba62149fa"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Xv+OPmhNVprkyysSgmBOi6YhSfo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
assert-plus "^1.0.0"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
git-raw-commits@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/git-raw-commits/-/git-raw-commits-2.0.0.tgz#d92addf74440c14bcc5c83ecce3fb7f8a79118b5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-w4jFEJFgKXMQJ0H0ikBk2S+4KP2VEjhCvLCNqbNRQC8BgGWgLKNCO7a9K9LI+TVT7Gfoloje502sEnctibffgg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
dargs "^4.0.1"
lodash.template "^4.0.2"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
meow "^4.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
split2 "^2.0.0"
through2 "^2.0.0"
git-remote-origin-url@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/git-remote-origin-url/-/git-remote-origin-url-2.0.0.tgz#5282659dae2107145a11126112ad3216ec5fa65f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-UoJlna4hBxRaERJhEq0yFuxfpl8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
gitconfiglocal "^1.0.0"
pify "^2.3.0"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
git-semver-tags@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/git-semver-tags/-/git-semver-tags-2.0.0.tgz#c218fd895bdf8e8e02f6bde555b2c3893ac73cd7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-lSgFc3zQTul31nFje2Q8XdNcTOI6B4I3mJRPCgFzHQQLfxfqdWTYzdtCaynkK5Xmb2wQlSJoKolhXJ1VhKROnQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
meow "^4.0.0"
semver "^5.5.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
gitconfiglocal@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/gitconfiglocal/-/gitconfiglocal-1.0.0.tgz#41d045f3851a5ea88f03f24ca1c6178114464b9b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-QdBF84UaXqiPA/JMocYXgRRGS5s=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
ini "^1.3.2"
glob-base@^0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/glob-base/-/glob-base-0.3.0.tgz#dbb164f6221b1c0b1ccf82aea328b497df0ea3c4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-27Fk9iIbHAscz4Kuoyi0l98Oo8Q=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
glob-parent "^2.0.0"
is-glob "^2.0.0"
glob-parent@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/glob-parent/-/glob-parent-2.0.0.tgz#81383d72db054fcccf5336daa902f182f6edbb28"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-gTg9ctsFT8zPUzbaqQLxgvbtuyg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-glob "^2.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
glob-parent@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/glob-parent/-/glob-parent-3.1.0.tgz#9e6af6299d8d3bd2bd40430832bd113df906c5ae"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nmr2KZ2NO9K9QEMIMr0RPfkGxa4=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
is-glob "^3.1.0"
path-dirname "^1.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
glob-slash@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/glob-slash/-/glob-slash-1.0.0.tgz#fe52efa433233f74a2fe64c7abb9bc848202ab95"
integrity sha1-/lLvpDMjP3Si/mTHq7m8hIICq5U=
glob-slasher@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/glob-slasher/-/glob-slasher-1.0.1.tgz#747a0e5bb222642ee10d3e05443e109493cb0f8e"
integrity sha1-dHoOW7IiZC7hDT4FRD4QlJPLD44=
dependencies:
glob-slash "^1.0.0"
lodash.isobject "^2.4.1"
toxic "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
glob-stream@^3.1.5:
version "3.1.18"
resolved "https://registry.yarnpkg.com/glob-stream/-/glob-stream-3.1.18.tgz#9170a5f12b790306fdfe598f313f8f7954fd143b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-kXCl8St5Awb9/lmPMT+PeVT9FDs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
glob "^4.3.1"
glob2base "^0.0.12"
minimatch "^2.0.1"
ordered-read-streams "^0.1.0"
through2 "^0.6.1"
unique-stream "^1.0.0"
glob-watcher@^0.0.6:
version "0.0.6"
resolved "https://registry.yarnpkg.com/glob-watcher/-/glob-watcher-0.0.6.tgz#b95b4a8df74b39c83298b0c05c978b4d9a3b710b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-uVtKjfdLOcgymLDAXJeLTZo7cQs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
gaze "^0.5.1"
glob2base@^0.0.12:
version "0.0.12"
resolved "https://registry.yarnpkg.com/glob2base/-/glob2base-0.0.12.tgz#9d419b3e28f12e83a362164a277055922c9c0d56"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nUGbPijxLoOjYhZKJ3BVkiycDVY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
find-index "^0.1.1"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
glob@7.1.2, glob@^7.0.0, glob@^7.0.3, glob@^7.0.6, glob@^7.1.1:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
version "7.1.2"
resolved "https://registry.yarnpkg.com/glob/-/glob-7.1.2.tgz#c19c9df9a028702d678612384a6552404c636d15"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-MJTUg1kjuLeQCJ+ccE4Vpa6kKVXkPYJ2mOCQyUuKLcLQsdrMCpBPUi8qVE6+YuaJkozeA9NusTAw3hLr8Xe5EQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
fs.realpath "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
inflight "^1.0.4"
inherits "2"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
minimatch "^3.0.4"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
once "^1.3.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
path-is-absolute "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
glob@^4.3.1:
version "4.5.3"
resolved "https://registry.yarnpkg.com/glob/-/glob-4.5.3.tgz#c6cb73d3226c1efef04de3c56d012f03377ee15f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-xstz0yJsHv7wTePFbQEvAzd+4V8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
inflight "^1.0.4"
inherits "2"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
minimatch "^2.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
once "^1.3.0"
build: update to rules_typescript 0.20.3 and rules_nodejs 0.15.1 (#26488) PR Close #26488
2018-10-16 18:27:47 -04:00
glob@^5.0.15, glob@~5.0.0:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
version "5.0.15"
resolved "https://registry.yarnpkg.com/glob/-/glob-5.0.15.tgz#1bc936b9e02f4a603fcc222ecf7633d30b8b93b1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-G8k2ueAvSmA/zCIuz3Yz0wuLk7E=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
inflight "^1.0.4"
inherits "2"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
minimatch "2 || 3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
once "^1.3.0"
path-is-absolute "^1.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
glob@^7.0.5, glob@^7.1.2, glob@^7.1.3:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "7.1.3"
resolved "https://registry.yarnpkg.com/glob/-/glob-7.1.3.tgz#3960832d3f1574108342dafd3a67b332c0969df1"
integrity sha512-vcfuiIxogLV4DlGBHIUOwI0IbrJ8HWPc4MU7HzviGeNho/UJDfi6B5p3sHeWIQ0KGIU0Jpxi5ZHxemQfLkkAwQ==
dependencies:
fs.realpath "^1.0.0"
inflight "^1.0.4"
inherits "2"
minimatch "^3.0.4"
once "^1.3.0"
path-is-absolute "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
glob@~3.1.21:
version "3.1.21"
resolved "https://registry.yarnpkg.com/glob/-/glob-3.1.21.tgz#d29e0a055dea5138f4d07ed40e8982e83c2066cd"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-0p4KBV3qUTj00H7UDomC6DwgZs0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
graceful-fs "~1.2.0"
inherits "1"
minimatch "~0.2.11"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
global-dirs@^0.1.0:
version "0.1.1"
resolved "https://registry.yarnpkg.com/global-dirs/-/global-dirs-0.1.1.tgz#b319c0dd4607f353f3be9cca4c72fc148c49f445"
integrity sha1-sxnA3UYH81PzvpzKTHL8FIxJ9EU=
dependencies:
ini "^1.3.4"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
global-modules@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/global-modules/-/global-modules-1.0.0.tgz#6d770f0eb523ac78164d72b5e71a8877265cc3ea"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-sKzpEkf11GpOFuw0Zzjzmt4B4UZwjOcG757PPvrfhxcLFbq0wpsgpOqxpxtxFiCG4DtG93M6XRVbF2oGdev7bg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
global-prefix "^1.0.1"
is-windows "^1.0.1"
resolve-dir "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
global-prefix@^1.0.1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/global-prefix/-/global-prefix-1.0.2.tgz#dbf743c6c14992593c655568cb66ed32c0122ebe"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-2/dDxsFJklk8ZVVoy2btMsASLr4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
expand-tilde "^2.0.2"
homedir-polyfill "^1.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ini "^1.3.4"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
is-windows "^1.0.1"
which "^1.2.14"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
globby@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/globby/-/globby-5.0.0.tgz#ebd84667ca0dbb330b99bcfc68eac2bc54370e0d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-69hGZ8oNuzMLmbz8aOrCvFQ3Dg0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
array-union "^1.0.1"
arrify "^1.0.0"
glob "^7.0.3"
object-assign "^4.0.1"
pify "^2.0.0"
pinkie-promise "^2.0.0"
globule@~0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/globule/-/globule-0.1.0.tgz#d9c8edde1da79d125a151b79533b978676346ae5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-2cjt3h2nnRJaFRt5UzuXhnY0auU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
glob "~3.1.21"
lodash "~1.0.1"
minimatch "~0.2.11"
glogg@^1.0.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/glogg/-/glogg-1.0.1.tgz#dcf758e44789cc3f3d32c1f3562a3676e6a34810"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-ynYqXLoluBKf9XGR1gA59yEJisIL7YHEH4xr3ZziHB5/yl4qWfaK8Js9jGe6gBGCSCKVqiyO30WnRZADvemUNw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
sparkles "^1.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
google-auth-library@0.12.0:
version "0.12.0"
resolved "https://registry.yarnpkg.com/google-auth-library/-/google-auth-library-0.12.0.tgz#a3fc6c296d00bb54e4d877ef581a05947330d07f"
integrity sha512-79qCXtJ1VweBmmLr4yLq9S4clZB2p5Y+iACvuKk9gu4JitEnPc+bQFmYvtCYehVR44MQzD1J8DVmYW2w677IEw==
dependencies:
gtoken "^1.2.3"
jws "^3.1.4"
lodash.isstring "^4.0.1"
lodash.merge "^4.6.0"
request "^2.81.0"
google-auth-library@^0.10.0:
version "0.10.0"
resolved "https://registry.yarnpkg.com/google-auth-library/-/google-auth-library-0.10.0.tgz#6e15babee85fd1dd14d8d128a295b6838d52136e"
integrity sha1-bhW6vuhf0d0U2NEoopW2g41SE24=
dependencies:
gtoken "^1.2.1"
jws "^3.1.4"
lodash.noop "^3.0.1"
request "^2.74.0"
google-auth-library@^1.3.1:
version "1.6.1"
resolved "https://registry.yarnpkg.com/google-auth-library/-/google-auth-library-1.6.1.tgz#9c73d831ad720c0c3048ab89d0ffdec714d07dd2"
integrity sha512-jYiWC8NA9n9OtQM7ANn0Tk464do9yhKEtaJ72pKcaBiEwn4LwcGYIYOfwtfsSm3aur/ed3tlSxbmg24IAT6gAg==
dependencies:
axios "^0.18.0"
gcp-metadata "^0.6.3"
gtoken "^2.3.0"
jws "^3.1.5"
lodash.isstring "^4.0.1"
lru-cache "^4.1.3"
retry-axios "^0.3.2"
google-auto-auth@^0.10.0:
version "0.10.1"
resolved "https://registry.yarnpkg.com/google-auto-auth/-/google-auto-auth-0.10.1.tgz#68834a6f3da59a6cb27fce56f76e3d99ee49d0a2"
integrity sha512-iIqSbY7Ypd32mnHGbYctp80vZzXoDlvI9gEfvtl3kmyy5HzOcrZCIGCBdSlIzRsg7nHpQiHE3Zl6Ycur6TSodQ==
dependencies:
async "^2.3.0"
gcp-metadata "^0.6.1"
google-auth-library "^1.3.1"
request "^2.79.0"
google-auto-auth@^0.7.2:
version "0.7.2"
resolved "https://registry.yarnpkg.com/google-auto-auth/-/google-auto-auth-0.7.2.tgz#bf9352d5c4a0897bf31fd9c491028b765fbea71e"
integrity sha512-ux2n2AE2g3+vcLXwL4dP/M12SFMRX5dzCzBfhAEkTeAB7dpyGdOIEj7nmUx0BHKaCcUQrRWg9kT63X/Mmtk1+A==
dependencies:
async "^2.3.0"
gcp-metadata "^0.3.0"
google-auth-library "^0.10.0"
request "^2.79.0"
google-p12-pem@^0.1.0:
version "0.1.2"
resolved "https://registry.yarnpkg.com/google-p12-pem/-/google-p12-pem-0.1.2.tgz#33c46ab021aa734fa0332b3960a9a3ffcb2f3177"
integrity sha1-M8RqsCGqc0+gMys5YKmj/8svMXc=
dependencies:
node-forge "^0.7.1"
google-p12-pem@^1.0.0:
version "1.0.3"
resolved "https://registry.yarnpkg.com/google-p12-pem/-/google-p12-pem-1.0.3.tgz#3d8acc140573339a5bca7b2f6a4b206bbea6d8d7"
integrity sha512-KGnAiMMWaJp4j4tYVvAjfP3wCKZRLv9M1Nir2wRRNWUYO7j1aX8O9Qgz+a8/EQ5rAvuo4SIu79n6SIdkNl7Msg==
dependencies:
node-forge "^0.7.5"
pify "^4.0.0"
googleapis@^23.0.2:
version "23.0.2"
resolved "https://registry.yarnpkg.com/googleapis/-/googleapis-23.0.2.tgz#18737965a9525b16e3e73b6cd660fcaeba6b792d"
integrity sha512-OobqDn586ogcF0dE+Byu5xZ6XmR/J7nkZN/wmhJoaxKdmELaf27ty2gKxGuq3I4/GDN+hcsUaMBueoQzFD3ObA==
dependencies:
async "2.6.0"
google-auth-library "0.12.0"
string-template "1.0.0"
got@^6.7.1:
version "6.7.1"
resolved "https://registry.yarnpkg.com/got/-/got-6.7.1.tgz#240cd05785a9a18e561dc1b44b41c763ef1e8db0"
integrity sha1-JAzQV4WpoY5WHcG0S0HHY+8ejbA=
dependencies:
create-error-class "^3.0.0"
duplexer3 "^0.1.4"
get-stream "^3.0.0"
is-redirect "^1.0.0"
is-retry-allowed "^1.0.0"
is-stream "^1.0.0"
lowercase-keys "^1.0.0"
safe-buffer "^5.0.1"
timed-out "^4.0.0"
unzip-response "^2.0.1"
url-parse-lax "^1.0.0"
got@^8.3.2:
version "8.3.2"
resolved "https://registry.yarnpkg.com/got/-/got-8.3.2.tgz#1d23f64390e97f776cac52e5b936e5f514d2e937"
integrity sha512-qjUJ5U/hawxosMryILofZCkm3C84PLJS/0grRIpjAwu+Lkxxj5cxeCU25BG0/3mDSpXKTyZr8oh8wIgLaH0QCw==
dependencies:
"@sindresorhus/is" "^0.7.0"
cacheable-request "^2.1.1"
decompress-response "^3.3.0"
duplexer3 "^0.1.4"
get-stream "^3.0.0"
into-stream "^3.1.0"
is-retry-allowed "^1.1.0"
isurl "^1.0.0-alpha5"
lowercase-keys "^1.0.0"
mimic-response "^1.0.0"
p-cancelable "^0.4.0"
p-timeout "^2.0.1"
pify "^3.0.0"
safe-buffer "^5.1.1"
timed-out "^4.0.1"
url-parse-lax "^3.0.0"
url-to-options "^1.0.1"
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
graceful-fs@^3.0.0, graceful-fs@~3.0.2:
version "3.0.11"
resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-3.0.11.tgz#7613c778a1afea62f25c630a086d7f3acbbdd818"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-dhPHeKGv6mLyXGMKCG1/Osu92Bg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
natives "^1.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
graceful-fs@^4.1.0, graceful-fs@^4.1.3, graceful-fs@^4.1.6, graceful-fs@^4.1.9:
Revert "build: allow bazel build ... (#22168)" This reverts commit 265ac8a106651e453b1bc91f3f9889bc70e7bcbb.
2018-02-14 23:41:12 -05:00
version "4.1.11"
resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.1.11.tgz#0e8bdfe4d1ddb8854d64e04ea7c00e2a026e5658"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Dovf5NHduIVNZOBOp8AOKgJuVlg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
graceful-fs@^4.1.11, graceful-fs@^4.1.15, graceful-fs@^4.1.2:
version "4.1.15"
resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.1.15.tgz#ffb703e1066e8a0eeaa4c8b80ba9253eeefbfb00"
integrity sha512-6uHUhOPEBgQ24HM+r6b/QwWfZq+yiFcipKFrOFiBEnWdy5sdzYoi+pJeQaPI5qOLRFqWmAXUPQNsielzdLoecA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
graceful-fs@~1.2.0:
version "1.2.3"
resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-1.2.3.tgz#15a4806a57547cb2d2dbf27f42e89a8c3451b364"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-FaSAaldUfLLS2/J/QuiajDRRs2Q=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
"graceful-readlink@>= 1.0.0":
version "1.0.1"
resolved "https://registry.yarnpkg.com/graceful-readlink/-/graceful-readlink-1.0.1.tgz#4cafad76bc62f02fa039b2f94e9a3dd3a391a725"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-TK+tdrxi8C+gObL5Tpo906ORpyU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
graphviz@0.0.7:
version "0.0.7"
resolved "https://registry.yarnpkg.com/graphviz/-/graphviz-0.0.7.tgz#e5ae4b5429353a099609c9d4a4b518b95516efee"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-5a5LVCk1OgmWCcnUpLUYuVUW7+4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
temp "~0.4.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
gtoken@^1.2.1, gtoken@^1.2.3:
version "1.2.3"
resolved "https://registry.yarnpkg.com/gtoken/-/gtoken-1.2.3.tgz#5509571b8afd4322e124cf66cf68115284c476d8"
integrity sha512-wQAJflfoqSgMWrSBk9Fg86q+sd6s7y6uJhIvvIPz++RElGlMtEqsdAR2oWwZ/WTEtp7P9xFbJRrT976oRgzJ/w==
dependencies:
google-p12-pem "^0.1.0"
jws "^3.0.0"
mime "^1.4.1"
request "^2.72.0"
gtoken@^2.3.0:
version "2.3.2"
resolved "https://registry.yarnpkg.com/gtoken/-/gtoken-2.3.2.tgz#49890a866c1f44e173099be95515db5872a92151"
integrity sha512-F8EObUGyC8Qd3WXTloNULZBwfUsOABoHElihB1F6zGhT/cy38iPL09wGLRY712I+hQnOyA+sYlgPFX2cOKz0qg==
dependencies:
gaxios "^1.0.4"
google-p12-pem "^1.0.0"
jws "^3.1.5"
mime "^2.2.0"
pify "^4.0.0"
build: downgrade `gulp-clang-format` to 1.0.23 (#31295) The `gulp format*` tasks have been broken since 5eb742621. These include the `gulp format:enforce` task, which is what runs on CI to enforce consistent code style. Here is what (I believe) happened: - I assume formatting was failing in 5eb742621 (moving `zone.js` into `angular/angular`). The reason must have been that [this glob pattern][1] matches `packages/zone.js/` (which is a directory) and passes it to `clang-format` claiming it is a file. - I further assume that in an attempt to fix the issue, `gulp-clang-format` was updated to the latest version (1.0.27) in 5eb742621. - `gulp format:enforce` stopped complaining, so everyone thought formatting was fine and moved on. - Formatting still wasn't fine, but the task completed successfully nevertheless :scream: - The reason is that angular/gulp-clang-format@55b697c5c (and subsequent commits) changed the way the `done()` callback was called, leaving it to `clang-format` to call it (while previously it was also called when the associated stream ended). - In the old version of `clang-format` that we are using (1.0.41), there is a bug (which has been fixed in angular/clang-format@4cce2c4ee): The callback is not called [unless the process exits with an error][2]. One can also see that the `gulp format:enforce` task is not completed in `gulp lint`. Example output from [build 374722][3]: ``` yarn gulp lint ... Starting 'format:enforce'... Starting 'validate-commit-messages'... ... Finished 'validate-commit-messages' after 833 ms Starting 'tools:build'... Finished 'tools:build' after 1.75 s Starting 'tslint'... Finished 'tslint' after 19 s Done in 21.82s. ``` Notice that all tasks have a corresponding "Finished X` log, except for `format:enforce`. For reference: The problem was originally reported by @ocombe on Slack ([discussion][4]). --- This commit fixes the issue by downgrading `gulp-clang-format` to 1.0.23. The linting failures due to formatting issues will be addressed in subsequent commits. [1]: https://github.com/angular/angular/blob/a8f3b317f/tools/gulp-tasks/format.js#L13 [2]: https://github.com/angular/clang-format/blob/b8c7df0b7/index.js#L95 [3]: https://circleci.com/gh/angular/angular/374722 [4]: https://angular-team.slack.com/archives/C042EU9T5/p1561480241191000 PR Close #31295
2019-06-26 14:09:32 -04:00
gulp-clang-format@1.0.23:
version "1.0.23"
resolved "https://registry.yarnpkg.com/gulp-clang-format/-/gulp-clang-format-1.0.23.tgz#fe258586b83998491e632fc0c4fc0ecdfa10c89f"
integrity sha1-/iWFhrg5mEkeYy/AxPwOzfoQyJ8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
clang-format "^1.0.32"
gulp-diff "^1.0.0"
build: downgrade `gulp-clang-format` to 1.0.23 (#31295) The `gulp format*` tasks have been broken since 5eb742621. These include the `gulp format:enforce` task, which is what runs on CI to enforce consistent code style. Here is what (I believe) happened: - I assume formatting was failing in 5eb742621 (moving `zone.js` into `angular/angular`). The reason must have been that [this glob pattern][1] matches `packages/zone.js/` (which is a directory) and passes it to `clang-format` claiming it is a file. - I further assume that in an attempt to fix the issue, `gulp-clang-format` was updated to the latest version (1.0.27) in 5eb742621. - `gulp format:enforce` stopped complaining, so everyone thought formatting was fine and moved on. - Formatting still wasn't fine, but the task completed successfully nevertheless :scream: - The reason is that angular/gulp-clang-format@55b697c5c (and subsequent commits) changed the way the `done()` callback was called, leaving it to `clang-format` to call it (while previously it was also called when the associated stream ended). - In the old version of `clang-format` that we are using (1.0.41), there is a bug (which has been fixed in angular/clang-format@4cce2c4ee): The callback is not called [unless the process exits with an error][2]. One can also see that the `gulp format:enforce` task is not completed in `gulp lint`. Example output from [build 374722][3]: ``` yarn gulp lint ... Starting 'format:enforce'... Starting 'validate-commit-messages'... ... Finished 'validate-commit-messages' after 833 ms Starting 'tools:build'... Finished 'tools:build' after 1.75 s Starting 'tslint'... Finished 'tslint' after 19 s Done in 21.82s. ``` Notice that all tasks have a corresponding "Finished X` log, except for `format:enforce`. For reference: The problem was originally reported by @ocombe on Slack ([discussion][4]). --- This commit fixes the issue by downgrading `gulp-clang-format` to 1.0.23. The linting failures due to formatting issues will be addressed in subsequent commits. [1]: https://github.com/angular/angular/blob/a8f3b317f/tools/gulp-tasks/format.js#L13 [2]: https://github.com/angular/clang-format/blob/b8c7df0b7/index.js#L95 [3]: https://circleci.com/gh/angular/angular/374722 [4]: https://angular-team.slack.com/archives/C042EU9T5/p1561480241191000 PR Close #31295
2019-06-26 14:09:32 -04:00
gulp-util "^3.0.4"
pkginfo "^0.3.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
stream-combiner2 "^1.1.1"
build: downgrade `gulp-clang-format` to 1.0.23 (#31295) The `gulp format*` tasks have been broken since 5eb742621. These include the `gulp format:enforce` task, which is what runs on CI to enforce consistent code style. Here is what (I believe) happened: - I assume formatting was failing in 5eb742621 (moving `zone.js` into `angular/angular`). The reason must have been that [this glob pattern][1] matches `packages/zone.js/` (which is a directory) and passes it to `clang-format` claiming it is a file. - I further assume that in an attempt to fix the issue, `gulp-clang-format` was updated to the latest version (1.0.27) in 5eb742621. - `gulp format:enforce` stopped complaining, so everyone thought formatting was fine and moved on. - Formatting still wasn't fine, but the task completed successfully nevertheless :scream: - The reason is that angular/gulp-clang-format@55b697c5c (and subsequent commits) changed the way the `done()` callback was called, leaving it to `clang-format` to call it (while previously it was also called when the associated stream ended). - In the old version of `clang-format` that we are using (1.0.41), there is a bug (which has been fixed in angular/clang-format@4cce2c4ee): The callback is not called [unless the process exits with an error][2]. One can also see that the `gulp format:enforce` task is not completed in `gulp lint`. Example output from [build 374722][3]: ``` yarn gulp lint ... Starting 'format:enforce'... Starting 'validate-commit-messages'... ... Finished 'validate-commit-messages' after 833 ms Starting 'tools:build'... Finished 'tools:build' after 1.75 s Starting 'tslint'... Finished 'tslint' after 19 s Done in 21.82s. ``` Notice that all tasks have a corresponding "Finished X` log, except for `format:enforce`. For reference: The problem was originally reported by @ocombe on Slack ([discussion][4]). --- This commit fixes the issue by downgrading `gulp-clang-format` to 1.0.23. The linting failures due to formatting issues will be addressed in subsequent commits. [1]: https://github.com/angular/angular/blob/a8f3b317f/tools/gulp-tasks/format.js#L13 [2]: https://github.com/angular/clang-format/blob/b8c7df0b7/index.js#L95 [3]: https://circleci.com/gh/angular/angular/374722 [4]: https://angular-team.slack.com/archives/C042EU9T5/p1561480241191000 PR Close #31295
2019-06-26 14:09:32 -04:00
stream-equal "0.1.6"
through2 "^0.6.3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
gulp-connect@5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/gulp-connect/-/gulp-connect-5.0.0.tgz#f2fdf306ae911468368c2285f2d782f13eddaf4e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8v3zBq6RFGg2jCKF8teC8T7dr04=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
connect "^2.30.0"
connect-livereload "^0.5.4"
event-stream "^3.3.2"
gulp-util "^3.0.6"
tiny-lr "^0.2.1"
style: update gulp task to format untracked and diff files separately (#24969) PR Close #24969
2018-09-10 21:19:14 -04:00
gulp-conventional-changelog@^2.0.3:
version "2.0.3"
resolved "https://registry.yarnpkg.com/gulp-conventional-changelog/-/gulp-conventional-changelog-2.0.3.tgz#80d3b558365bb0d662f61b20257d4084bbed6b07"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-DoDjADVYJTxTrBBBEZg+ISV8tNDPPQZeaTQ+cqXEyfNusjWpiCxOddrr/q0EV/aocTFjsCHNtWP/JGJq9lzmbA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
add-stream "^1.0.0"
style: update gulp task to format untracked and diff files separately (#24969) PR Close #24969
2018-09-10 21:19:14 -04:00
concat-stream "^1.6.0"
conventional-changelog "^2.0.3"
fancy-log "^1.3.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
object-assign "^4.0.1"
style: update gulp task to format untracked and diff files separately (#24969) PR Close #24969
2018-09-10 21:19:14 -04:00
plugin-error "^1.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
through2 "^2.0.0"
gulp-diff@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/gulp-diff/-/gulp-diff-1.0.0.tgz#101b23712dd6b107bd07d05ab88ea3ac485fed77"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-EBsjcS3WsQe9B9BauI6jrEhf7Xc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
cli-color "^1.0.0"
diff "^2.0.2"
event-stream "^3.1.5"
gulp-util "^3.0.6"
through2 "^2.0.0"
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
gulp-filter@^5.1.0:
version "5.1.0"
resolved "https://registry.yarnpkg.com/gulp-filter/-/gulp-filter-5.1.0.tgz#a05e11affb07cf7dcf41a7de1cb7b63ac3783e73"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-oF4Rr/sHz33PQafeHLe2OsN4PnM=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
multimatch "^2.0.0"
plugin-error "^0.1.2"
streamfilter "^1.0.5"
gulp-git@^2.7.0:
version "2.8.0"
resolved "https://registry.yarnpkg.com/gulp-git/-/gulp-git-2.8.0.tgz#c2b8e27566a008daccd0f235fec24a584c49abdd"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-45pahZGIcsb6eCJS9EGCdXqYBbxE1dtSbS03iXIF3dHHor1r37KMqwoQQJv1SXJjpLKc6ei+rdvIl7Ar6tB+ow==
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
any-shell-escape "^0.1.1"
fancy-log "^1.3.2"
lodash.template "^4.4.0"
plugin-error "^0.1.2"
require-dir "^1.0.0"
strip-bom-stream "^3.0.0"
through2 "^2.0.3"
vinyl "^2.0.1"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
gulp-tslint@8.1.2:
version "8.1.2"
resolved "https://registry.yarnpkg.com/gulp-tslint/-/gulp-tslint-8.1.2.tgz#e0f43194b473d7e76bb45a58fe8c60e7dfe3beb2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-0RNGqbp2TKPdbG+sWU3mNMXEMuF/noY1KS4+jd5lOStkvuFINkFL29dHX3IT1u+vVFD4Glwf+lkcdR2QMVNMzA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
gulp-util "~3.0.8"
map-stream "~0.0.7"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
through "~2.3.8"
build: downgrade `gulp-clang-format` to 1.0.23 (#31295) The `gulp format*` tasks have been broken since 5eb742621. These include the `gulp format:enforce` task, which is what runs on CI to enforce consistent code style. Here is what (I believe) happened: - I assume formatting was failing in 5eb742621 (moving `zone.js` into `angular/angular`). The reason must have been that [this glob pattern][1] matches `packages/zone.js/` (which is a directory) and passes it to `clang-format` claiming it is a file. - I further assume that in an attempt to fix the issue, `gulp-clang-format` was updated to the latest version (1.0.27) in 5eb742621. - `gulp format:enforce` stopped complaining, so everyone thought formatting was fine and moved on. - Formatting still wasn't fine, but the task completed successfully nevertheless :scream: - The reason is that angular/gulp-clang-format@55b697c5c (and subsequent commits) changed the way the `done()` callback was called, leaving it to `clang-format` to call it (while previously it was also called when the associated stream ended). - In the old version of `clang-format` that we are using (1.0.41), there is a bug (which has been fixed in angular/clang-format@4cce2c4ee): The callback is not called [unless the process exits with an error][2]. One can also see that the `gulp format:enforce` task is not completed in `gulp lint`. Example output from [build 374722][3]: ``` yarn gulp lint ... Starting 'format:enforce'... Starting 'validate-commit-messages'... ... Finished 'validate-commit-messages' after 833 ms Starting 'tools:build'... Finished 'tools:build' after 1.75 s Starting 'tslint'... Finished 'tslint' after 19 s Done in 21.82s. ``` Notice that all tasks have a corresponding "Finished X` log, except for `format:enforce`. For reference: The problem was originally reported by @ocombe on Slack ([discussion][4]). --- This commit fixes the issue by downgrading `gulp-clang-format` to 1.0.23. The linting failures due to formatting issues will be addressed in subsequent commits. [1]: https://github.com/angular/angular/blob/a8f3b317f/tools/gulp-tasks/format.js#L13 [2]: https://github.com/angular/clang-format/blob/b8c7df0b7/index.js#L95 [3]: https://circleci.com/gh/angular/angular/374722 [4]: https://angular-team.slack.com/archives/C042EU9T5/p1561480241191000 PR Close #31295
2019-06-26 14:09:32 -04:00
gulp-util@^3.0.0, gulp-util@^3.0.4, gulp-util@^3.0.6, gulp-util@~3.0.8:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "3.0.8"
resolved "https://registry.yarnpkg.com/gulp-util/-/gulp-util-3.0.8.tgz#0054e1e744502e27c04c187c3ecc505dd54bbb4f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-AFTh50RQLifATBh8PsxQXdVLu08=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
array-differ "^1.0.0"
array-uniq "^1.0.2"
beeper "^1.0.0"
chalk "^1.0.0"
dateformat "^2.0.0"
fancy-log "^1.1.0"
gulplog "^1.0.0"
has-gulplog "^0.1.0"
lodash._reescape "^3.0.0"
lodash._reevaluate "^3.0.0"
lodash._reinterpolate "^3.0.0"
lodash.template "^3.0.0"
minimist "^1.1.0"
multipipe "^0.1.2"
object-assign "^3.0.0"
replace-ext "0.0.1"
through2 "^2.0.0"
vinyl "^0.5.0"
gulp@3.9.1:
version "3.9.1"
resolved "https://registry.yarnpkg.com/gulp/-/gulp-3.9.1.tgz#571ce45928dd40af6514fc4011866016c13845b4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-VxzkWSjdQK9lFPxAEYZgFsE4RbQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
archy "^1.0.0"
chalk "^1.0.0"
deprecated "^0.0.1"
gulp-util "^3.0.0"
interpret "^1.0.0"
liftoff "^2.1.0"
minimist "^1.1.0"
orchestrator "^0.3.0"
pretty-hrtime "^1.0.0"
semver "^4.1.0"
tildify "^1.0.0"
v8flags "^2.0.2"
vinyl-fs "^0.3.0"
gulplog@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/gulplog/-/gulplog-1.0.0.tgz#e28c4d45d05ecbbed818363ce8f9c5926229ffe5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-4oxNRdBey77YGDY86PnFkmIp/+U=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
glogg "^1.0.0"
hammerjs@2.0.8:
version "2.0.8"
resolved "https://registry.yarnpkg.com/hammerjs/-/hammerjs-2.0.8.tgz#04ef77862cff2bb79d30f7692095930222bf60f1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-BO93hiz/K7edMPdpIJWTAiK/YPE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
handlebars@^4.0.2:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "4.0.11"
resolved "https://registry.yarnpkg.com/handlebars/-/handlebars-4.0.11.tgz#630a35dfe0294bc281edae6ffc5d329fc7982dcc"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Ywo13+ApS8KB7a5v/F0yn8eYLcw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
async "^1.4.0"
optimist "^0.6.1"
source-map "^0.4.4"
optionalDependencies:
uglify-js "^2.6"
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
handlebars@^4.0.3:
version "4.1.1"
resolved "https://registry.yarnpkg.com/handlebars/-/handlebars-4.1.1.tgz#6e4e41c18ebe7719ae4d38e5aca3d32fa3dd23d3"
integrity sha512-3Zhi6C0euYZL5sM0Zcy7lInLXKQ+YLcF/olbN010mzGQ4XVm50JeyBnMqofHh696GrciGruC7kCcApPDJvVgwA==
dependencies:
neo-async "^2.6.0"
optimist "^0.6.1"
source-map "^0.6.1"
optionalDependencies:
uglify-js "^3.1.4"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
har-schema@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/har-schema/-/har-schema-2.0.0.tgz#a94c2224ebcac04782a0d9035521f24735b7ec92"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-qUwiJOvKwEeCoNkDVSHyRzW37JI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
har-validator@~2.0.6:
version "2.0.6"
resolved "https://registry.yarnpkg.com/har-validator/-/har-validator-2.0.6.tgz#cdcbc08188265ad119b6a5a7c8ab70eecfb5d27d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-zcvAgYgmWtEZtqWnyKtw7s+10n0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
chalk "^1.1.1"
commander "^2.9.0"
is-my-json-valid "^2.12.4"
pinkie-promise "^2.0.0"
har-validator@~5.0.3:
version "5.0.3"
resolved "https://registry.yarnpkg.com/har-validator/-/har-validator-5.0.3.tgz#ba402c266194f15956ef15e0fcf242993f6a7dfd"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ukAsJmGU8VlW7xXg/PJCmT9qff0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
ajv "^5.1.0"
har-schema "^2.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
har-validator@~5.1.0:
version "5.1.3"
resolved "https://registry.yarnpkg.com/har-validator/-/har-validator-5.1.3.tgz#1ef89ebd3e4996557675eed9893110dc350fa080"
integrity sha512-sNvOCzEQNr/qrvJgc3UG/kD4QtlHycrzwS+6mfTrrSq97BvaYcPZZI1ZSqGSPR73Cxn4LKTD4PttRwfU7jWq5g==
dependencies:
ajv "^6.5.5"
har-schema "^2.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
has-ansi@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/has-ansi/-/has-ansi-2.0.0.tgz#34f5049ce1ecdf2b0649af3ef24e45ed35416d91"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-NPUEnOHs3ysGSa8+8k5F7TVBbZE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
ansi-regex "^2.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
has-binary2@~1.0.2:
version "1.0.3"
resolved "https://registry.yarnpkg.com/has-binary2/-/has-binary2-1.0.3.tgz#7776ac627f3ea77250cfc332dab7ddf5e4f5d11d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-G1LWKhDSvhGeAQ8mPVQlqNcOB2sJdwATtZKl2pDKKHfpf/rYj24lkinxf69blJbnsvtqqNU+L3SL50vzZhXOnw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
isarray "2.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
has-cors@1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/has-cors/-/has-cors-1.1.0.tgz#5e474793f7ea9843d1bb99c23eef49ff126fff39"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-XkdHk/fqmEPRu5nCPu9J/xJv/zk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
has-flag@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/has-flag/-/has-flag-1.0.0.tgz#9d9e793165ce017a00f00418c43f942a7b1d11fa"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nZ55MWXOAXoA8AQYxD+UKnsdEfo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
has-flag@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/has-flag/-/has-flag-3.0.0.tgz#b5d454dc2199ae225699f3467e5a07f3b955bafd"
integrity sha1-tdRU3CGZriJWmfNGfloH87lVuv0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
has-gulplog@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/has-gulplog/-/has-gulplog-0.1.0.tgz#6414c82913697da51590397dafb12f22967811ce"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ZBTIKRNpfaUVkDl9r7EvIpZ4Ec4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
sparkles "^1.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
has-symbol-support-x@^1.4.1:
version "1.4.2"
resolved "https://registry.yarnpkg.com/has-symbol-support-x/-/has-symbol-support-x-1.4.2.tgz#1409f98bc00247da45da67cee0a36f282ff26455"
integrity sha512-3ToOva++HaW+eCpgqZrCfN51IPB+7bJNVT6CUATzueB5Heb8o6Nam0V3HG5dlDvZU1Gn5QLcbahiKw/XVk5JJw==
has-to-string-tag-x@^1.2.0:
version "1.4.1"
resolved "https://registry.yarnpkg.com/has-to-string-tag-x/-/has-to-string-tag-x-1.4.1.tgz#a045ab383d7b4b2012a00148ab0aa5f290044d4d"
integrity sha512-vdbKfmw+3LoOYVr+mtxHaX5a96+0f3DljYd8JOqvOLsf5mw2Otda2qCDT9qRqLAhrjyQ0h7ual5nOiASpsGNFw==
dependencies:
has-symbol-support-x "^1.4.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
has-unicode@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/has-unicode/-/has-unicode-2.0.1.tgz#e0e6fe6a28cf51138855e086d1691e771de2a8b9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-4Ob+aijPUROIVeCG0Wkedx3iqLk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
has-value@^0.3.1:
version "0.3.1"
resolved "https://registry.yarnpkg.com/has-value/-/has-value-0.3.1.tgz#7b1f58bada62ca827ec0a2078025654845995e1f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ex9YutpiyoJ+wKIHgCVlSEWZXh8=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
get-value "^2.0.3"
has-values "^0.1.4"
isobject "^2.0.0"
has-value@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/has-value/-/has-value-1.0.0.tgz#18b281da585b1c5c51def24c930ed29a0be6b177"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-GLKB2lhbHFxR3vJMkw7SmgvmsXc=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
get-value "^2.0.6"
has-values "^1.0.0"
isobject "^3.0.0"
has-values@^0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/has-values/-/has-values-0.1.4.tgz#6d61de95d91dfca9b9a02089ad384bff8f62b771"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-bWHeldkd/Km5oCCJrThL/49it3E=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
has-values@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/has-values/-/has-values-1.0.0.tgz#95b0b63fec2146619a6fe57fe75628d5a39efe4f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-lbC2P+whRmGab+V/51Yo1aOe/k8=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
is-number "^3.0.0"
kind-of "^4.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
hash-stream-validation@^0.2.1:
version "0.2.1"
resolved "https://registry.yarnpkg.com/hash-stream-validation/-/hash-stream-validation-0.2.1.tgz#ecc9b997b218be5bb31298628bb807869b73dcd1"
integrity sha1-7Mm5l7IYvluzEphii7gHhptz3NE=
dependencies:
through2 "^2.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"hashish@>=0.0.2 <0.1":
version "0.0.4"
resolved "https://registry.yarnpkg.com/hashish/-/hashish-0.0.4.tgz#6d60bc6ffaf711b6afd60e426d077988014e6554"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-bWC8b/r3Ebav1g5CbQd5iAFOZVQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
traverse ">=0.2.4"
build: to fsevents@2.0.1 (#27469) the old version was failing to compile on MacOS Mojave 10.14.1. PR Close #27469
2018-12-05 13:10:58 -05:00
hawk@~3.1.3:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "3.1.3"
resolved "https://registry.yarnpkg.com/hawk/-/hawk-3.1.3.tgz#078444bd7c1640b0fe540d2c9b73d59678e8e1c4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-B4REvXwWQLD+VA0sm3PVlnjo4cQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
boom "2.x.x"
cryptiles "2.x.x"
hoek "2.x.x"
sntp "1.x.x"
build: update to rules_nodejs 0.38 (#32889) PR Close #32889
2019-09-27 18:49:59 -04:00
he@^1.1.1:
version "1.2.0"
resolved "https://registry.yarnpkg.com/he/-/he-1.2.0.tgz#84ae65fa7eafb165fddb61566ae14baf05664f0f"
integrity sha512-F/1DnUGPopORZi0ni+CvrCgHQ5FyEAHRLSApuYWMmrbSwoN2Mn/7k+Gl38gJnR7yyDZk6WLXwiGod1JOWNDKGw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
hoek@2.x.x:
version "2.16.3"
resolved "https://registry.yarnpkg.com/hoek/-/hoek-2.16.3.tgz#20bb7403d3cea398e91dc4710a8ff1b8274a25ed"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ILt0A9POo5jpHcRxCo/xuCdKJe0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
home-dir@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/home-dir/-/home-dir-1.0.0.tgz#2917eb44bdc9072ceda942579543847e3017fe4e"
integrity sha1-KRfrRL3JByztqUJXlUOEfjAX/k4=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
homedir-polyfill@^1.0.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/homedir-polyfill/-/homedir-polyfill-1.0.1.tgz#4c2bbc8a758998feebf5ed68580f76d46768b4bc"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-TCu8inWJmP7r9e1oWA921GdotLw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
parse-passwd "^1.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
hosted-git-info@^2.1.4, hosted-git-info@^2.6.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "2.7.1"
resolved "https://registry.yarnpkg.com/hosted-git-info/-/hosted-git-info-2.7.1.tgz#97f236977bd6e125408930ff6de3eec6281ec047"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-7T/BxH19zbcCTa8XkMlbK5lTo1WtgkFi3GvdWEyNuc4Vex7/9Dqbnpsf4JMydcfj9HCg4zUWFTL3Za6lapg5/w==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
http-browserify@^1.3.2:
version "1.7.0"
resolved "https://registry.yarnpkg.com/http-browserify/-/http-browserify-1.7.0.tgz#33795ade72df88acfbfd36773cefeda764735b20"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-M3la3nLfiKz7/TZ3PO/tp2RzWyA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
Base64 "~0.2.0"
inherits "~2.0.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
http-cache-semantics@3.8.1, http-cache-semantics@^3.8.1:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "3.8.1"
resolved "https://registry.yarnpkg.com/http-cache-semantics/-/http-cache-semantics-3.8.1.tgz#39b0e16add9b605bf0a9ef3d9daaf4843b4cacd2"
integrity sha512-5ai2iksyV8ZXmnZhHH4rWPoxxistEexSi5936zIQ1bnNTW5VnA85B6P/VpXiRM017IgRvb2kKo1a//y+0wSp3w==
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
http-errors@1.6.3, http-errors@~1.6.2, http-errors@~1.6.3:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.6.3"
resolved "https://registry.yarnpkg.com/http-errors/-/http-errors-1.6.3.tgz#8b55680bb4be283a0b5bf4ea2e38580be1d9320d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-i1VoC7S+KDoLW/TqLjhYC+HZMg0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
depd "~1.1.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
inherits "2.0.3"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
setprototypeof "1.1.0"
statuses ">= 1.4.0 < 2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
http-errors@~1.3.1:
version "1.3.1"
resolved "https://registry.yarnpkg.com/http-errors/-/http-errors-1.3.1.tgz#197e22cdebd4198585e8694ef6786197b91ed942"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-GX4izevUGYWF6GlO9nhhl7ke2UI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
inherits "~2.0.1"
statuses "1"
http-parser-js@>=0.4.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.4.13"
resolved "https://registry.yarnpkg.com/http-parser-js/-/http-parser-js-0.4.13.tgz#3bd6d6fde6e3172c9334c3b33b6c193d80fe1137"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-O9bW/ebjFyyTNMOzO2wZPYD+ETc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
http-proxy-agent@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/http-proxy-agent/-/http-proxy-agent-2.1.0.tgz#e4821beef5b2142a2026bd73926fe537631c5405"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-qwHbBLV7WviBl0rQsOzH6o5lwyOIvwp/BdFnvVxXORldu5TmjFfjzBcWUWS5kWAZhmv+JtiDhSuQCp4sBfbIgg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
agent-base "4"
debug "3.1.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
http-proxy@1.16.2:
version "1.16.2"
resolved "https://registry.yarnpkg.com/http-proxy/-/http-proxy-1.16.2.tgz#06dff292952bf64dbe8471fa9df73066d4f37742"
integrity sha1-Bt/ykpUr9k2+hHH6nfcwZtTzd0I=
dependencies:
eventemitter3 "1.x.x"
requires-port "1.x.x"
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
http-proxy@^1.13.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.17.0"
resolved "https://registry.yarnpkg.com/http-proxy/-/http-proxy-1.17.0.tgz#7ad38494658f84605e2f6db4436df410f4e5be9a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-Taqn+3nNvYRfJ3bGvKfBSRwy1v6eePlm3oc/aWVxZp57DQr5Eq3xhKJi7Z4hZpS8PC3H4qI+Yly5EmFacGuA/g==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
eventemitter3 "^3.0.0"
follow-redirects "^1.0.0"
requires-port "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to rules_nodejs 0.38 (#32889) PR Close #32889
2019-09-27 18:49:59 -04:00
http-proxy@^1.8.1:
version "1.18.0"
resolved "https://registry.yarnpkg.com/http-proxy/-/http-proxy-1.18.0.tgz#dbe55f63e75a347db7f3d99974f2692a314a6a3a"
integrity sha512-84I2iJM/n1d4Hdgc6y2+qY5mDaz2PUVjlg9znE9byl+q0uC3DeByqBGReQu5tpLK0TAqTIXScRUV+dg7+bUPpQ==
dependencies:
eventemitter3 "^4.0.0"
follow-redirects "^1.0.0"
requires-port "^1.0.0"
http-server@^0.11.1:
version "0.11.1"
resolved "https://registry.yarnpkg.com/http-server/-/http-server-0.11.1.tgz#2302a56a6ffef7f9abea0147d838a5e9b6b6a79b"
integrity sha512-6JeGDGoujJLmhjiRGlt8yK8Z9Kl0vnl/dQoQZlc4oeqaUoAKQg94NILLfrY3oWzSyFaQCVNTcKE5PZ3cH8VP9w==
dependencies:
colors "1.0.3"
corser "~2.0.0"
ecstatic "^3.0.0"
http-proxy "^1.8.1"
opener "~1.4.0"
optimist "0.6.x"
portfinder "^1.0.13"
union "~0.4.3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
http-signature@~1.1.0:
version "1.1.1"
resolved "https://registry.yarnpkg.com/http-signature/-/http-signature-1.1.1.tgz#df72e267066cd0ac67fb76adf8e134a8fbcf91bf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-33LiZwZs0Kxn+3at+OE0qPvPkb8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
assert-plus "^0.2.0"
jsprim "^1.2.2"
sshpk "^1.7.0"
http-signature@~1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/http-signature/-/http-signature-1.2.0.tgz#9aecd925114772f3d95b65a60abb8f7c18fbace1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-muzZJRFHcvPZW2WmCruPfBj7rOE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
assert-plus "^1.0.0"
jsprim "^1.2.2"
sshpk "^1.7.0"
https-browserify@0.0.0:
version "0.0.0"
resolved "https://registry.yarnpkg.com/https-browserify/-/https-browserify-0.0.0.tgz#b3ffdfe734b2a3d4a9efd58e8654c91fce86eafd"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-s//f5zSyo9Sp79WOhlTJH86G6v0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
https-proxy-agent@1.0.0, https-proxy-agent@^1.0.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.0"
resolved "https://registry.yarnpkg.com/https-proxy-agent/-/https-proxy-agent-1.0.0.tgz#35f7da6c48ce4ddbfa264891ac593ee5ff8671e6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-NffabEjOTdv6JkiRrFk+5f+GceY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
agent-base "2"
debug "2"
extend "3"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
https-proxy-agent@^2.2.1:
version "2.2.1"
resolved "https://registry.yarnpkg.com/https-proxy-agent/-/https-proxy-agent-2.2.1.tgz#51552970fa04d723e04c56d04178c3f92592bbc0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-HPCTS1LW51bcyMYbxUIOO4HEOlQ1/1qRaFWcyxvwaqUS9TY88aoEuHUY33kuAh1YhVVaDQhLZsnPd+XNARWZlQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
agent-base "^4.1.0"
debug "^3.1.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
humanize-ms@^1.2.1:
version "1.2.1"
resolved "https://registry.yarnpkg.com/humanize-ms/-/humanize-ms-1.2.1.tgz#c46e3159a293f6b896da29316d8b6fe8bb79bbed"
integrity sha1-xG4xWaKT9riW2ikxbYtv6Lt5u+0=
dependencies:
ms "^2.0.0"
refactor: add a commit-msg git hook to check commit messages (#22969) The commit command will fail if the commit message header does not follow the Angular convetions as defined in /CONTRIBUTING.md. You can force the commit by adding the `--no-verify` option. NOTE: You should remove all unused hooks (in <angular>/.git/hooks) before running `yarn` so that husky hooks are installed correctly. PR Close #22969
2018-03-23 19:07:33 -04:00
husky@^0.14.3:
version "0.14.3"
resolved "https://registry.yarnpkg.com/husky/-/husky-0.14.3.tgz#c69ed74e2d2779769a17ba8399b54ce0b63c12c3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-e21wivqHpstpoiWA/Yi8eFti8E+sQDSS53cpJsPptPs295QTOQR0ZwnHo2TXy1XOpZFD9rPOd3NpmqTK6uMLJA==
refactor: add a commit-msg git hook to check commit messages (#22969) The commit command will fail if the commit message header does not follow the Angular convetions as defined in /CONTRIBUTING.md. You can force the commit by adding the `--no-verify` option. NOTE: You should remove all unused hooks (in <angular>/.git/hooks) before running `yarn` so that husky hooks are installed correctly. PR Close #22969
2018-03-23 19:07:33 -04:00
dependencies:
is-ci "^1.0.10"
normalize-path "^1.0.0"
strip-indent "^2.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
i@0.3.x:
version "0.3.6"
resolved "https://registry.yarnpkg.com/i/-/i-0.3.6.tgz#d96c92732076f072711b6b10fd7d4f65ad8ee23d"
integrity sha1-2WyScyB28HJxG2sQ/X1PZa2O4j0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
iconv-lite@0.4.11:
version "0.4.11"
resolved "https://registry.yarnpkg.com/iconv-lite/-/iconv-lite-0.4.11.tgz#2ecb42fd294744922209a2e7c404dac8793d8ade"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-LstC/SlHRJIiCaLnxATayHk9it4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
iconv-lite@0.4.13:
version "0.4.13"
resolved "https://registry.yarnpkg.com/iconv-lite/-/iconv-lite-0.4.13.tgz#1f88aba4ab0b1508e8312acc39345f36e992e2f2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-H4irpKsLFQjoMSrMOTRfNumS4vI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
iconv-lite@0.4.23, iconv-lite@^0.4.5:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "0.4.23"
resolved "https://registry.yarnpkg.com/iconv-lite/-/iconv-lite-0.4.23.tgz#297871f63be507adcfbfca715d0cd0eed84e9a63"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-neyTUVFtahjf0mB3dZT77u+8O0QB89jFdnBkd5P1JgYPbPaia3gXXOVL2fq8VyU2gMMD7SaN7QukTB/pmXYvDA==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
safer-buffer ">= 2.1.2 < 3"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
iconv-lite@^0.4.24, iconv-lite@^0.4.4, iconv-lite@~0.4.13:
version "0.4.24"
resolved "https://registry.yarnpkg.com/iconv-lite/-/iconv-lite-0.4.24.tgz#2022b4b25fbddc21d2f524974a474aafe733908b"
integrity sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==
dependencies:
safer-buffer ">= 2.1.2 < 3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ieee754@^1.1.4:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.1.12"
resolved "https://registry.yarnpkg.com/ieee754/-/ieee754-1.1.12.tgz#50bf24e5b9c8bb98af4964c941cdb0918da7b60b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-GguP+DRY+pJ3soyIiGPTvdiVXjZ+DbXOxGpXn3eMvNW4x4irjqXm4wHKscC+TfxSJ0yw/S1F24tqdMNsMZTiLA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
iferr@^0.1.5:
version "0.1.5"
resolved "https://registry.yarnpkg.com/iferr/-/iferr-0.1.5.tgz#c60eed69e6d8fdb6b3104a1fcbca1c192dc5b501"
integrity sha1-xg7taebY/bazEEofy8ocGS3FtQE=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
ignore-walk@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/ignore-walk/-/ignore-walk-3.0.1.tgz#a83e62e7d272ac0e3b551aaa82831a19b69f82f8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-DTVlMx3IYPe0/JJcYP7Gxg7ttZZu3IInhuEhbchuqneY9wWe5Ojy2mXLBaQFUQmo0AW2r3qG7m1mg86js+gnlQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
minimatch "^3.0.4"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
immediate@~3.0.5:
version "3.0.6"
resolved "https://registry.yarnpkg.com/immediate/-/immediate-3.0.6.tgz#9db1dbd0faf8de6fbe0f5dd5e56bb606280de69b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nbHb0Pr43m++D13V5Wu2BigN5ps=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
import-lazy@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/import-lazy/-/import-lazy-2.1.0.tgz#05698e3d45c88e8d7e9d92cb0584e77f096f3e43"
integrity sha1-BWmOPUXIjo1+nZLLBYTnfwlvPkM=
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
imurmurhash@^0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/imurmurhash/-/imurmurhash-0.1.4.tgz#9218b9b2b928a238b13dc4fb6b6d576f231453ea"
integrity sha1-khi5srkoojixPcT7a21XbyMUU+o=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
incremental-dom@0.4.1:
version "0.4.1"
resolved "https://registry.yarnpkg.com/incremental-dom/-/incremental-dom-0.4.1.tgz#80eb151969bd52054dc29a4720c4e89abd103401"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-gOsVGWm9UgVNwppHIMTomr0QNAE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
indent-string@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/indent-string/-/indent-string-2.1.0.tgz#8e2d48348742121b4a8218b7a137e9a52049dc80"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ji1INIdCEhtKghi3oTfppSBJ3IA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
repeating "^2.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
indent-string@^3.0.0:
version "3.2.0"
resolved "https://registry.yarnpkg.com/indent-string/-/indent-string-3.2.0.tgz#4a5fd6d27cc332f37e5419a504dbb837105c9289"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Sl/W0nzDMvN+VBmlBNu4NxBckok=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
indexof@0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/indexof/-/indexof-0.0.1.tgz#82dc336d232b9062179d05ab3293a66059fd435d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-gtwzbSMrkGIXnQWrMpOmYFn9Q10=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
inflight@^1.0.4:
version "1.0.6"
resolved "https://registry.yarnpkg.com/inflight/-/inflight-1.0.6.tgz#49bd6331d7d02d0c09bc910a1075ba8165b56df9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Sb1jMdfQLQwJvJEKEHW6gWW1bfk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
once "^1.3.0"
wrappy "1"
inherits@1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/inherits/-/inherits-1.0.2.tgz#ca4309dadee6b54cc0b8d247e8d7c7a0975bdc9b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ykMJ2t7mtUzAuNJH6NfHoJdb3Js=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
inherits@2, inherits@2.0.3, inherits@^2.0.1, inherits@^2.0.3, inherits@~2.0.0, inherits@~2.0.1, inherits@~2.0.3:
version "2.0.3"
resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.3.tgz#633c2c83e3da42a502f52466022480f4208261de"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Yzwsg+PaQqUC9SRmAiSA9CCCYd4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
inherits@2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.1.tgz#b17d08d326b4423e568eff719f91b0b1cbdf69f1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-sX0I0ya0Qj5Wjv9xn5GwscvfafE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
ini@1.3.5, ini@^1.2.0, ini@^1.3.2, ini@^1.3.4, ini@~1.3.0, ini@~1.3.3:
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
version "1.3.5"
resolved "https://registry.yarnpkg.com/ini/-/ini-1.3.5.tgz#eee25f56db1c9ec6085e0c22778083f596abf927"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-RZY5huIKCMRWDUqZlEi72f/lmXKMvuszcMBduliQ3nnWbx9X/ZBQO7DijMEYS9EhHBb2qacRUMtC7svLwe0lcw==
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
inquirer@6.2.2:
version "6.2.2"
resolved "https://registry.yarnpkg.com/inquirer/-/inquirer-6.2.2.tgz#46941176f65c9eb20804627149b743a218f25406"
integrity sha512-Z2rREiXA6cHRR9KBOarR3WuLlFzlIfAEIiB45ll5SSadMg7WqOh1MKEjjndfuH5ewXdixWCxqnVfGOQzPeiztA==
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
dependencies:
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
ansi-escapes "^3.2.0"
chalk "^2.4.2"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
cli-cursor "^2.1.0"
cli-width "^2.0.0"
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
external-editor "^3.0.3"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
figures "^2.0.0"
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
lodash "^4.17.11"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
mute-stream "0.0.7"
run-async "^2.2.0"
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
rxjs "^6.4.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
string-width "^2.1.0"
strip-ansi "^5.0.0"
through "^2.3.6"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
inquirer@^0.12.0:
version "0.12.0"
resolved "https://registry.yarnpkg.com/inquirer/-/inquirer-0.12.0.tgz#1ef2bfd63504df0bc75785fff8c2c41df12f077e"
integrity sha1-HvK/1jUE3wvHV4X/+MLEHfEvB34=
dependencies:
ansi-escapes "^1.1.0"
ansi-regex "^2.0.0"
chalk "^1.0.0"
cli-cursor "^1.0.1"
cli-width "^2.0.0"
figures "^1.3.5"
lodash "^4.3.0"
readline2 "^1.0.1"
run-async "^0.1.0"
rx-lite "^3.1.2"
string-width "^1.0.1"
strip-ansi "^3.0.0"
through "^2.3.6"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
interpret@^0.6.4:
version "0.6.6"
resolved "https://registry.yarnpkg.com/interpret/-/interpret-0.6.6.tgz#fecd7a18e7ce5ca6abfb953e1f86213a49f1625b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-/s16GOfOXKar+5U+H4YhOknxYls=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
interpret@^1.0.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.1.0"
resolved "https://registry.yarnpkg.com/interpret/-/interpret-1.1.0.tgz#7ed1b1410c6a0e0f78cf95d3b8440c63f78b8614"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ftGxQQxqDg94z5XTuEQMY/eLhhQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
into-stream@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/into-stream/-/into-stream-3.1.0.tgz#96fb0a936c12babd6ff1752a17d05616abd094c6"
integrity sha1-lvsKk2wSur1v8XUqF9BWFqvQlMY=
dependencies:
from2 "^2.1.1"
p-is-promise "^1.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
invert-kv@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/invert-kv/-/invert-kv-1.0.0.tgz#104a8e4aaca6d3d8cd157a8ef8bfab2d7a3ffdb6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-EEqOSqym09jNFXqO+L+rLXo//bY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
invert-kv@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/invert-kv/-/invert-kv-2.0.0.tgz#7393f5afa59ec9ff5f67a27620d11c226e3eec02"
integrity sha512-wPVv/y/QQ/Uiirj/vh3oP+1Ww+AWehmi1g5fFWGPF6IpCBCDVrhgHRMvrLfdYcwDh3QJbGXDW4JAuzxElLSqKA==
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
ip@^1.1.5:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.1.5"
resolved "https://registry.yarnpkg.com/ip/-/ip-1.1.5.tgz#bdded70114290828c0a039e72ef25f5aaec4354a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-vd7XARQpCCjAoDnnLvJfWq7ENUo=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
ipaddr.js@1.8.0:
version "1.8.0"
resolved "https://registry.yarnpkg.com/ipaddr.js/-/ipaddr.js-1.8.0.tgz#eaa33d6ddd7ace8f7f6fe0c9ca0440e706738b1e"
integrity sha1-6qM9bd16zo9/b+DJygRA5wZzix4=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
is-absolute@^0.1.7:
version "0.1.7"
resolved "https://registry.yarnpkg.com/is-absolute/-/is-absolute-0.1.7.tgz#847491119fccb5fb436217cc737f7faad50f603f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-hHSREZ/MtftDYhfMc39/qtUPYD8=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
is-relative "^0.1.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
is-absolute@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-absolute/-/is-absolute-1.0.0.tgz#395e1ae84b11f26ad1795e73c17378e48a301576"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-dOWoqflvcydARa360Gvv18DZ/gRuHKi2NU/wU5X1ZFzdYfH29nkiNZsF3mp4OJ3H4yo9Mx8A/uAGNzpzPN3yBA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
is-relative "^1.0.0"
is-windows "^1.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
is-accessor-descriptor@^0.1.6:
version "0.1.6"
resolved "https://registry.yarnpkg.com/is-accessor-descriptor/-/is-accessor-descriptor-0.1.6.tgz#a9e12cb3ae8d876727eeef3843f8a0897b5c98d6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-qeEss66Nh2cn7u84Q/igiXtcmNY=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
kind-of "^3.0.2"
is-accessor-descriptor@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-accessor-descriptor/-/is-accessor-descriptor-1.0.0.tgz#169c2f6d3df1f992618072365c9b0ea1f6878656"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-m5hnHTkcVsPfqx3AKlyttIPb7J+XykHvJP2B9bZDjlhLIoEq4XoK64Vg7boZlVWYK6LUY94dYPEE7Lh0ZkZKcQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
kind-of "^6.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-arrayish@^0.2.1:
version "0.2.1"
resolved "https://registry.yarnpkg.com/is-arrayish/-/is-arrayish-0.2.1.tgz#77c99840527aa8ecb1a8ba697b80645a7a926a9d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-d8mYQFJ6qOyxqLppe4BkWnqSap0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-binary-path@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/is-binary-path/-/is-binary-path-1.0.1.tgz#75f16642b480f187a711c814161fd3a4a7655898"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-dfFmQrSA8YenEcgUFh/TpKdlWJg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
binary-extensions "^1.0.0"
is-buffer@^1.1.5:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.1.6"
resolved "https://registry.yarnpkg.com/is-buffer/-/is-buffer-1.1.6.tgz#efaa2ea9daa0d7ab2ea13a97b2b8ad51fefbe8be"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-NcdALwpXkTm5Zvvbk7owOUSvVvBKDgKP5/ewfXEznmQFfs4ZRmanOeKBTjRVjka3QFoN6XJ+9F3USqfHqTaU5w==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-builtin-module@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-builtin-module/-/is-builtin-module-1.0.0.tgz#540572d34f7ac3119f8f76c30cbc1b1e037affbe"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-VAVy0096wxGfj3bDDLwbHgN6/74=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
builtin-modules "^1.0.0"
refactor: add a commit-msg git hook to check commit messages (#22969) The commit command will fail if the commit message header does not follow the Angular convetions as defined in /CONTRIBUTING.md. You can force the commit by adding the `--no-verify` option. NOTE: You should remove all unused hooks (in <angular>/.git/hooks) before running `yarn` so that husky hooks are installed correctly. PR Close #22969
2018-03-23 19:07:33 -04:00
is-ci@^1.0.10:
version "1.1.0"
resolved "https://registry.yarnpkg.com/is-ci/-/is-ci-1.1.0.tgz#247e4162e7860cebbdaf30b774d6b0ac7dcfe7a5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-c7TnwxLePuqIlxHgr7xtxzycJPegNHFuIrBkwbf8hc58//+Op1CqFkyS+xnIMkwn9UsJIwc174BIjkyBmSpjKg==
refactor: add a commit-msg git hook to check commit messages (#22969) The commit command will fail if the commit message header does not follow the Angular convetions as defined in /CONTRIBUTING.md. You can force the commit by adding the `--no-verify` option. NOTE: You should remove all unused hooks (in <angular>/.git/hooks) before running `yarn` so that husky hooks are installed correctly. PR Close #22969
2018-03-23 19:07:33 -04:00
dependencies:
ci-info "^1.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
is-data-descriptor@^0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/is-data-descriptor/-/is-data-descriptor-0.1.4.tgz#0b5ee648388e2c860282e793f1856fec3f301b56"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-C17mSDiOLIYCgueT8YVv7D8wG1Y=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
kind-of "^3.0.2"
is-data-descriptor@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-data-descriptor/-/is-data-descriptor-1.0.0.tgz#d84876321d0e7add03990406abbbbd36ba9268c7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-jbRXy1FmtAoCjQkVmIVYwuuqDFUbaOeDjmed1tOGPrsMhtJA4rD9tkgA0F1qJ3gRFRXcHYVkdeaP50Q5rE/jLQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
kind-of "^6.0.0"
is-descriptor@^0.1.0:
version "0.1.6"
resolved "https://registry.yarnpkg.com/is-descriptor/-/is-descriptor-0.1.6.tgz#366d8240dde487ca51823b1ab9f07a10a78251ca"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-avDYr0SB3DwO9zsMov0gKCESFYqCnE4hq/4z3TdUlukEy5t9C0YRq7HLrsN52NAcqXKaepeCD0n+B0arnVG3Hg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
is-accessor-descriptor "^0.1.6"
is-data-descriptor "^0.1.4"
kind-of "^5.0.0"
is-descriptor@^1.0.0, is-descriptor@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/is-descriptor/-/is-descriptor-1.0.2.tgz#3b159746a66604b04f8c81524ba365c5f14d86ec"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-2eis5WqQGV7peooDyLmNEPUrps9+SXX5c9pL3xEB+4e9HnGuDa7mB7kHxHw4CbqS9k1T2hOH3miL8n8WtiYVtg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
is-accessor-descriptor "^1.0.0"
is-data-descriptor "^1.0.0"
kind-of "^6.0.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-dotfile@^1.0.0:
version "1.0.3"
resolved "https://registry.yarnpkg.com/is-dotfile/-/is-dotfile-1.0.3.tgz#a6a2f32ffd2dfb04f5ca25ecd0f6b83cf798a1e1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-pqLzL/0t+wT1yiXs0Pa4PPeYoeE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-equal-shallow@^0.1.3:
version "0.1.3"
resolved "https://registry.yarnpkg.com/is-equal-shallow/-/is-equal-shallow-0.1.3.tgz#2238098fc221de0bcfa5d9eac4c45d638aa1c534"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-IjgJj8Ih3gvPpdnqxMRdY4qhxTQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-primitive "^2.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
is-extendable@^0.1.0, is-extendable@^0.1.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.1.1"
resolved "https://registry.yarnpkg.com/is-extendable/-/is-extendable-0.1.1.tgz#62b110e289a471418e3ec36a617d472e301dfc89"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-YrEQ4omkcUGOPsNqYX1HLjAd/Ik=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
is-extendable@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/is-extendable/-/is-extendable-1.0.1.tgz#a7470f9e426733d81bd81e1155264e3a3507cab4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-arnXMxT1hhoKo9k1LZdmlNyJdDDfy2v0fXjFlmok4+i8ul/6WlbVge9bhM74OpNPQPMGUToDtz+KXa1PneJxOA==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
is-plain-object "^2.0.4"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-extglob@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-extglob/-/is-extglob-1.0.0.tgz#ac468177c4943405a092fc8f29760c6ffc6206c0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-rEaBd8SUNAWgkvyPKXYMb/xiBsA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
is-extglob@^2.1.0, is-extglob@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/is-extglob/-/is-extglob-2.1.1.tgz#a88c02535791f02ed37c76a1b9ea9773c833f8c2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-qIwCU1eR8C7TfHahueqXc8gz+MI=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-finite@^1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/is-finite/-/is-finite-1.0.2.tgz#cc6677695602be550ef11e8b4aa6305342b6d0aa"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-zGZ3aVYCvlUO8R6LSqYwU0K20Ko=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
number-is-nan "^1.0.0"
is-fullwidth-code-point@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-fullwidth-code-point/-/is-fullwidth-code-point-1.0.0.tgz#ef9e31386f031a7f0d643af82fde50c457ef00cb"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-754xOG8DGn8NZDr4L95QxFfvAMs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
number-is-nan "^1.0.0"
is-fullwidth-code-point@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/is-fullwidth-code-point/-/is-fullwidth-code-point-2.0.0.tgz#a3b30a5c4f199183167aaab93beefae3ddfb654f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-o7MKXE8ZkYMWeqq5O+764937ZU8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-glob@^2.0.0, is-glob@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/is-glob/-/is-glob-2.0.1.tgz#d096f926a3ded5600f3fdfd91198cb0888c2d863"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-0Jb5JqPe1WAPP9/ZEZjLCIjC2GM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-extglob "^1.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
is-glob@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/is-glob/-/is-glob-3.1.0.tgz#7ba5ae24217804ac70707b96922567486cc3e84a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-e6WuJCF4BKxwcHuWkiVnSGzD6Eo=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
is-extglob "^2.1.0"
is-glob@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/is-glob/-/is-glob-4.0.0.tgz#9521c76845cc2610a85203ddf080a958c2ffabc0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-lSHHaEXMJhCoUgPd8ICpWML/q8A=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
is-extglob "^2.1.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
is-installed-globally@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/is-installed-globally/-/is-installed-globally-0.1.0.tgz#0dfd98f5a9111716dd535dda6492f67bf3d25a80"
integrity sha1-Df2Y9akRFxbdU13aZJL2e/PSWoA=
dependencies:
global-dirs "^0.1.0"
is-path-inside "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-module@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-module/-/is-module-1.0.0.tgz#3258fb69f78c14d5b815d664336b4cffb6441591"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Mlj7afeMFNW4FdZkM2tM/7ZEFZE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
is-my-ip-valid@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-my-ip-valid/-/is-my-ip-valid-1.0.0.tgz#7b351b8e8edd4d3995d4d066680e664d94696824"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-gmh/eWXROncUzRnIa1Ubrt5b8ep/MGSnfAUI3aRp+sqTCs1tv1Isl8d8F6JmkN3dXKc3ehZMrtiPN9eL03NuaQ==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
is-my-json-valid@^2.12.4:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "2.17.2"
resolved "https://registry.yarnpkg.com/is-my-json-valid/-/is-my-json-valid-2.17.2.tgz#6b2103a288e94ef3de5cf15d29dd85fc4b78d65c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-IBhBslgngMQN8DDSppmgDv7RNrlFotuuDsKcrCP3+HbFaVivIBU7u9oiiErw8sH4ynx3+gOGQ3q2otkgiSi6kg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
generate-function "^2.0.0"
generate-object-property "^1.1.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
is-my-ip-valid "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
jsonpointer "^4.0.0"
xtend "^4.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
is-npm@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-npm/-/is-npm-1.0.0.tgz#f2fb63a65e4905b406c86072765a1a4dc793b9f4"
integrity sha1-8vtjpl5JBbQGyGBydloaTceTufQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-number@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/is-number/-/is-number-0.1.1.tgz#69a7af116963d47206ec9bd9b48a14216f1e3806"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-aaevEWlj1HIG7JvZtIoUIW8eOAY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-number@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/is-number/-/is-number-2.1.0.tgz#01fcbbb393463a548f2f466cce16dece49db908f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Afy7s5NGOlSPL0ZszhbezknbkI8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
kind-of "^3.0.2"
is-number@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/is-number/-/is-number-3.0.0.tgz#24fd6201a4782cf50561c810276afc7d12d71195"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-JP1iAaR4LPUFYcgQJ2r8fRLXEZU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
kind-of "^3.0.2"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
is-number@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/is-number/-/is-number-4.0.0.tgz#0026e37f5454d73e356dfe6564699867c6a7f0ff"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-rSklcAIlf1OmFdyAqbnWTLVelsQ58uvZ66S/ZyawjWqIviTWCjg2PzVGw8WUA+nNuPTqb4wgA+NszrJ+08LlgQ==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-obj@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/is-obj/-/is-obj-1.0.1.tgz#3e4729ac1f5fde025cd7d83a896dab9f4f67db0f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-PkcprB9f3gJc19g6iW2rn09n2w8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
is-object@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/is-object/-/is-object-1.0.1.tgz#8952688c5ec2ffd6b03ecc85e769e02903083470"
integrity sha1-iVJojF7C/9awPsyF52ngKQMINHA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-path-cwd@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-path-cwd/-/is-path-cwd-1.0.0.tgz#d225ec23132e89edd38fda767472e62e65f1106d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-0iXsIxMuie3Tj9p2dHLmLmXxEG0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-path-in-cwd@^1.0.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/is-path-in-cwd/-/is-path-in-cwd-1.0.1.tgz#5ac48b345ef675339bd6c7a48a912110b241cf52"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-FjV1RTW48E7CWM7eE/J2NJvAEEVektecDBVBE5Hh3nM1Jd0kvhHtX68Pr3xsDf857xt3Y4AkwVULK1Vku62aaQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-path-inside "^1.0.0"
is-path-inside@^1.0.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/is-path-inside/-/is-path-inside-1.0.1.tgz#8ef5b7de50437a3fdca6b4e865ef7aa55cb48036"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-jvW33lBDej/cprToZe96pVy0gDY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
path-is-inside "^1.0.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
is-plain-obj@^1.0.0, is-plain-obj@^1.1.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.1.0"
resolved "https://registry.yarnpkg.com/is-plain-obj/-/is-plain-obj-1.1.0.tgz#71a50c8429dfca773c92a390a4a03b39fcd51d3e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-caUMhCnfync8kqOQpKA7OfzVHT4=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
is-plain-object@^2.0.1, is-plain-object@^2.0.3, is-plain-object@^2.0.4:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.0.4"
resolved "https://registry.yarnpkg.com/is-plain-object/-/is-plain-object-2.0.4.tgz#2c163b3fafb1b606d9d17928f05c2a1c38e07677"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-h5PpgXkWitc38BBMYawTYMWJHFZJVnBquFE57xFpjB8pJFiF6gZ+bU+WyI/yqXiFR5mdLsgYNaPe8uao6Uv9Og==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
isobject "^3.0.1"
is-posix-bracket@^0.1.0:
version "0.1.1"
resolved "https://registry.yarnpkg.com/is-posix-bracket/-/is-posix-bracket-0.1.1.tgz#3334dc79774368e92f016e6fbc0a88f5cd6e6bc4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-MzTceXdDaOkvAW5vvAqI9c1ua8Q=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-primitive@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/is-primitive/-/is-primitive-2.0.0.tgz#207bab91638499c07b2adf240a41a87210034575"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-IHurkWOEmcB7Kt8kCkGochADRXU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
is-promise@^2.1, is-promise@^2.1.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.1.0"
resolved "https://registry.yarnpkg.com/is-promise/-/is-promise-2.1.0.tgz#79a2a9ece7f096e80f36d2b2f3bc16c1ff4bf3fa"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-eaKp7OfwlugPNtKy87wWwf9L8/o=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-property@^1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/is-property/-/is-property-1.0.2.tgz#57fe1c4e48474edd65b09911f26b1cd4095dda84"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-V/4cTkhHTt1lsJkR8msc1Ald2oQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
is-redirect@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-redirect/-/is-redirect-1.0.0.tgz#1d03dded53bd8db0f30c26e4f95d36fc7c87dc24"
integrity sha1-HQPd7VO9jbDzDCbk+V02/HyH3CQ=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
is-relative@^0.1.0:
version "0.1.3"
resolved "https://registry.yarnpkg.com/is-relative/-/is-relative-0.1.3.tgz#905fee8ae86f45b3ec614bc3c15c869df0876e82"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-kF/uiuhvRbPsYUvDwVyGnfCHboI=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
is-relative@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-relative/-/is-relative-1.0.0.tgz#a1bb6935ce8c5dba1e8b9754b9b2dcc020e2260d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-Kw/ReK0iqwKeu0MITLFuj0jbPAmEiOsIwyIXvvbfa6QfmN9pkD1M+8pdk7Rl/dTKbH34/XBFMbgD4iMJhLQbGA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
is-unc-path "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
is-retry-allowed@^1.0.0, is-retry-allowed@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/is-retry-allowed/-/is-retry-allowed-1.1.0.tgz#11a060568b67339444033d0125a61a20d564fb34"
integrity sha1-EaBgVotnM5REAz0BJaYaINVk+zQ=
is-stream-ended@^0.1.0:
version "0.1.4"
resolved "https://registry.yarnpkg.com/is-stream-ended/-/is-stream-ended-0.1.4.tgz#f50224e95e06bce0e356d440a4827cd35b267eda"
integrity sha512-xj0XPvmr7bQFTvirqnFr50o0hQIh6ZItDqloxt5aJrR4NQsYeSsyFQERYGCAzfindAcnKjINnwEEgLx4IqVzQw==
is-stream@^1.0.0, is-stream@^1.1.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.1.0"
resolved "https://registry.yarnpkg.com/is-stream/-/is-stream-1.1.0.tgz#12d4a3dd4e68e0b79ceb8dbc84173ae80d91ca44"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-EtSj3U5o4Lec6428hBc66A2RykQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-subset@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/is-subset/-/is-subset-0.1.1.tgz#8a59117d932de1de00f245fcdd39ce43f1e939a6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ilkRfZMt4d4A8kX83TnOQ/HpOaY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-text-path@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/is-text-path/-/is-text-path-1.0.1.tgz#4e1aa0fb51bfbcb3e92688001397202c1775b66e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Thqg+1G/vLPpJogAE5cgLBd1tm4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
text-extensions "^1.0.0"
is-typedarray@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-typedarray/-/is-typedarray-1.0.0.tgz#e479c80858df0c1b11ddda6940f96011fcda4a9a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-5HnICFjfDBsR3dppQPlgEfzaSpo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
is-unc-path@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-unc-path/-/is-unc-path-1.0.0.tgz#d731e8898ed090a12c352ad2eaed5095ad322c9d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-mrGpVd0fs7WWLfVsStvgF6iEJnbjDFZh9/emhRDcGWTduTfNHd9CHeUwH3gYIjdbwo4On6hunkztwOaAw0yllQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
unc-path-regex "^0.1.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
is-url@^1.2.2:
version "1.2.4"
resolved "https://registry.yarnpkg.com/is-url/-/is-url-1.2.4.tgz#04a4df46d28c4cff3d73d01ff06abeb318a1aa52"
integrity sha512-ITvGim8FhRiYe4IQ5uHSkj7pVaPDrCTkNd3yq3cV7iZAcJdHTUMPMEHcqSOy9xZ9qFenQCvi+2wjH9a1nXqHww==
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
is-utf8@^0.2.0, is-utf8@^0.2.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.2.1"
resolved "https://registry.yarnpkg.com/is-utf8/-/is-utf8-0.2.1.tgz#4b0da1442104d1b336340e80797e865cf39f7d72"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Sw2hRCEE0bM2NA6AeX6GXPOffXI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
is-windows@^1.0.0, is-windows@^1.0.1, is-windows@^1.0.2:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/is-windows/-/is-windows-1.0.2.tgz#d1850eb9791ecd18e6182ce12a30f396634bb19d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-eXK1UInq2bPmjyX6e3VHIzMLobc4J94i4AWn+Hpq3OU5KkrRC96OAcR3PRJ/pGu6m8TRnBHP9dkXQVsT/COVIA==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
is-wsl@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/is-wsl/-/is-wsl-1.1.0.tgz#1f16e4aa22b04d1336b66188a66af3c600c3a66d"
integrity sha1-HxbkqiKwTRM2tmGIpmrzxgDDpm0=
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
is@^3.0.1, is@^3.2.0, is@^3.2.1:
version "3.3.0"
resolved "https://registry.yarnpkg.com/is/-/is-3.3.0.tgz#61cff6dd3c4193db94a3d62582072b44e5645d79"
integrity sha512-nW24QBoPcFGGHJGUwnfpI7Yc5CdqWNdsyHQszVE/z2pKHXzh7FZ5GWhJqSyaQ9wMkQnsTx+kAI8bHlCX4tKdbg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
isarray@0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/isarray/-/isarray-0.0.1.tgz#8a18acfca9a8f4177e09abfc6038939b05d1eedf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ihis/Kmo9Bd+Cav8YDiTmwXR7t8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
isarray@1.0.0, isarray@^1.0.0, isarray@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/isarray/-/isarray-1.0.0.tgz#bb935d48582cba168c06834957a54a3e07124f11"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
isarray@2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/isarray/-/isarray-2.0.1.tgz#a37d94ed9cda2d59865c9f76fe596ee1f338741e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-o32U7ZzaLVmGXJ92/llu4fM4dB4=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
isbinaryfile@^3.0.0:
version "3.0.2"
resolved "https://registry.yarnpkg.com/isbinaryfile/-/isbinaryfile-3.0.2.tgz#4a3e974ec0cba9004d3fc6cde7209ea69368a621"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Sj6XTsDLqQBNP8bN5yCeppNopiE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
isemail@1.x.x:
version "1.2.0"
resolved "https://registry.yarnpkg.com/isemail/-/isemail-1.2.0.tgz#be03df8cc3e29de4d2c5df6501263f1fa4595e9a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-vgPfjMPineTSxd9lASY/H6RZXpo=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
isexe@^1.1.1:
version "1.1.2"
resolved "https://registry.yarnpkg.com/isexe/-/isexe-1.1.2.tgz#36f3e22e60750920f5e7241a476a8c6a42275ad0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-NvPiLmB1CSD15yQaR2qMakInWtA=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
isexe@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/isexe/-/isexe-2.0.0.tgz#e8fbf374dc556ff8947a10dcb0572d633f2cfa10"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-6PvzdNxVb/iUehDcsFctYz8s+hA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
isobject@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/isobject/-/isobject-2.1.0.tgz#f065561096a3f1da2ef46272f815c840d87e0c89"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8GVWEJaj8dou9GJy+BXIQNh+DIk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
isarray "1.0.0"
isobject@^3.0.0, isobject@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/isobject/-/isobject-3.0.1.tgz#4e431e92b11a9731636aa1f9c8d1ccbcfdab78df"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-TkMekrEalzFjaqH5yNHMvP2reN8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
isstream@0.1.x, isstream@~0.1.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.1.2"
resolved "https://registry.yarnpkg.com/isstream/-/isstream-0.1.2.tgz#47e63f7af55afa6f92e1500e690eb8b8529c099a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-R+Y/evVa+m+S4VAOaQ64uFKcCZo=
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
istanbul-lib-coverage@^1.2.0, istanbul-lib-coverage@^1.2.1:
version "1.2.1"
resolved "https://registry.yarnpkg.com/istanbul-lib-coverage/-/istanbul-lib-coverage-1.2.1.tgz#ccf7edcd0a0bb9b8f729feeb0930470f9af664f0"
integrity sha512-PzITeunAgyGbtY1ibVIUiV679EFChHjoMNRibEIobvmrCRaIgwLxNucOSimtNWUhEib/oO7QY2imD75JVgCJWQ==
istanbul-lib-report@^1.1.3:
version "1.1.5"
resolved "https://registry.yarnpkg.com/istanbul-lib-report/-/istanbul-lib-report-1.1.5.tgz#f2a657fc6282f96170aaf281eb30a458f7f4170c"
integrity sha512-UsYfRMoi6QO/doUshYNqcKJqVmFe9w51GZz8BS3WB0lYxAllQYklka2wP9+dGZeHYaWIdcXUx8JGdbqaoXRXzw==
dependencies:
istanbul-lib-coverage "^1.2.1"
mkdirp "^0.5.1"
path-parse "^1.0.5"
supports-color "^3.1.2"
istanbul-reports@^1.3.0:
version "1.5.1"
resolved "https://registry.yarnpkg.com/istanbul-reports/-/istanbul-reports-1.5.1.tgz#97e4dbf3b515e8c484caea15d6524eebd3ff4e1a"
integrity sha512-+cfoZ0UXzWjhAdzosCPP3AN8vvef8XDkWtTfgaN+7L3YTpNYITnCaEkceo5SEYy644VkHka/P1FvkWvrG/rrJw==
dependencies:
handlebars "^4.0.3"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
isurl@^1.0.0-alpha5:
version "1.0.0"
resolved "https://registry.yarnpkg.com/isurl/-/isurl-1.0.0.tgz#b27f4f49f3cdaa3ea44a0a5b7f3462e6edc39d67"
integrity sha512-1P/yWsxPlDtn7QeRD+ULKQPaIaN6yF368GZ2vDfv0AL0NwpStafjWCDDdn0k8wgFMWpVAqG7oJhxHnlud42i9w==
dependencies:
has-to-string-tag-x "^1.2.0"
is-object "^1.0.1"
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
jasmine-core@2.8.0, jasmine-core@~2.8.0:
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
version "2.8.0"
resolved "https://registry.yarnpkg.com/jasmine-core/-/jasmine-core-2.8.0.tgz#bcc979ae1f9fd05701e45e52e65d3a5d63f1a24e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-vMl5rh+f0FcB5F5S5l06XWPxok4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to latest bazel rules (#28931) PR Close #28931
2019-02-22 16:22:11 -05:00
jasmine-core@^3.1.0:
build: upgrade jasmine to 3.1.0 (#19904) PR Close #19904
2018-07-05 14:18:38 -04:00
version "3.1.0"
resolved "https://registry.yarnpkg.com/jasmine-core/-/jasmine-core-3.1.0.tgz#a4785e135d5df65024dfc9224953df585bd2766c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-pHheE11d9lAk38kiSVPfWFvSdmw=
build: upgrade jasmine to 2.99.x and fix tests (#19904) PR Close #19904
2018-07-04 18:53:51 -04:00
build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) nodejs rules 0.34.0 now includes protractor_web_test_suite rule (via new @bazel/protractor rule) so we switch to that location for that rule in this PR so that /packages/bazel/src/protractor can be removed in a future PR this PR also brings in node toolchain support which was released in nodejs rules 0.33.0. this is a prerequisite for RBE for mac & windows users bazel schematics also updated with the same. @bazel/bazel 0.28.1 npm package includes transitive dep on hide-bazel-files so we're able to remove an explicit dep on that as well. PR Close #31824
2019-07-24 11:52:26 -04:00
jasmine-core@^3.3, jasmine-core@~3.4.0:
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
version "3.4.0"
resolved "https://registry.yarnpkg.com/jasmine-core/-/jasmine-core-3.4.0.tgz#2a74618e966026530c3518f03e9f845d26473ce3"
integrity sha512-HU/YxV4i6GcmiH4duATwAbJQMlE0MsDIR5XmSVxURxKHn3aGAdbY1/ZJFmVRbKtnLwIxxMJD7gYaPsypcbYimg==
build: update to latest bazel rules (#28931) PR Close #28931
2019-02-22 16:22:11 -05:00
jasmine-core@~3.3.0:
version "3.3.0"
resolved "https://registry.yarnpkg.com/jasmine-core/-/jasmine-core-3.3.0.tgz#dea1cdc634bc93c7e0d4ad27185df30fa971b10e"
integrity sha512-3/xSmG/d35hf80BEN66Y6g9Ca5l/Isdeg/j6zvbTYlTzeKinzmaTM4p9am5kYqOmE05D7s1t8FGjzdSnbUbceA==
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
jasmine@2.8.0:
version "2.8.0"
resolved "https://registry.yarnpkg.com/jasmine/-/jasmine-2.8.0.tgz#6b089c0a11576b1f16df11b80146d91d4e8b8a3e"
integrity sha1-awicChFXax8W3xG4AUbZHU6Lij4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
exit "^0.1.2"
glob "^7.0.6"
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
jasmine-core "~2.8.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) nodejs rules 0.34.0 now includes protractor_web_test_suite rule (via new @bazel/protractor rule) so we switch to that location for that rule in this PR so that /packages/bazel/src/protractor can be removed in a future PR this PR also brings in node toolchain support which was released in nodejs rules 0.33.0. this is a prerequisite for RBE for mac & windows users bazel schematics also updated with the same. @bazel/bazel 0.28.1 npm package includes transitive dep on hide-bazel-files so we're able to remove an explicit dep on that as well. PR Close #31824
2019-07-24 11:52:26 -04:00
jasmine@^3.1.0:
build: update to latest bazel rules (#28931) PR Close #28931
2019-02-22 16:22:11 -05:00
version "3.3.1"
resolved "https://registry.yarnpkg.com/jasmine/-/jasmine-3.3.1.tgz#d61bb1dd8888859bd11ea83074a78ee13d949905"
integrity sha512-/vU3/H7U56XsxIXHwgEuWpCgQ0bRi2iiZeUpx7Nqo8n1TpoDHfZhkPIc7CO8I4pnMzYsi3XaSZEiy8cnTfujng==
build: upgrade jasmine to 3.1.0 (#19904) PR Close #19904
2018-07-05 14:18:38 -04:00
dependencies:
glob "^7.0.6"
build: update to latest bazel rules (#28931) PR Close #28931
2019-02-22 16:22:11 -05:00
jasmine-core "~3.3.0"
build: upgrade jasmine to 3.1.0 (#19904) PR Close #19904
2018-07-05 14:18:38 -04:00
build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) nodejs rules 0.34.0 now includes protractor_web_test_suite rule (via new @bazel/protractor rule) so we switch to that location for that rule in this PR so that /packages/bazel/src/protractor can be removed in a future PR this PR also brings in node toolchain support which was released in nodejs rules 0.33.0. this is a prerequisite for RBE for mac & windows users bazel schematics also updated with the same. @bazel/bazel 0.28.1 npm package includes transitive dep on hide-bazel-files so we're able to remove an explicit dep on that as well. PR Close #31824
2019-07-24 11:52:26 -04:00
jasmine@~3.4.0:
version "3.4.0"
resolved "https://registry.yarnpkg.com/jasmine/-/jasmine-3.4.0.tgz#0fa68903ff0c9697459cd044b44f4dcef5ec8bdc"
integrity sha512-sR9b4n+fnBFDEd7VS2el2DeHgKcPiMVn44rtKFumq9q7P/t8WrxsVIZPob4UDdgcDNCwyDqwxCt4k9TDRmjPoQ==
dependencies:
glob "^7.1.3"
jasmine-core "~3.4.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
jasminewd2@^2.1.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/jasminewd2/-/jasminewd2-2.2.0.tgz#e37cf0b17f199cce23bea71b2039395246b4ec4e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-43zwsX8ZnM4jvqcbIDk5Uka07E4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
jest-worker@^24.0.0:
version "24.6.0"
resolved "https://registry.yarnpkg.com/jest-worker/-/jest-worker-24.6.0.tgz#7f81ceae34b7cde0c9827a6980c35b7cdc0161b3"
integrity sha512-jDwgW5W9qGNvpI1tNnvajh0a5IE/PuGLFmHk6aR/BZFz8tSgGw17GsDPXAJ6p91IvYDjOw8GpFbvvZGAK+DPQQ==
dependencies:
merge-stream "^1.0.1"
supports-color "^6.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
jetpack-id@0.0.4:
version "0.0.4"
resolved "https://registry.yarnpkg.com/jetpack-id/-/jetpack-id-0.0.4.tgz#6fc35a394a4aea190820a2ce7f23d2bb53512a9b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-b8NaOUpK6hkIIKLOfyPSu1NRKps=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
jetpack-id@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/jetpack-id/-/jetpack-id-1.0.0.tgz#2cf9fbae46d8074fc16b7de0071c8efebca473a6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-LPn7rkbYB0/Ba33gBxyO/rykc6Y=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
jetpack-validation@0.0.7:
version "0.0.7"
resolved "https://registry.yarnpkg.com/jetpack-validation/-/jetpack-validation-0.0.7.tgz#5418065b029af3db7782fc53775d52a633fb04ba"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-VBgGWwKa89t3gvxTd11SpjP7BLo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
jetpack-id "0.0.4"
resolve "^0.7.1"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
semver "^5.3.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
jju@^1.1.0, jju@~1.4.0:
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
version "1.4.0"
resolved "https://registry.yarnpkg.com/jju/-/jju-1.4.0.tgz#a3abe2718af241a2b2904f84a625970f389ae32a"
integrity sha1-o6vicYryQaKykE+EpiWXDzia4yo=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
joi@^6.10.1:
version "6.10.1"
resolved "https://registry.yarnpkg.com/joi/-/joi-6.10.1.tgz#4d50c318079122000fe5f16af1ff8e1917b77e06"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-TVDDGAeRIgAP5fFq8f+OGRe3fgY=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
hoek "2.x.x"
isemail "1.x.x"
moment "2.x.x"
topo "1.x.x"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
join-path@^1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/join-path/-/join-path-1.1.1.tgz#10535a126d24cbd65f7ffcdf15ef2e631076b505"
integrity sha1-EFNaEm0ky9Zff/zfFe8uYxB2tQU=
dependencies:
as-array "^2.0.0"
url-join "0.0.1"
valid-url "^1"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
jpm-core@0.0.11:
version "0.0.11"
resolved "https://registry.yarnpkg.com/jpm-core/-/jpm-core-0.0.11.tgz#88904d78087aadc6e9f22825dcb34a67cf2e3ac7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-iJBNeAh6rcbp8igl3LNKZ88uOsc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
jpm@1.3.1:
version "1.3.1"
resolved "https://registry.yarnpkg.com/jpm/-/jpm-1.3.1.tgz#430c98193e87692f9ccd72f6cb348eaf224dfe15"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-QwyYGT6HaS+czXL2yzSOryJN/hU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
commander "2.9.0"
decompress-zip "0.3.0"
firefox-profile "0.4.0"
fs-extra "0.30.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
fs-promise "0.3.1"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
fx-runner "1.0.5"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
jetpack-id "0.0.4"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
jetpack-validation "0.0.7"
jpm-core "0.0.11"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
jsontoxml "0.0.11"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
jszip "2.4.0"
lodash "4.11.1"
minimatch "3.0.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
mozilla-toolkit-versioning "0.0.2"
mozilla-version-comparator "1.0.2"
node-watch "0.3.4"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
object-assign "4.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
open "0.0.5"
promzard "0.3.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
read "1.0.7"
semver "5.1.0"
sign-addon "0.2.0"
tmp "0.0.28"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
when "3.7.2"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
xml2js "0.4.16"
zip-dir "1.0.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update jquery to latest (#28719) Versions less than 3.0.0 have security vulnerabilities PR Close #28719
2019-02-13 19:09:00 -05:00
jquery@3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/jquery/-/jquery-3.0.0.tgz#95a2a9541291a9f819e016f85ba247116d03e4ab"
integrity sha1-laKpVBKRqfgZ4Bb4W6JHEW0D5Ks=
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 06:33:17 -05:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
js-tokens@^3.0.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "3.0.2"
resolved "https://registry.yarnpkg.com/js-tokens/-/js-tokens-3.0.2.tgz#9866df395102130e38f7f996bceb65443209c25b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-mGbfOVECEw449/mWvOtlRDIJwls=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
js-tokens@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/js-tokens/-/js-tokens-4.0.0.tgz#19203fb59991df98e3a287050d4647cdeaf32499"
integrity sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
jsbn@~0.1.0:
version "0.1.1"
resolved "https://registry.yarnpkg.com/jsbn/-/jsbn-0.1.1.tgz#a5e654c2e5a2deb5f201d96cefbca80c0ef2f513"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-peZUwuWi3rXyAdls77yoDA7y9RM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
json-buffer@3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/json-buffer/-/json-buffer-3.0.0.tgz#5b1f397afc75d677bde8bcfc0e47e1f9a3d9a898"
integrity sha1-Wx85evx11ne96Lz8Dkfh+aPZqJg=
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
json-parse-better-errors@^1.0.0, json-parse-better-errors@^1.0.1:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/json-parse-better-errors/-/json-parse-better-errors-1.0.2.tgz#bb867cfb3450e69107c131d1c514bab3dc8bcaa9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-mrqyZKfX5EhL7hvqcV6WG1yYjnjeuYDzDhhcAAUrq8Po85NBQBJP+ZDUT75qZQ98IkUoBqdkExkukOU7Ts2wrw==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
json-parse-helpfulerror@^1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/json-parse-helpfulerror/-/json-parse-helpfulerror-1.0.3.tgz#13f14ce02eed4e981297b64eb9e3b932e2dd13dc"
integrity sha1-E/FM4C7tTpgSl7ZOueO5MuLdE9w=
dependencies:
jju "^1.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
json-schema-traverse@^0.3.0:
version "0.3.1"
resolved "https://registry.yarnpkg.com/json-schema-traverse/-/json-schema-traverse-0.3.1.tgz#349a6d44c53a51de89b40805c5d5e59b417d3340"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-NJptRMU6Ud6JtAgFxdXlm0F9M0A=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
feat(bazel): Bazel workspace schematics (#26971) This commit creates a schematics for Bazel workspace. PR Close #26971
2018-09-14 10:03:29 -04:00
json-schema-traverse@^0.4.1:
version "0.4.1"
resolved "https://registry.yarnpkg.com/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz#69f6a87d9513ab8bb8fe63bdb0979c448e684660"
integrity sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
json-schema@0.2.3:
version "0.2.3"
resolved "https://registry.yarnpkg.com/json-schema/-/json-schema-0.2.3.tgz#b480c892e59a2f05954ce727bd3f2a4e882f9e13"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-tIDIkuWaLwWVTOcnvT8qTogvnhM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
json-stringify-safe@^5.0.1, json-stringify-safe@~5.0.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "5.0.1"
resolved "https://registry.yarnpkg.com/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz#1296a2d58fd45f19a0f6ce01d65701e2c735b6eb"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Epai1Y/UXxmg9s4B1lcB4sc1tus=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
json5@^0.5.0:
version "0.5.1"
resolved "https://registry.yarnpkg.com/json5/-/json5-0.5.1.tgz#1eade7acc012034ad84e2396767ead9fa5495821"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Hq3nrMASA0rYTiOWdn6tn6VJWCE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update version of Angular CLI and Build Optimizer used for tests (#28372) PR Close #28372
2019-01-25 11:33:22 -05:00
json5@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/json5/-/json5-1.0.1.tgz#779fb0018604fa854eacbf6252180d83543e3dbe"
integrity sha512-aKS4WQjPenRxiQsC93MNfjx+nbF4PAdYzmd/1JIj8HYzqfbu86beTuNgXDzPknWk0n0uARlyewZo4s++ES36Ow==
dependencies:
minimist "^1.2.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
jsonfile@^2.1.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.4.0"
resolved "https://registry.yarnpkg.com/jsonfile/-/jsonfile-2.4.0.tgz#3736a2b428b87bbda0cc83b53fa3d633a35c2ae8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-NzaitCi4e72gzIO1P6PWM6NcKug=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
optionalDependencies:
graceful-fs "^4.1.6"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
jsonfile@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/jsonfile/-/jsonfile-4.0.0.tgz#8771aae0799b64076b76640fca058f9c10e33ecb"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-h3Gq4HmbZAdrdmQPygWPnBDjPss=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
optionalDependencies:
graceful-fs "^4.1.6"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
jsonify@~0.0.0:
version "0.0.0"
resolved "https://registry.yarnpkg.com/jsonify/-/jsonify-0.0.0.tgz#2c74b6ee41d93ca51b7b5aaee8f503631d252a73"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-LHS27kHZPKUbe1qu6PUDYx0lKnM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
jsonparse@^1.2.0:
version "1.3.1"
resolved "https://registry.yarnpkg.com/jsonparse/-/jsonparse-1.3.1.tgz#3f4dae4a91fac315f71062f8521cc239f1366280"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-P02uSpH6wxX3EGL4UhzCOfE2YoA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
jsonpointer@^4.0.0:
version "4.0.1"
resolved "https://registry.yarnpkg.com/jsonpointer/-/jsonpointer-4.0.1.tgz#4fd92cb34e0e9db3c89c8622ecf51f9b978c6cb9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-T9kss04OnbPInIYi7PUfm5eMbLk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
jsonschema@^1.0.2:
version "1.2.4"
resolved "https://registry.yarnpkg.com/jsonschema/-/jsonschema-1.2.4.tgz#a46bac5d3506a254465bc548876e267c6d0d6464"
integrity sha512-lz1nOH69GbsVHeVgEdvyavc/33oymY1AZwtePMiMj4HZPMbP5OIKK3zT9INMWjwua/V4Z4yq7wSlBbSG+g4AEw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
jsontoxml@0.0.11:
version "0.0.11"
resolved "https://registry.yarnpkg.com/jsontoxml/-/jsontoxml-0.0.11.tgz#373ab5b2070be3737a5fb3e32fd1b7b81870caa4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Nzq1sgcL43N6X7PjL9G3uBhwyqQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
jsonwebtoken@7.1.9:
version "7.1.9"
resolved "https://registry.yarnpkg.com/jsonwebtoken/-/jsonwebtoken-7.1.9.tgz#847804e5258bec5a9499a8dc4a5e7a3bae08d58a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-hHgE5SWL7FqUmajcSl56O64I1Yo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
joi "^6.10.1"
jws "^3.1.3"
lodash.once "^4.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ms "^0.7.1"
xtend "^4.0.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
jsonwebtoken@^8.2.1:
version "8.4.0"
resolved "https://registry.yarnpkg.com/jsonwebtoken/-/jsonwebtoken-8.4.0.tgz#8757f7b4cb7440d86d5e2f3becefa70536c8e46a"
integrity sha512-coyXjRTCy0pw5WYBpMvWOMN+Kjaik2MwTUIq9cna/W7NpO9E+iYbumZONAz3hcr+tXFJECoQVrtmIoC3Oz0gvg==
dependencies:
jws "^3.1.5"
lodash.includes "^4.3.0"
lodash.isboolean "^3.0.3"
lodash.isinteger "^4.0.4"
lodash.isnumber "^3.0.3"
lodash.isplainobject "^4.0.6"
lodash.isstring "^4.0.1"
lodash.once "^4.0.0"
ms "^2.1.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
jsprim@^1.2.2:
version "1.4.1"
resolved "https://registry.yarnpkg.com/jsprim/-/jsprim-1.4.1.tgz#313e66bc1e5cc06e438bc1b7499c2e5c56acb6a2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-MT5mvB5cwG5Di8G3SZwuXFastqI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
assert-plus "1.0.0"
extsprintf "1.3.0"
json-schema "0.2.3"
verror "1.10.0"
jstransform@^8.2.0:
version "8.2.0"
resolved "https://registry.yarnpkg.com/jstransform/-/jstransform-8.2.0.tgz#e43f697f7cc01a1e7c827dd9df5a79d29d0c50bb"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-5D9pf3zAGh58gn3Z31p50p0MULs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
base62 "0.1.1"
esprima-fb "8001.1001.0-dev-harmony-fb"
source-map "0.1.31"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
jszip@2.4.0:
version "2.4.0"
resolved "https://registry.yarnpkg.com/jszip/-/jszip-2.4.0.tgz#487a93b76c3bffa6cb085cd61eb934eabe2d294f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-SHqTt2w7/6bLCFzWHrk06r4tKU8=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
pako "~0.2.5"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
jszip@^2.4.0:
version "2.6.1"
resolved "https://registry.yarnpkg.com/jszip/-/jszip-2.6.1.tgz#b88f3a7b2e67a2a048152982c7a3756d9c4828f0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-uI86ey5noqBIFSmCx6N1bZxIKPA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
pako "~1.0.2"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
jszip@^3.1.3:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "3.1.5"
resolved "https://registry.yarnpkg.com/jszip/-/jszip-3.1.5.tgz#e3c2a6c6d706ac6e603314036d43cd40beefdf37"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-5W8NUaFRFRqTOL7ZDDrx5qWHJyBXy6velVudIzQUSoqAAYqzSh2Z7/m0Rf1QbmQJccegD0r+YZxBjzqoBiEeJQ==
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
core-js "~2.3.0"
es6-promise "~3.0.2"
lie "~3.1.0"
pako "~1.0.2"
readable-stream "~2.0.6"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
jwa@^1.1.5:
version "1.1.6"
resolved "https://registry.yarnpkg.com/jwa/-/jwa-1.1.6.tgz#87240e76c9808dbde18783cf2264ef4929ee50e6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-tBO/cf++BUsJkYql/kBbJroKOgHWEigTKBAjjBEmrMGYd1QMBC74Hr4Wo2zCZw6ZrVhlJPvoMrkcOnlWR/DJfw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
buffer-equal-constant-time "1.0.1"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
ecdsa-sig-formatter "1.0.10"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
safe-buffer "^5.0.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
jwa@^1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/jwa/-/jwa-1.2.0.tgz#606da70c1c6d425cad329c77c99f2df2a981489a"
integrity sha512-Grku9ZST5NNQ3hqNUodSkDfEBqAmGA1R8yiyPHOnLzEKI0GaCQC/XhFmsheXYuXzFQJdILbh+lYBiliqG5R/Vg==
dependencies:
buffer-equal-constant-time "1.0.1"
ecdsa-sig-formatter "1.0.10"
safe-buffer "^5.0.1"
jws@^3.0.0, jws@^3.1.4, jws@^3.1.5:
version "3.2.1"
resolved "https://registry.yarnpkg.com/jws/-/jws-3.2.1.tgz#d79d4216a62c9afa0a3d5e8b5356d75abdeb2be5"
integrity sha512-bGA2omSrFUkd72dhh05bIAN832znP4wOU3lfuXtRBuGTbsmNmDXMQg28f0Vsxaxgk4myF5YkKQpz6qeRpMgX9g==
dependencies:
jwa "^1.2.0"
safe-buffer "^5.0.1"
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
jws@^3.1.3:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "3.1.5"
resolved "https://registry.yarnpkg.com/jws/-/jws-3.1.5.tgz#80d12d05b293d1e841e7cb8b4e69e561adcf834f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-GsCSexFADNQUr8T5HPJvayTjvPIfoyJPtLQBwn5a4WZQchcrPMPMAWcC1AzJVRDKyD6ZPROPAxgv6rfHViO4uQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
jwa "^1.1.5"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
safe-buffer "^5.0.1"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
karma-browserstack-launcher@^1.3.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/karma-browserstack-launcher/-/karma-browserstack-launcher-1.3.0.tgz#61fe3d36b1cf10681e40f9d874bf37271fb1c674"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-LrPf5sU/GISkEElWyoy06J8x0c8BcOjjOwf61Wqu6M0aWQu0Eoqm9yh3xON64/ByST/CEr0GsWiREQ/EIEMd4Q==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
browserstack "1.5.0"
browserstacktunnel-wrapper "~2.0.1"
q "~1.5.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
karma-chrome-launcher@2.2.0, karma-chrome-launcher@^2.2.0:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/karma-chrome-launcher/-/karma-chrome-launcher-2.2.0.tgz#cf1b9d07136cc18fe239327d24654c3dbc368acf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-uf/ZVpAabDBPvdPdveyk1EPgbnloPvFFGgmRhYLTDH7gEB4nZdSBk8yTU47w1g/drLSx5uMOkjKk7IWKfWg/+w==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
fs-access "^1.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
which "^1.2.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
karma-firefox-launcher@1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/karma-firefox-launcher/-/karma-firefox-launcher-1.1.0.tgz#2c47030452f04531eb7d13d4fc7669630bb93339"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-LbZ5/XlIXLeQ3cqnCbYLn+rOVhuMIK9aZwlP6eOLGzWdo1UVp7t6CN3DP4SafiRLjexKwHeKHDm0c38Mtd3VxA==
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
karma-jasmine@2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/karma-jasmine/-/karma-jasmine-2.0.1.tgz#26e3e31f2faf272dd80ebb0e1898914cc3a19763"
integrity sha512-iuC0hmr9b+SNn1DaUD2QEYtUxkS1J+bSJSn7ejdEexs7P8EYvA1CWkEdrDQ+8jVH3AgWlCNwjYsT1chjcNW9lA==
dependencies:
jasmine-core "^3.3"
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
test: run unit tests in random order (#19904) PR Close #19904
2018-07-06 02:13:25 -04:00
karma-jasmine@^1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/karma-jasmine/-/karma-jasmine-1.1.2.tgz#394f2b25ffb4a644b9ada6f22d443e2fd08886c3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-OU8rJf+0pkS5rabyLUQ+L9CIhsM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
karma-requirejs@1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/karma-requirejs/-/karma-requirejs-1.1.0.tgz#fddae2cb87d7ebc16fb0222893564d7fee578798"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-/driy4fX68FvsCIok1ZNf+5Xh5g=
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
karma-sauce-launcher@2.0.2, karma-sauce-launcher@^2.0.2:
build: update to latest karma-sauce-launcher version (#27634) PR Close #27634
2018-12-12 17:07:21 -05:00
version "2.0.2"
resolved "https://registry.yarnpkg.com/karma-sauce-launcher/-/karma-sauce-launcher-2.0.2.tgz#dbf98e70d86bf287b03a537cf637eb7aefa975c3"
integrity sha512-jLUFaJhHMcKpxFWUesyWYihzM5FvQiJsDwGcCtKeOy2lsWhkVw0V0Byqb1d+wU6myU1mribBtsIcub23HS4kWA==
dependencies:
sauce-connect-launcher "^1.2.4"
saucelabs "^1.5.0"
selenium-webdriver "^4.0.0-alpha.1"
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
karma-sourcemap-loader@0.3.7, karma-sourcemap-loader@^0.3.7:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "0.3.7"
resolved "https://registry.yarnpkg.com/karma-sourcemap-loader/-/karma-sourcemap-loader-0.3.7.tgz#91322c77f8f13d46fed062b042e1009d4c4505d8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-kTIsd/jxPUb+0GKwQuEAnUxFBdg=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
graceful-fs "^4.1.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
karma@^3.1.4:
version "3.1.4"
resolved "https://registry.yarnpkg.com/karma/-/karma-3.1.4.tgz#3890ca9722b10d1d14b726e1335931455788499e"
integrity sha512-31Vo8Qr5glN+dZEVIpnPCxEGleqE0EY6CtC2X9TagRV3rRQ3SNrvfhddICkJgUK3AgqpeKSZau03QumTGhGoSw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
bluebird "^3.3.0"
body-parser "^1.16.1"
chokidar "^2.0.3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
colors "^1.1.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
combine-lists "^1.0.0"
connect "^3.6.0"
core-js "^2.2.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
di "^0.0.1"
dom-serialize "^2.2.0"
expand-braces "^0.1.1"
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
flatted "^2.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
glob "^7.1.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
graceful-fs "^4.1.2"
http-proxy "^1.13.0"
isbinaryfile "^3.0.0"
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
lodash "^4.17.5"
log4js "^3.0.0"
mime "^2.3.1"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
minimatch "^3.0.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
optimist "^0.6.1"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
qjobs "^1.1.4"
range-parser "^1.2.0"
rimraf "^2.6.0"
safe-buffer "^5.0.1"
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
socket.io "2.1.1"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
source-map "^0.6.1"
tmp "0.0.33"
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
useragent "2.3.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
karma@~4.1.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/karma/-/karma-4.1.0.tgz#d07387c9743a575b40faf73e8a3eb5421c2193e1"
integrity sha512-xckiDqyNi512U4dXGOOSyLKPwek6X/vUizSy2f3geYevbLj+UIdvNwbn7IwfUIL2g1GXEPWt/87qFD1fBbl/Uw==
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
dependencies:
bluebird "^3.3.0"
body-parser "^1.16.1"
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
braces "^2.3.2"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
chokidar "^2.0.3"
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
colors "^1.1.0"
connect "^3.6.0"
core-js "^2.2.0"
di "^0.0.1"
dom-serialize "^2.2.0"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
flatted "^2.0.0"
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
glob "^7.1.1"
graceful-fs "^4.1.2"
http-proxy "^1.13.0"
isbinaryfile "^3.0.0"
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
lodash "^4.17.11"
log4js "^4.0.0"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
mime "^2.3.1"
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
minimatch "^3.0.2"
optimist "^0.6.1"
qjobs "^1.1.4"
range-parser "^1.2.0"
rimraf "^2.6.0"
safe-buffer "^5.0.1"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
socket.io "2.1.1"
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
source-map "^0.6.1"
tmp "0.0.33"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
useragent "2.3.0"
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
keyv@3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/keyv/-/keyv-3.0.0.tgz#44923ba39e68b12a7cec7df6c3268c031f2ef373"
integrity sha512-eguHnq22OE3uVoSYG0LVWNP+4ppamWr9+zWBe1bsNcovIMy6huUJFPgy4mGwCd/rnl3vOLGW1MTlu4c57CT1xA==
dependencies:
json-buffer "3.0.0"
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
kind-of@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-1.1.0.tgz#140a3d2d41a36d2efcfa9377b62c24f8495a5c44"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-FAo9LUGjbS78+pN3tiwk+ElaXEQ=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
kind-of@^3.0.2, kind-of@^3.0.3, kind-of@^3.2.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "3.2.2"
resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-3.2.2.tgz#31ea21a734bab9bbb0f32466d893aea51e4a3c64"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-buffer "^1.1.5"
kind-of@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-4.0.0.tgz#20813df3d712928b207378691a45066fae72dd57"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-IIE989cSkosgc3hpGkUGb65y3Vc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-buffer "^1.1.5"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
kind-of@^5.0.0:
version "5.1.0"
resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-5.1.0.tgz#729c91e2d857b7a419a1f9aa65685c4c33f5845d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-NGEErnH6F2vUuXDh+OlbcKW7/wOcfdRHaZ7VWtqCztfHri/++YKmP51OdWeGPuqCOba6kk2OTe5d02VmTB80Pw==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
kind-of@^6.0.0, kind-of@^6.0.2:
version "6.0.2"
resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-6.0.2.tgz#01146b36a6218e64e58f3a8d66de5d7fc6f6d051"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-s5kLOcnH0XqDO+FvuaLX8DDjZ18CGFk7VygH40QoKPUQhW4e2rvM0rwUq0t8IQDOwYSeLK01U90OjzBTme2QqA==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
klaw@^1.0.0:
version "1.3.1"
resolved "https://registry.yarnpkg.com/klaw/-/klaw-1.3.1.tgz#4088433b46b3b1ba259d78785d8e96f73ba02439"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-QIhDO0azsbolnXh4XY6W9zugJDk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
optionalDependencies:
graceful-fs "^4.1.9"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
latest-version@^3.0.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/latest-version/-/latest-version-3.1.0.tgz#a205383fea322b33b5ae3b18abee0dc2f356ee15"
integrity sha1-ogU4P+oyKzO1rjsYq+4NwvNW7hU=
dependencies:
package-json "^4.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lazy-cache@^1.0.3:
version "1.0.4"
resolved "https://registry.yarnpkg.com/lazy-cache/-/lazy-cache-1.0.4.tgz#a1d78fc3a50474cb80845d3b3b6e1da49a446e8e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-odePw6UEdMuAhF07O24dpJpEbo4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
lazystream@^1.0.0, lazystream@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/lazystream/-/lazystream-1.0.0.tgz#f6995fe0f820392f61396be89462407bb77168e4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-9plf4PggOS9hOWvolGJAe7dxaOQ=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
readable-stream "^2.0.5"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lcid@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/lcid/-/lcid-1.0.0.tgz#308accafa0bc483a3867b4b6f2b9506251d1b835"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-MIrMr6C8SDo4Z7S28rlQYlHRuDU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
invert-kv "^1.0.0"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
lcid@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/lcid/-/lcid-2.0.0.tgz#6ef5d2df60e52f82eb228a4c373e8d1f397253cf"
integrity sha512-avPEb8P8EGnwXKClwsNUgryVjllcRqtMYa49NTsbQagYuT1DcXnl1915oxWjoyGrXR6zH/Y0Zc96xWsPcoDKeA==
dependencies:
invert-kv "^2.0.0"
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
levn@~0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/levn/-/levn-0.3.0.tgz#3b09924edf9f083c0490fdd4c0bc4421e04764ee"
integrity sha1-OwmSTt+fCDwEkP3UwLxEIeBHZO4=
dependencies:
prelude-ls "~1.1.2"
type-check "~0.3.2"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
lie@~3.1.0:
version "3.1.1"
resolved "https://registry.yarnpkg.com/lie/-/lie-3.1.1.tgz#9a436b2cc7746ca59de7a41fa469b3efb76bd87e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-mkNrLMd0bKWd56QfpGmz77dr2H4=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
immediate "~3.0.5"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
liftoff@^2.1.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "2.5.0"
resolved "https://registry.yarnpkg.com/liftoff/-/liftoff-2.5.0.tgz#2009291bb31cea861bbf10a7c15a28caf75c31ec"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-IAkpG7Mc6oYbvxCnwVooyvdcMew=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
extend "^3.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
findup-sync "^2.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
fined "^1.0.1"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
flagged-respawn "^1.0.0"
is-plain-object "^2.0.4"
object.map "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
rechoir "^0.6.2"
resolve "^1.1.7"
livereload-js@^2.2.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "2.3.0"
resolved "https://registry.yarnpkg.com/livereload-js/-/livereload-js-2.3.0.tgz#c3ab22e8aaf5bf3505d80d098cbad67726548c9a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-j1R0/FeGa64Y+NmqfZhyoVRzcFlOZ8sNlKzHjh4VvLULFACZhn68XrX5DFg2FhMvSMJmROuFxRSa560ECWKBMg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
load-json-file@^1.0.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/load-json-file/-/load-json-file-1.1.0.tgz#956905708d58b4bab4c2261b04f59f31c99374c0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-lWkFcI1YtLq0wiYbBPWfMcmTdMA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
graceful-fs "^4.1.2"
parse-json "^2.2.0"
pify "^2.0.0"
pinkie-promise "^2.0.0"
strip-bom "^2.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
load-json-file@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/load-json-file/-/load-json-file-4.0.0.tgz#2f5f45ab91e33216234fd53adab668eb4ec0993b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-L19Fq5HjMhYjT9U62rZo607AmTs=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
graceful-fs "^4.1.2"
parse-json "^4.0.0"
pify "^3.0.0"
strip-bom "^3.0.0"
build: update version of Angular CLI and Build Optimizer used for tests (#28372) PR Close #28372
2019-01-25 11:33:22 -05:00
loader-utils@1.2.3:
version "1.2.3"
resolved "https://registry.yarnpkg.com/loader-utils/-/loader-utils-1.2.3.tgz#1ff5dc6911c9f0a062531a4c04b609406108c2c7"
integrity sha512-fkpz8ejdnEMG3s37wGL07iSBDg99O9D5yflE9RGNH3hRdx9SOwYfnGYdZOUIZitN8E+E2vkq3MUMYMvPYl5ZZA==
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
dependencies:
build: update version of Angular CLI and Build Optimizer used for tests (#28372) PR Close #28372
2019-01-25 11:33:22 -05:00
big.js "^5.2.2"
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
emojis-list "^2.0.0"
build: update version of Angular CLI and Build Optimizer used for tests (#28372) PR Close #28372
2019-01-25 11:33:22 -05:00
json5 "^1.0.1"
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
loader-utils@^0.2.11:
version "0.2.17"
resolved "https://registry.yarnpkg.com/loader-utils/-/loader-utils-0.2.17.tgz#f86e6374d43205a6e6c60e9196f17c0299bfb348"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+G5jdNQyBabmxg6RlvF8Apm/s0g=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
big.js "^3.1.3"
emojis-list "^2.0.0"
json5 "^0.5.0"
object-assign "^4.0.1"
locate-path@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/locate-path/-/locate-path-2.0.0.tgz#2b568b265eec944c6d9c0de9c3dbbbca0354cd8e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-K1aLJl7slExtnA3pw9u7ygNUzY4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
p-locate "^2.0.0"
path-exists "^3.0.0"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
locate-path@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/locate-path/-/locate-path-3.0.0.tgz#dbec3b3ab759758071b58fe59fc41871af21400e"
integrity sha512-7AO748wWnIhNqAuaty2ZWHkQHRSNfPVIsPIfwEOWO22AmaoVrWavlOcMR5nzTLNYvp36X220/maaRsrec1G65A==
dependencies:
p-locate "^3.0.0"
path-exists "^3.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash._basecopy@^3.0.0:
version "3.0.1"
resolved "https://registry.yarnpkg.com/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz#8da0e6a876cf344c0ad8a54882111dd3c5c7ca36"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-jaDmqHbPNEwK2KVIghEd08XHyjY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash._basetostring@^3.0.0:
version "3.0.1"
resolved "https://registry.yarnpkg.com/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz#d1861d877f824a52f669832dcaf3ee15566a07d5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-0YYdh3+CSlL2aYMtyvPuFVZqB9U=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash._basevalues@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz#5b775762802bde3d3297503e26300820fdf661b7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-W3dXYoAr3j0yl1A+JjAIIP32Ybc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash._getnative@^3.0.0:
version "3.9.1"
resolved "https://registry.yarnpkg.com/lodash._getnative/-/lodash._getnative-3.9.1.tgz#570bc7dede46d61cdcde687d65d3eecbaa3aaff5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-VwvH3t5G1hzc3mh9ZdPuy6o6r/U=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash._isiterateecall@^3.0.0:
version "3.0.9"
resolved "https://registry.yarnpkg.com/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz#5203ad7ba425fae842460e696db9cf3e6aac057c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-UgOte6Ql+uhCRg5pbbnPPmqsBXw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
lodash._isnative@~2.4.1:
version "2.4.1"
resolved "https://registry.yarnpkg.com/lodash._isnative/-/lodash._isnative-2.4.1.tgz#3ea6404b784a7be836c7b57580e1cdf79b14832c"
integrity sha1-PqZAS3hKe+g2x7V1gOHN95sUgyw=
lodash._objecttypes@~2.4.1:
version "2.4.1"
resolved "https://registry.yarnpkg.com/lodash._objecttypes/-/lodash._objecttypes-2.4.1.tgz#7c0b7f69d98a1f76529f890b0cdb1b4dfec11c11"
integrity sha1-fAt/admKH3ZSn4kLDNsbTf7BHBE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash._reescape@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/lodash._reescape/-/lodash._reescape-3.0.0.tgz#2b1d6f5dfe07c8a355753e5f27fac7f1cde1616a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Kx1vXf4HyKNVdT5fJ/rH8c3hYWo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash._reevaluate@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz#58bc74c40664953ae0b124d806996daca431e2ed"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-WLx0xAZklTrgsSTYBpltrKQx4u0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash._reinterpolate@^3.0.0, lodash._reinterpolate@~3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz#0ccf2d89166af03b3663c796538b75ac6e114d9d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-DM8tiRZq8Ds2Y8eWU4t1rG4RTZ0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash._root@^3.0.0:
version "3.0.1"
resolved "https://registry.yarnpkg.com/lodash._root/-/lodash._root-3.0.1.tgz#fba1c4524c19ee9a5f8136b4609f017cf4ded692"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+6HEUkwZ7ppfgTa0YJ8BfPTe1pI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
lodash._shimkeys@~2.4.1:
version "2.4.1"
resolved "https://registry.yarnpkg.com/lodash._shimkeys/-/lodash._shimkeys-2.4.1.tgz#6e9cc9666ff081f0b5a6c978b83e242e6949d203"
integrity sha1-bpzJZm/wgfC1psl4uD4kLmlJ0gM=
dependencies:
lodash._objecttypes "~2.4.1"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
lodash.debounce@^4.0.8:
version "4.0.8"
resolved "https://registry.yarnpkg.com/lodash.debounce/-/lodash.debounce-4.0.8.tgz#82d79bff30a67c4005ffd5e2515300ad9ca4d7af"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-gteb/zCmfEAF/9XiUVMArZyk168=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash.escape@^3.0.0:
version "3.2.0"
resolved "https://registry.yarnpkg.com/lodash.escape/-/lodash.escape-3.2.0.tgz#995ee0dc18c1b48cc92effae71a10aab5b487698"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-mV7g3BjBtIzJLv+ucaEKq1tIdpg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
lodash._root "^3.0.0"
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
lodash.get@^4.0.0:
version "4.4.2"
resolved "https://registry.yarnpkg.com/lodash.get/-/lodash.get-4.4.2.tgz#2d177f652fa31e939b4438d5341499dfa3825e99"
integrity sha1-LRd/ZS+jHpObRDjVNBSZ36OCXpk=
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
lodash.includes@^4.3.0:
version "4.3.0"
resolved "https://registry.yarnpkg.com/lodash.includes/-/lodash.includes-4.3.0.tgz#60bb98a87cb923c68ca1e51325483314849f553f"
integrity sha1-YLuYqHy5I8aMoeUTJUgzFISfVT8=
lodash.isarguments@2.4.x:
version "2.4.1"
resolved "https://registry.yarnpkg.com/lodash.isarguments/-/lodash.isarguments-2.4.1.tgz#4931a9c08253adf091ae7ca192258a973876ecca"
integrity sha1-STGpwIJTrfCRrnyhkiWKlzh27Mo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash.isarguments@^3.0.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/lodash.isarguments/-/lodash.isarguments-3.1.0.tgz#2f573d85c6a24289ff00663b491c1d338ff3458a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-L1c9hcaiQon/AGY7SRwdM4/zRYo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash.isarray@^3.0.0:
version "3.0.4"
resolved "https://registry.yarnpkg.com/lodash.isarray/-/lodash.isarray-3.0.4.tgz#79e4eb88c36a8122af86f844aa9bcd851b5fbb55"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-eeTriMNqgSKvhvhEqpvNhRtfu1U=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
lodash.isboolean@^3.0.3:
version "3.0.3"
resolved "https://registry.yarnpkg.com/lodash.isboolean/-/lodash.isboolean-3.0.3.tgz#6c2e171db2a257cd96802fd43b01b20d5f5870f6"
integrity sha1-bC4XHbKiV82WgC/UOwGyDV9YcPY=
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
lodash.isequal@^4.0.0:
version "4.5.0"
resolved "https://registry.yarnpkg.com/lodash.isequal/-/lodash.isequal-4.5.0.tgz#415c4478f2bcc30120c22ce10ed3226f7d3e18e0"
integrity sha1-QVxEePK8wwEgwizhDtMib30+GOA=
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
lodash.isinteger@^4.0.4:
version "4.0.4"
resolved "https://registry.yarnpkg.com/lodash.isinteger/-/lodash.isinteger-4.0.4.tgz#619c0af3d03f8b04c31f5882840b77b11cd68343"
integrity sha1-YZwK89A/iwTDH1iChAt3sRzWg0M=
lodash.isnumber@^3.0.3:
version "3.0.3"
resolved "https://registry.yarnpkg.com/lodash.isnumber/-/lodash.isnumber-3.0.3.tgz#3ce76810c5928d03352301ac287317f11c0b1ffc"
integrity sha1-POdoEMWSjQM1IwGsKHMX8RwLH/w=
lodash.isobject@^2.4.1, lodash.isobject@~2.4.1:
version "2.4.1"
resolved "https://registry.yarnpkg.com/lodash.isobject/-/lodash.isobject-2.4.1.tgz#5a2e47fe69953f1ee631a7eba1fe64d2d06558f5"
integrity sha1-Wi5H/mmVPx7mMafrof5k0tBlWPU=
dependencies:
lodash._objecttypes "~2.4.1"
lodash.isobject@^3.0.0:
version "3.0.2"
resolved "https://registry.yarnpkg.com/lodash.isobject/-/lodash.isobject-3.0.2.tgz#3c8fb8d5b5bf4bf90ae06e14f2a530a4ed935e1d"
integrity sha1-PI+41bW/S/kK4G4U8qUwpO2TXh0=
lodash.isplainobject@^4.0.6:
version "4.0.6"
resolved "https://registry.yarnpkg.com/lodash.isplainobject/-/lodash.isplainobject-4.0.6.tgz#7c526a52d89b45c45cc690b88163be0497f550cb"
integrity sha1-fFJqUtibRcRcxpC4gWO+BJf1UMs=
lodash.isstring@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/lodash.isstring/-/lodash.isstring-4.0.1.tgz#d527dfb5456eca7cc9bb95d5daeaf88ba54a5451"
integrity sha1-1SfftUVuynzJu5XV2ur4i6VKVFE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash.keys@^3.0.0:
version "3.1.2"
resolved "https://registry.yarnpkg.com/lodash.keys/-/lodash.keys-3.1.2.tgz#4dbc0472b156be50a0b286855d1bd0b0c656098a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-TbwEcrFWvlCgsoaFXRvQsMZWCYo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
lodash._getnative "^3.0.0"
lodash.isarguments "^3.0.0"
lodash.isarray "^3.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
lodash.keys@~2.4.1:
version "2.4.1"
resolved "https://registry.yarnpkg.com/lodash.keys/-/lodash.keys-2.4.1.tgz#48dea46df8ff7632b10d706b8acb26591e2b3727"
integrity sha1-SN6kbfj/djKxDXBrissmWR4rNyc=
dependencies:
lodash._isnative "~2.4.1"
lodash._shimkeys "~2.4.1"
lodash.isobject "~2.4.1"
lodash.merge@^4.6.0:
version "4.6.1"
resolved "https://registry.yarnpkg.com/lodash.merge/-/lodash.merge-4.6.1.tgz#adc25d9cb99b9391c59624f379fbba60d7111d54"
integrity sha512-AOYza4+Hf5z1/0Hztxpm2/xiPZgi/cjMqdnKTUWTBSKchJlxXXuUSxCCl8rJlf4g6yww/j6mA8nC8Hw/EZWxKQ==
lodash.noop@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/lodash.noop/-/lodash.noop-3.0.1.tgz#38188f4d650a3a474258439b96ec45b32617133c"
integrity sha1-OBiPTWUKOkdCWEObluxFsyYXEzw=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
lodash.once@^4.0.0:
version "4.1.1"
resolved "https://registry.yarnpkg.com/lodash.once/-/lodash.once-4.1.1.tgz#0dd3971213c7c56df880977d504c88fb471a97ac"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-DdOXEhPHxW34gJd9UEyI+0cal6w=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash.restparam@^3.0.0:
version "3.6.1"
resolved "https://registry.yarnpkg.com/lodash.restparam/-/lodash.restparam-3.6.1.tgz#936a4e309ef330a7645ed4145986c85ae5b20805"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-k2pOMJ7zMKdkXtQUWYbIWuWyCAU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash.template@^3.0.0:
version "3.6.2"
resolved "https://registry.yarnpkg.com/lodash.template/-/lodash.template-3.6.2.tgz#f8cdecc6169a255be9098ae8b0c53d378931d14f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+M3sxhaaJVvpCYrosMU9N4kx0U8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
lodash._basecopy "^3.0.0"
lodash._basetostring "^3.0.0"
lodash._basevalues "^3.0.0"
lodash._isiterateecall "^3.0.0"
lodash._reinterpolate "^3.0.0"
lodash.escape "^3.0.0"
lodash.keys "^3.0.0"
lodash.restparam "^3.0.0"
lodash.templatesettings "^3.0.0"
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
lodash.template@^4.0.2, lodash.template@^4.4.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "4.4.0"
resolved "https://registry.yarnpkg.com/lodash.template/-/lodash.template-4.4.0.tgz#e73a0385c8355591746e020b99679c690e68fba0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-5zoDhcg1VZF0bgILmWecaQ5o+6A=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
lodash._reinterpolate "~3.0.0"
lodash.templatesettings "^4.0.0"
lodash.templatesettings@^3.0.0:
version "3.1.1"
resolved "https://registry.yarnpkg.com/lodash.templatesettings/-/lodash.templatesettings-3.1.1.tgz#fb307844753b66b9f1afa54e262c745307dba8e5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+zB4RHU7Zrnxr6VOJix0UwfbqOU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
lodash._reinterpolate "^3.0.0"
lodash.escape "^3.0.0"
lodash.templatesettings@^4.0.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/lodash.templatesettings/-/lodash.templatesettings-4.1.0.tgz#2b4d4e95ba440d915ff08bc899e4553666713316"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-K01OlbpEDZFf8IvImeRVNmZxMxY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
lodash._reinterpolate "~3.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
lodash.values@^2.4.1:
version "2.4.1"
resolved "https://registry.yarnpkg.com/lodash.values/-/lodash.values-2.4.1.tgz#abf514436b3cb705001627978cbcf30b1280eea4"
integrity sha1-q/UUQ2s8twUAFieXjLzzCxKA7qQ=
dependencies:
lodash.keys "~2.4.1"
lodash@3.10.1, lodash@^3.10.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "3.10.1"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-3.10.1.tgz#5bf45e8e49ba4189e17d482789dfd15bd140b7b6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-W/Rejkm6QYnhfUgnid/RW9FAt7Y=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
lodash@4.11.1:
version "4.11.1"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.11.1.tgz#a32106eb8e2ec8e82c241611414773c9df15f8bc"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-oyEG644uyOgsJBYRQUdzyd8V+Lw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
lodash@4.17.5:
version "4.17.5"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.5.tgz#99a92d65c0272debe8c96b6057bc8fbfa3bed511"
integrity sha512-svL3uiZf1RwhH+cWrfZn3A4+U58wbP0tGVTLQPbjplZxZ8ROD9VLuNgsRniTlLe7OlSqR79RUehXgpBW/s0IQw==
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
lodash@^4.0.0, lodash@^4.14.0, lodash@^4.16.6, lodash@^4.2.1, lodash@^4.5.0, lodash@^4.8.0, lodash@~4.17.2:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "4.17.10"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.10.tgz#1b7793cf7259ea38fb3661d4d38b3260af8ae4e7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-UejweD1pDoXu+AD825lWwp4ZGtSwgnpZxb3JDViD7StjQz+Nb/6l093lx4OQ0foGWNRoc19mWy7BzL+UAK2iVg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
feat(bazel): update to the latest `@microsoft/api-extractor` (#32185) PR Close #32185
2019-08-19 05:55:34 -04:00
lodash@^4.17.10, lodash@^4.17.11, lodash@^4.17.4, lodash@^4.17.5, lodash@^4.3.0:
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
version "4.17.11"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.11.tgz#b39ea6229ef607ecd89e2c8df12536891cac9b8d"
integrity sha512-cQKh8igo5QUhZ7lg38DYWAxMvjSAKG0A8wGSVimP07SIUEK2UO+arSRKbRZWtelMtN5V0Hkwh5ryOto/SshYIg==
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
lodash@^4.17.14, lodash@~4.17.15:
version "4.17.15"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.15.tgz#b447f6670a0455bbfeedd11392eff330ea097548"
integrity sha512-8xOcRHvCjnocdS5cpwXQXVzmmh5e5+saE2QGoeQmbKmRS6J3VQppPOIt0MnmE+4xlZoumy0GPG0D0MVIQbNA1A==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lodash@~1.0.1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-1.0.2.tgz#8f57560c83b59fc270bd3d561b690043430e2551"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-j1dWDIO1n8JwvT1WG2kAQ0MOJVE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
lodash@~4.12.0:
version "4.12.0"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.12.0.tgz#2bd6dc46a040f59e686c972ed21d93dc59053258"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-K9bcRqBA9Z5obJcu0h2T3FkFMlg=
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
log-driver@1.2.7:
version "1.2.7"
resolved "https://registry.yarnpkg.com/log-driver/-/log-driver-1.2.7.tgz#63b95021f0702fedfa2c9bb0a24e7797d71871d8"
integrity sha512-U7KCmLdqsGHBLeWqYlFA0V0Sl6P08EE1ZrmA9cxjUE0WVqT9qnyVDPz1kzpFEP0jdJuFnasWIfSd7fsaNXkpbg==
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
log4js@^3.0.0:
version "3.0.6"
resolved "https://registry.yarnpkg.com/log4js/-/log4js-3.0.6.tgz#e6caced94967eeeb9ce399f9f8682a4b2b28c8ff"
integrity sha512-ezXZk6oPJCWL483zj64pNkMuY/NcRX5MPiB0zE6tjZM137aeusrOnW1ecxgF9cmwMWkBMhjteQxBPoZBh9FDxQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
circular-json "^0.5.5"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
date-format "^1.2.0"
debug "^3.1.0"
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
rfdc "^1.1.2"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
streamroller "0.7.0"
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
log4js@^4.0.0:
version "4.5.1"
resolved "https://registry.yarnpkg.com/log4js/-/log4js-4.5.1.tgz#e543625e97d9e6f3e6e7c9fc196dd6ab2cae30b5"
integrity sha512-EEEgFcE9bLgaYUKuozyFfytQM2wDHtXn4tAN41pkaxpNjAykv11GVdeI4tHtmPWW4Xrgh9R/2d7XYghDVjbKKw==
dependencies:
date-format "^2.0.0"
debug "^4.1.1"
flatted "^2.0.0"
rfdc "^1.1.4"
streamroller "^1.0.6"
build(bazel): update to nodejs rules 0.27.10 (#29694) PR Close #29694
2019-04-03 19:56:20 -04:00
long@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/long/-/long-4.0.0.tgz#9a7b71cfb7d361a194ea555241c92f7468d5bf28"
integrity sha512-XsP+KhQif4bjX1kbuSiySJFNAehNxgLb6hPRGJ9QsUr8ajHkuXGdrHmFUTUUXhDwVX2R5bY4JNZEwbUiMhV+MA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
longest@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/longest/-/longest-1.0.1.tgz#30a0b2da38f73770e8294a0d22e6625ed77d0097"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-MKCy2jj3N3DoKUoNIuZiXtd9AJc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
loud-rejection@^1.0.0:
version "1.6.0"
resolved "https://registry.yarnpkg.com/loud-rejection/-/loud-rejection-1.6.0.tgz#5b46f80147edee578870f086d04821cf998e551f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-W0b4AUft7leIcPCG0Eghz5mOVR8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
currently-unhandled "^0.4.1"
signal-exit "^3.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
lowercase-keys@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/lowercase-keys/-/lowercase-keys-1.0.0.tgz#4e3366b39e7f5457e35f1324bdf6f88d0bfc7306"
integrity sha1-TjNms55/VFfjXxMkvfb4jQv8cwY=
lowercase-keys@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/lowercase-keys/-/lowercase-keys-1.0.1.tgz#6f9e30b47084d971a7c820ff15a6c5167b74c26f"
integrity sha512-G2Lj61tXDnVFFOi8VZds+SoQjtQC3dgokKdDG2mTm1tx4m50NUHBOZSBwQQHyy0V12A0JTG4icfZQH+xPyh8VA==
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
lru-cache@2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.7.3"
resolved "https://registry.yarnpkg.com/lru-cache/-/lru-cache-2.7.3.tgz#6d4524e8b955f95d4f5b58851ce21dd72fb4e952"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-bUUk6LlV+V1PW1iFHOId1y+06VI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lru-cache@2.5.0:
version "2.5.0"
resolved "https://registry.yarnpkg.com/lru-cache/-/lru-cache-2.5.0.tgz#d82388ae9c960becbea0c73bb9eb79b6c6ce9aeb"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-2COIrpyWC+y+oMc7uet5tsbOmus=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
lru-cache@4.1.x, lru-cache@^4.0.1:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "4.1.3"
resolved "https://registry.yarnpkg.com/lru-cache/-/lru-cache-4.1.3.tgz#a1175cf3496dfc8436c156c334b4955992bce69c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-fFEhvcgzuIoJVUF8fYr5KR0YqxD238zgObTps31YdADwPPAp82a4M8TrckkWyx7ekNlf9aBcVn81cFwwXngrJA==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
pseudomap "^1.0.2"
yallist "^2.1.2"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
lru-cache@^4.1.2, lru-cache@^4.1.3:
version "4.1.5"
resolved "https://registry.yarnpkg.com/lru-cache/-/lru-cache-4.1.5.tgz#8bbe50ea85bed59bc9e33dcab8235ee9bcf443cd"
integrity sha512-sWZlbEP2OsHNkXrMl5GYk/jKk70MBng6UU4YI/qGDYbgf6YbP4EvmqISbXCoJiRKs+1bSpFHVgQxvJ17F2li5g==
dependencies:
pseudomap "^1.0.2"
yallist "^2.1.2"
lru-cache@^5.1.1:
version "5.1.1"
resolved "https://registry.yarnpkg.com/lru-cache/-/lru-cache-5.1.1.tgz#1da27e6710271947695daf6848e847f01d84b920"
integrity sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w==
dependencies:
yallist "^3.0.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
lru-queue@0.1:
version "0.1.0"
resolved "https://registry.yarnpkg.com/lru-queue/-/lru-queue-0.1.0.tgz#2738bd9f0d3cf4f84490c5736c48699ac632cda3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Jzi9nw089PhEkMVzbEhpmsYyzaM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
es5-ext "~0.10.2"
madge@0.5.0:
version "0.5.0"
resolved "https://registry.yarnpkg.com/madge/-/madge-0.5.0.tgz#4da1ba55ccde09bd7642a8e721fe6cbcea32c60f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-TaG6VczeCb12QqjnIf5svOoyxg8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
amdetective "0.0.2"
coffee-script "1.3.3"
colors "0.6.0-1"
commander "1.0.0"
commondir "0.0.1"
detective "0.1.1"
detective-es6 "1.1.0"
graphviz "0.0.7"
react-tools "0.12.1"
resolve "0.2.3"
uglify-js "1.2.6"
walkdir "0.0.5"
build: update @angular/cli version to 8.0.0-beta.13 (#29873) This commit updates the version of @angular/cli to the recently pushed 8.0.0-beta.13. This is necessary as the CI has started to fail with a module hoisting issue caused by a relative import in the CLI, which is fixed in the latest (emergency) release. PR Close #29873
2019-04-12 18:51:39 -04:00
magic-string@0.25.2, magic-string@^0.25.1:
version "0.25.2"
resolved "https://registry.yarnpkg.com/magic-string/-/magic-string-0.25.2.tgz#139c3a729515ec55e96e69e82a11fe890a293ad9"
integrity sha512-iLs9mPjh9IuTtRsqqhNGYcZXGei0Nh/A4xirrsqW7c+QhKVFL2vm7U09ru6cHRD22azaP/wMDgI+HCqbETMTtg==
dependencies:
sourcemap-codec "^1.4.4"
build: add dependencies to be used by ngcc (#24897) PR Close #24897
2018-07-16 02:08:48 -04:00
magic-string@^0.25.0:
version "0.25.0"
resolved "https://registry.yarnpkg.com/magic-string/-/magic-string-0.25.0.tgz#1f3696f9931ff0a1ed4c132250529e19cad6759b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-Msbwa9oNYNPjwVh9ury5X2BHbTFWoirTlzuf4X+pIoSOQVKNRJHXTx1WmKYuXzRM4QZFv8dGXyZvhDMmWhGLPw==
build: add dependencies to be used by ngcc (#24897) PR Close #24897
2018-07-16 02:08:48 -04:00
dependencies:
sourcemap-codec "^1.4.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
make-dir@^1.0.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/make-dir/-/make-dir-1.3.0.tgz#79c1033b80515bd6d24ec9933e860ca75ee27f0c"
integrity sha512-2w31R7SJtieJJnQtGc7RVL2StM2vGYVfqUOvUDxH6bC6aJTxPxTF0GnIgCyu7tjockiUWAYQRbxa7vKn34s5sQ==
dependencies:
pify "^3.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
make-fetch-happen@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/make-fetch-happen/-/make-fetch-happen-4.0.1.tgz#141497cb878f243ba93136c83d8aba12c216c083"
integrity sha512-7R5ivfy9ilRJ1EMKIOziwrns9fGeAD4bAha8EB7BIiBBLHm2KeTUGCrICFt2rbHfzheTLynv50GnNTK1zDTrcQ==
dependencies:
agentkeepalive "^3.4.1"
cacache "^11.0.1"
http-cache-semantics "^3.8.1"
http-proxy-agent "^2.1.0"
https-proxy-agent "^2.2.1"
lru-cache "^4.1.2"
mississippi "^3.0.0"
node-fetch-npm "^2.0.2"
promise-retry "^1.1.1"
socks-proxy-agent "^4.0.0"
ssri "^6.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
make-iterator@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/make-iterator/-/make-iterator-1.0.1.tgz#29b33f312aa8f547c4a5e490f56afcec99133ad6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-pxiuXh0iVEq7VM7KMIhs5gxsfxCux2URptUQaXo4iZZJxBAzTPOLE2BumO5dbfVYq/hBJFBR/a1mFDmOx5AGmw==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
kind-of "^6.0.2"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
map-age-cleaner@^0.1.1:
version "0.1.3"
resolved "https://registry.yarnpkg.com/map-age-cleaner/-/map-age-cleaner-0.1.3.tgz#7d583a7306434c055fe474b0f45078e6e1b4b92a"
integrity sha512-bJzx6nMoP6PDLPBFmg7+xRKeFZvFboMrGlxmNj9ClvX53KrmvM5bXFXEWjbz4cz1AFn+jWJ9z/DJSz7hrs0w3w==
dependencies:
p-defer "^1.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
map-cache@^0.2.0, map-cache@^0.2.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.2.2"
resolved "https://registry.yarnpkg.com/map-cache/-/map-cache-0.2.2.tgz#c32abd0bd6525d9b051645bb4f26ac5dc98a0dbf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wyq9C9ZSXZsFFkW7TyasXcmKDb8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
map-obj@^1.0.0, map-obj@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/map-obj/-/map-obj-1.0.1.tgz#d933ceb9205d82bdcf4886f6742bdc2b4dea146d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-2TPOuSBdgr3PSIb2dCvcK03qFG0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
map-obj@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/map-obj/-/map-obj-2.0.0.tgz#a65cd29087a92598b8791257a523e021222ac1f9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-plzSkIepJZi4eRJXpSPgISIqwfk=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
map-stream@~0.0.7:
version "0.0.7"
resolved "https://registry.yarnpkg.com/map-stream/-/map-stream-0.0.7.tgz#8a1f07896d82b10926bd3744a2420009f88974a8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ih8HiW2CsQkmvTdEokIACfiJdKg=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
map-stream@~0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/map-stream/-/map-stream-0.1.0.tgz#e56aa94c4c8055a16404a0674b78f215f7c8e194"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-5WqpTEyAVaFkBKBnS3jyFffI4ZQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
map-visit@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/map-visit/-/map-visit-1.0.0.tgz#ecdca8f13144e660f1b5bd41f12f3479d98dfb8f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-7Nyo8TFE5mDxtb1B8S80edmN+48=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
object-visit "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"match-stream@>= 0.0.2 < 1":
version "0.0.2"
resolved "https://registry.yarnpkg.com/match-stream/-/match-stream-0.0.2.tgz#99eb050093b34dffade421b9ac0b410a9cfa17cf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-mesFAJOzTf+t5CG5rAtBCpz6F88=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
buffers "~0.1.1"
readable-stream "~1.0.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 06:33:17 -05:00
materialize-css@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/materialize-css/-/materialize-css-1.0.0.tgz#8d5db1c4a81c6d65f3b2e2ca83a8e08daa24d1be"
integrity sha512-4/oecXl8y/1i8RDZvyvwAICyqwNoKU4or5uf8uoAd74k76KzZ0Llym4zhJ5lLNUskcqjO0AuMcvNyDkpz8Z6zw==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
math-random@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/math-random/-/math-random-1.0.1.tgz#8b3aac588b8a66e4975e3cdea67f7bb329601fac"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-izqsWIuKZuSXXjzepn97sylgH6w=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
media-typer@0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/media-typer/-/media-typer-0.3.0.tgz#8710d7af0aa626f8fffa1ce00168545263255748"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-hxDXrwqmJvj/+hzgAWhUUmMlV0g=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
mem@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/mem/-/mem-1.1.0.tgz#5edd52b485ca1d900fe64895505399a0dfa45f76"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Xt1StIXKHZAP5kiVUFOZoN+kX3Y=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
mimic-fn "^1.0.0"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
mem@^4.0.0:
version "4.3.0"
resolved "https://registry.yarnpkg.com/mem/-/mem-4.3.0.tgz#461af497bc4ae09608cdb2e60eefb69bff744178"
integrity sha512-qX2bG48pTqYRVmDB37rn/6PT7LcR8T7oAX3bf99u1Tt1nzxYfxkgqDwUwolPlXweM0XzBOBFzSx4kfp7KP1s/w==
dependencies:
map-age-cleaner "^0.1.1"
mimic-fn "^2.0.0"
p-is-promise "^2.0.0"
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
memoizeasync@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/memoizeasync/-/memoizeasync-1.1.0.tgz#9d7028a6f266deb733510bb7dbba5f51878c561e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nXAopvJm3rczUQu327pfUYeMVh4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
lru-cache "2.5.0"
passerror "1.1.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
memoizee@^0.4.14:
version "0.4.14"
resolved "https://registry.yarnpkg.com/memoizee/-/memoizee-0.4.14.tgz#07a00f204699f9a95c2d9e77218271c7cd610d57"
integrity sha512-/SWFvWegAIYAO4NQMpcX+gcra0yEZu4OntmUdrBaWrJncxOqAziGFlHxc7yjKVK2uu3lpPW27P27wkR82wA8mg==
dependencies:
d "1"
es5-ext "^0.10.45"
es6-weak-map "^2.0.2"
event-emitter "^0.3.5"
is-promise "^2.1"
lru-queue "0.1"
next-tick "1"
timers-ext "^0.1.5"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
memoizee@^0.4.3:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.4.12"
resolved "https://registry.yarnpkg.com/memoizee/-/memoizee-0.4.12.tgz#780e99a219c50c549be6d0fc61765080975c58fb"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-sprBu6nwxBWBvBOh5v2jcsGqiGLlL2xr2dLub3vR8dnE8YB17omwtm/0NSHl8jjNbcsJd5GMWJAnTSVe/O0Wfg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
d "1"
es5-ext "^0.10.30"
es6-weak-map "^2.0.2"
event-emitter "^0.3.5"
is-promise "^2.1"
lru-queue "0.1"
next-tick "1"
timers-ext "^0.1.2"
memory-fs@^0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/memory-fs/-/memory-fs-0.2.0.tgz#f2bb25368bc121e391c2520de92969caee0a0290"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8rslNovBIeORwlIN6Slpyu4KApA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
memory-fs@~0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/memory-fs/-/memory-fs-0.3.0.tgz#7bcc6b629e3a43e871d7e29aca6ae8a7f15cbb20"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-e8xrYp46Q+hx1+Kaymrop/FcuyA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
errno "^0.1.3"
readable-stream "^2.0.1"
meow@^3.3.0:
version "3.7.0"
resolved "https://registry.yarnpkg.com/meow/-/meow-3.7.0.tgz#72cb668b425228290abbfa856892587308a801fb"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-cstmi0JSKCkKu/qFaJJYcwioAfs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
camelcase-keys "^2.0.0"
decamelize "^1.1.2"
loud-rejection "^1.0.0"
map-obj "^1.0.1"
minimist "^1.1.3"
normalize-package-data "^2.3.4"
object-assign "^4.0.1"
read-pkg-up "^1.0.1"
redent "^1.0.0"
trim-newlines "^1.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
meow@^4.0.0:
version "4.0.1"
resolved "https://registry.yarnpkg.com/meow/-/meow-4.0.1.tgz#d48598f6f4b1472f35bf6317a95945ace347f975"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-xcSBHD5Z86zaOc+781KrupuHAzeGXSLtiAOmBsiLDiPSaYSB6hdew2ng9EBAnZ62jagG9MHAOdxpDi/lWBFJ/A==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
camelcase-keys "^4.0.0"
decamelize-keys "^1.0.0"
loud-rejection "^1.0.0"
minimist "^1.1.3"
minimist-options "^3.0.1"
normalize-package-data "^2.3.4"
read-pkg-up "^3.0.0"
redent "^2.0.0"
trim-newlines "^2.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
merge-descriptors@1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/merge-descriptors/-/merge-descriptors-1.0.1.tgz#b00aaa556dd8b44568150ec9d1b953f3f90cbb61"
integrity sha1-sAqqVW3YtEVoFQ7J0blT8/kMu2E=
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
merge-stream@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/merge-stream/-/merge-stream-1.0.1.tgz#4041202d508a342ba00174008df0c251b8c135e1"
integrity sha1-QEEgLVCKNCugAXQAjfDCUbjBNeE=
dependencies:
readable-stream "^2.0.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
methmeth@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/methmeth/-/methmeth-1.1.0.tgz#e80a26618e52f5c4222861bb748510bd10e29089"
integrity sha1-6AomYY5S9cQiKGG7dIUQvRDikIk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
method-override@~2.3.5:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "2.3.10"
resolved "https://registry.yarnpkg.com/method-override/-/method-override-2.3.10.tgz#e3daf8d5dee10dd2dce7d4ae88d62bbee77476b4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-49r41d7hDdLc59SuiNYrvud0drQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
debug "2.6.9"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
methods "~1.1.2"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
parseurl "~1.3.2"
vary "~1.1.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
methods@~1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/methods/-/methods-1.1.2.tgz#5529a4d67654134edcc5266656835b0f851afcee"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-VSmk1nZUE07cxSZmVoNbD4Ua/O4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
micromatch@^2.1.5, micromatch@^2.3.11:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.3.11"
resolved "https://registry.yarnpkg.com/micromatch/-/micromatch-2.3.11.tgz#86677c97d1720b363431d04d0d15293bd38c1565"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-hmd8l9FyCzY0MdBNDRUpO9OMFWU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
arr-diff "^2.0.0"
array-unique "^0.2.1"
braces "^1.8.2"
expand-brackets "^0.1.4"
extglob "^0.3.1"
filename-regex "^2.0.0"
is-extglob "^1.0.0"
is-glob "^2.0.1"
kind-of "^3.0.2"
normalize-path "^2.0.1"
object.omit "^2.0.0"
parse-glob "^3.0.4"
regex-cache "^0.4.2"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
micromatch@^3.0.4, micromatch@^3.1.10, micromatch@^3.1.4:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "3.1.10"
resolved "https://registry.yarnpkg.com/micromatch/-/micromatch-3.1.10.tgz#70859bc95c9840952f359a068a3fc49f9ecfac23"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-MWikgl9n9M3w+bpsY3He8L+w9eF9338xRl8IAO5viDizwSzziFEyUzo2xrrloB64ADbTf8uA8vRqqttDTOmccg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
arr-diff "^4.0.0"
array-unique "^0.3.2"
braces "^2.3.1"
define-property "^2.0.2"
extend-shallow "^3.0.2"
extglob "^2.0.4"
fragment-cache "^0.2.1"
kind-of "^6.0.2"
nanomatch "^1.2.9"
object.pick "^1.3.0"
regex-not "^1.0.0"
snapdragon "^0.8.1"
to-regex "^3.0.2"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
"mime-db@>= 1.34.0 < 2":
version "1.34.0"
resolved "https://registry.yarnpkg.com/mime-db/-/mime-db-1.34.0.tgz#452d0ecff5c30346a6dc1e64b1eaee0d3719ff9a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-RS0Oz/XDA0am3B5kseruDTcZ/5o=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
"mime-db@>= 1.36.0 < 2":
version "1.38.0"
resolved "https://registry.yarnpkg.com/mime-db/-/mime-db-1.38.0.tgz#1a2aab16da9eb167b49c6e4df2d9c68d63d8e2ad"
integrity sha512-bqVioMFFzc2awcdJZIzR3HjZFX20QhilVS7hytkKrv7xFAn8bM1gzc/FOX2awLISvWe0PV8ptFKcon+wZ5qYkg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
mime-db@~1.33.0:
version "1.33.0"
resolved "https://registry.yarnpkg.com/mime-db/-/mime-db-1.33.0.tgz#a3492050a5cb9b63450541e39d9788d2272783db"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-BHJ/EKruNIqJf/QahvxwQZXKygOQ256myeN/Ew+THcAa5q+PjyTTMMeNQC4DZw5AwfvelsUrA6B67NKMqXDbzQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
mime-db@~1.37.0:
version "1.37.0"
resolved "https://registry.yarnpkg.com/mime-db/-/mime-db-1.37.0.tgz#0b6a0ce6fdbe9576e25f1f2d2fde8830dc0ad0d8"
integrity sha512-R3C4db6bgQhlIhPU48fUtdVmKnflq+hRdad7IyKhtFj06VPNVdk2RhiYL3UjQIlso8L+YxAtFkobT0VK+S/ybg==
mime-types@^2.0.8, mime-types@^2.1.16, mime-types@~2.1.19:
version "2.1.21"
resolved "https://registry.yarnpkg.com/mime-types/-/mime-types-2.1.21.tgz#28995aa1ecb770742fe6ae7e58f9181c744b3f96"
integrity sha512-3iL6DbwpyLzjR3xHSFNFeb9Nz/M8WDkX33t1GFQnFOllWk8pOrh/LSrB5OXlnlW5P9LH73X6loW/eogc+F5lJg==
dependencies:
mime-db "~1.37.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
mime-types@^2.1.11, mime-types@^2.1.12, mime-types@~2.1.17, mime-types@~2.1.18, mime-types@~2.1.6, mime-types@~2.1.7, mime-types@~2.1.9:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "2.1.18"
resolved "https://registry.yarnpkg.com/mime-types/-/mime-types-2.1.18.tgz#6f323f60a83d11146f831ff11fd66e2fe5503bb8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-lc/aahn+t4/SWV/qcmumYjymLsWfN3ELhpmVuUFjgsORruuZPVSwAQryq+HHGvO/SI2KVX26bx+En+zhM8g8hQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
mime-db "~1.33.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
mime@1.3.4:
version "1.3.4"
resolved "https://registry.yarnpkg.com/mime/-/mime-1.3.4.tgz#115f9e3b6b3daf2959983cb38f149a2d40eb5d53"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-EV+eO2s9rylZmDyzjxSaLUDrXVM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
mime@1.4.1:
version "1.4.1"
resolved "https://registry.yarnpkg.com/mime/-/mime-1.4.1.tgz#121f9ebc49e3766f311a76e1fa1c8003c4b03aa6"
integrity sha512-KI1+qOZu5DcW6wayYHSzR/tXKCDC5Om4s1z2QJjDULzLcmf3DvzS7oluY4HCTrc+9FiKmWUgeNLg7W3uIQvxtQ==
build: update to rules_nodejs 0.38 (#32889) PR Close #32889
2019-09-27 18:49:59 -04:00
mime@^1.4.1, mime@^1.6.0:
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
version "1.6.0"
resolved "https://registry.yarnpkg.com/mime/-/mime-1.6.0.tgz#32cd9e5c64553bd58d19a568af452acff04981b1"
integrity sha512-x0Vn8spI+wuJ1O6S7gnbaQg8Pxh4NNHb7KSINmEWKiPE4RKOplvijn+NkmYmmRgP68mc70j2EbeTFRsrswaQeg==
mime@^2.2.0, mime@^2.3.1:
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
version "2.4.0"
resolved "https://registry.yarnpkg.com/mime/-/mime-2.4.0.tgz#e051fd881358585f3279df333fe694da0bcffdd6"
integrity sha512-ikBcWwyqXQSHKtciCcctu9YfPbFYZ4+gbHEmE0Q8jzcTYQg5dHCr3g2wwAZjPoJfQVXZq6KXAjpXOTf5/cjT7w==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
mimic-fn@^1.0.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/mimic-fn/-/mimic-fn-1.2.0.tgz#820c86a39334640e99516928bd03fca88057d022"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-jf84uxzwiuiIVKiOLpfYk7N46TSy8ubTonmneY9vrpHNAnp0QBt2BxWV9dO3/j+BoVAb+a5G6YDPW3M5HOdMWQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
mimic-fn@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/mimic-fn/-/mimic-fn-2.1.0.tgz#7ed2c2ccccaf84d3ffcb7a69b57711fc2083401b"
integrity sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg==
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
mimic-response@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/mimic-response/-/mimic-response-1.0.1.tgz#4923538878eef42063cb8a3e3b0798781487ab1b"
integrity sha512-j5EctnkH7amfV/q5Hgmoal1g2QHFJRraOtmx0JpIqkxhBhI/lJSl1nMpQ45hVarwNETOoWEimndZ4QK0RHxuxQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"minimatch@2 || 3", minimatch@^3.0.0, minimatch@^3.0.2, minimatch@^3.0.4:
version "3.0.4"
resolved "https://registry.yarnpkg.com/minimatch/-/minimatch-3.0.4.tgz#5166e286457f03306064be5497e8dbb0c3d32083"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-yJHVQEhyqPLUTgt9B83PXu6W3rx4MvvHvSUvToogpwoGDOUQ+yDrR0HRot+yOCdCO7u4hX3pWft6kWBBcqh0UA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
brace-expansion "^1.1.7"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
minimatch@3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/minimatch/-/minimatch-3.0.2.tgz#0f398a7300ea441e9c348c83d98ab8c9dbf9c40a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-DzmKcwDqRB6cNIyD2Yq4ydv5xAo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
brace-expansion "^1.0.0"
minimatch@^2.0.1:
version "2.0.10"
resolved "https://registry.yarnpkg.com/minimatch/-/minimatch-2.0.10.tgz#8d087c39c6b38c001b97fca7ce6d0e1e80afbac7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-jQh8OcazjAAbl/ynzm0OHoCvusc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
brace-expansion "^1.0.0"
minimatch@~0.2.11:
version "0.2.14"
resolved "https://registry.yarnpkg.com/minimatch/-/minimatch-0.2.14.tgz#c74e780574f63c6f9a090e90efbe6ef53a6a756a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-x054BXT2PG+aCQ6Q775u9TpqdWo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
lru-cache "2"
sigmund "~1.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
minimist-options@^3.0.1:
version "3.0.2"
resolved "https://registry.yarnpkg.com/minimist-options/-/minimist-options-3.0.2.tgz#fba4c8191339e13ecf4d61beb03f070103f3d954"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-FyBrT/d0d4+uiZRbqznPXqw3IpZZG3gl3wKWiX784FycUKVwBt0uLBFkQrtE4tZOrgo78nZp2jnKz3L65T5LdQ==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
arrify "^1.0.1"
is-plain-obj "^1.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
minimist@0.0.8:
version "0.0.8"
resolved "https://registry.yarnpkg.com/minimist/-/minimist-0.0.8.tgz#857fcabfc3397d2625b8228262e86aa7a011b05d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-hX/Kv8M5fSYluCKCYuhqp6ARsF0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
minimist@1.2.0, minimist@^1.1.0, minimist@^1.1.1, minimist@^1.1.3, minimist@^1.2.0, minimist@~1.2.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/minimist/-/minimist-1.2.0.tgz#a35008b20f41383eec1fb914f4cd5df79a264284"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-o1AIsg9BOD7sH7kU9M1d95omQoQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
minimist@~0.0.1:
version "0.0.10"
resolved "https://registry.yarnpkg.com/minimist/-/minimist-0.0.10.tgz#de3f98543dbf96082be48ad1a0c7cda836301dcf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-3j+YVD2/lggr5IrRoMfNqDYwHc8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
minipass@^2.2.1, minipass@^2.3.4, minipass@^2.3.5:
version "2.3.5"
resolved "https://registry.yarnpkg.com/minipass/-/minipass-2.3.5.tgz#cacebe492022497f656b0f0f51e2682a9ed2d848"
integrity sha512-Gi1W4k059gyRbyVUZQ4mEqLm0YIUiGYfvxhF6SIlk3ui1WVxMTGfGdQ2SInh3PDrRTVvPKgULkpJtT4RH10+VA==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
safe-buffer "^5.1.2"
yallist "^3.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
minizlib@^1.1.1:
version "1.2.1"
resolved "https://registry.yarnpkg.com/minizlib/-/minizlib-1.2.1.tgz#dd27ea6136243c7c880684e8672bb3a45fd9b614"
integrity sha512-7+4oTUOWKg7AuL3vloEWekXY2/D20cevzsrNT2kGWm+39J9hGTCBv8VI5Pm5lXZ/o3/mdR4f8rflAPhnQb8mPA==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
minipass "^2.2.1"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
mississippi@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/mississippi/-/mississippi-3.0.0.tgz#ea0a3291f97e0b5e8776b363d5f0a12d94c67022"
integrity sha512-x471SsVjUtBRtcvd4BzKE9kFC+/2TeWgKCgw0bZcw1b9l2X3QX5vCWgF+KaZaYm87Ss//rHnWryupDrgLvmSkA==
dependencies:
concat-stream "^1.5.0"
duplexify "^3.4.2"
end-of-stream "^1.1.0"
flush-write-stream "^1.0.0"
from2 "^2.1.0"
parallel-transform "^1.1.0"
pump "^3.0.0"
pumpify "^1.3.3"
stream-each "^1.1.0"
through2 "^2.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
mixin-deep@^1.2.0:
version "1.3.1"
resolved "https://registry.yarnpkg.com/mixin-deep/-/mixin-deep-1.3.1.tgz#a49e7268dce1a0d9698e45326c5626df3543d0fe"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-8ZItLHeEgaqEvd5lYBXfm4EZSFCX29Jb9K+lAHhDKzReKBQKj3R+7NOF6tjqYi9t4oI8VUfaWITJQm86wnXGNQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
for-in "^1.0.2"
is-extendable "^1.0.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
mkdirp@0.5, mkdirp@0.5.x, mkdirp@0.x.x, mkdirp@^0.5.0, mkdirp@^0.5.1, mkdirp@~0.5.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.5.1"
resolved "https://registry.yarnpkg.com/mkdirp/-/mkdirp-0.5.1.tgz#30057438eac6cf7f8c4767f38648d6697d75c903"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-MAV0OOrGz3+MR2fzhkjWaX11yQM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
minimist "0.0.8"
mkdirp@0.5.0:
version "0.5.0"
resolved "https://registry.yarnpkg.com/mkdirp/-/mkdirp-0.5.0.tgz#1d73076a6df986cd9344e15e71fcc05a4c9abf12"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-HXMHam35hs2TROFecfzAWkyavxI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
minimist "0.0.8"
mkpath@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/mkpath/-/mkpath-0.1.0.tgz#7554a6f8d871834cc97b5462b122c4c124d6de91"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-dVSm+Nhxg0zJe1RisSLEwSTW3pE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
modelo@^4.2.0:
version "4.2.3"
resolved "https://registry.yarnpkg.com/modelo/-/modelo-4.2.3.tgz#b278588a4db87fc1e5107ae3a277c0876f38d894"
integrity sha512-9DITV2YEMcw7XojdfvGl3gDD8J9QjZTJ7ZOUuSAkP+F3T6rDbzMJuPktxptsdHYEvZcmXrCD3LMOhdSAEq6zKA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
modify-values@^1.0.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/modify-values/-/modify-values-1.0.1.tgz#b3939fa605546474e3e3e3c63d64bd43b4ee6022"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-xV2bxeN6F7oYjZWTe/YPAy6MN2M+sL4u/Rlm2AHCIVGfo2p1yGmBHQ6vHehl4bRTZBdHu3TSkWdYgkwpYzAGSw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
moment@2.x.x:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "2.22.2"
resolved "https://registry.yarnpkg.com/moment/-/moment-2.22.2.tgz#3c257f9839fc0e93ff53149632239eb90783ff66"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-PCV/mDn8DpP/UxSWMiOeuQeD/2Y=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
morgan@^1.8.2:
version "1.9.1"
resolved "https://registry.yarnpkg.com/morgan/-/morgan-1.9.1.tgz#0a8d16734a1d9afbc824b99df87e738e58e2da59"
integrity sha512-HQStPIV4y3afTiCYVxirakhlCfGkI161c76kKFca7Fk1JusM//Qeo1ej2XaMniiNeaZklMVrh3vTtIzpzwbpmA==
dependencies:
basic-auth "~2.0.0"
debug "2.6.9"
depd "~1.1.2"
on-finished "~2.3.0"
on-headers "~1.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
morgan@~1.6.1:
version "1.6.1"
resolved "https://registry.yarnpkg.com/morgan/-/morgan-1.6.1.tgz#5fd818398c6819cba28a7cd6664f292fe1c0bbf2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-X9gYOYxoGcuiinzWZk8pL+HAu/I=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
basic-auth "~1.0.3"
debug "~2.2.0"
depd "~1.0.1"
on-finished "~2.3.0"
on-headers "~1.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
move-concurrently@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/move-concurrently/-/move-concurrently-1.0.1.tgz#be2c005fda32e0b29af1f05d7c4b33214c701f92"
integrity sha1-viwAX9oy4LKa8fBdfEszIUxwH5I=
dependencies:
aproba "^1.1.1"
copy-concurrently "^1.0.0"
fs-write-stream-atomic "^1.0.8"
mkdirp "^0.5.1"
rimraf "^2.5.4"
run-queue "^1.0.3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
mozilla-toolkit-versioning@0.0.2:
version "0.0.2"
resolved "https://registry.yarnpkg.com/mozilla-toolkit-versioning/-/mozilla-toolkit-versioning-0.0.2.tgz#90590e05d48dfdc35b63a22d0233a6cae7c277ff"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-kFkOBdSN/cNbY6ItAjOmyufCd/8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
mozilla-version-comparator@1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/mozilla-version-comparator/-/mozilla-version-comparator-1.0.2.tgz#f86731e70c15d1ff5eb288d13b4db8d1e605f7fc"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+Gcx5wwV0f9esojRO0240eYF9/w=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ms@0.7.1:
version "0.7.1"
resolved "https://registry.yarnpkg.com/ms/-/ms-0.7.1.tgz#9cd13c03adbff25b65effde7ce864ee952017098"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nNE8A62/8ltl7/3nzoZO6VIBcJg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ms@0.7.2:
version "0.7.2"
resolved "https://registry.yarnpkg.com/ms/-/ms-0.7.2.tgz#ae25cf2512b3885a1d95d7f037868d8431124765"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-riXPJRKziFodldfwN4aNhDESR2U=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
ms@2.0.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.0.0"
resolved "https://registry.yarnpkg.com/ms/-/ms-2.0.0.tgz#5608aeadfc00be6c2901df5f9861788de0d597c8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-VgiurfwAvmwpAd9fmGF4jeDVl8g=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ms@^0.7.1:
version "0.7.3"
resolved "https://registry.yarnpkg.com/ms/-/ms-0.7.3.tgz#708155a5e44e33f5fd0fc53e81d0d40a91be1fff"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-cIFVpeROM/X9D8U+gdDUCpG+H/8=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
ms@^2.0.0, ms@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/ms/-/ms-2.1.1.tgz#30a5864eb3ebb0a66f2ebe6d727af06a09d86e0a"
integrity sha512-tgp+dl5cGk28utYktBsrFqA7HKgrhgPsg6Z/EfhWI4gl1Hwq8B/GmY/0oXZ6nF8hDVesS/FpnYaD/kOWhYQvyg==
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
multimatch@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/multimatch/-/multimatch-2.1.0.tgz#9c7906a22fb4c02919e2f5f75161b4cdbd4b2a2b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nHkGoi+0wCkZ4vX3UWG0zb1LKis=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
array-differ "^1.0.0"
array-union "^1.0.1"
arrify "^1.0.0"
minimatch "^3.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
multiparty@3.3.2:
version "3.3.2"
resolved "https://registry.yarnpkg.com/multiparty/-/multiparty-3.3.2.tgz#35de6804dc19643e5249f3d3e3bdc6c8ce301d3f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Nd5oBNwZZD5SSfPT473GyM4wHT8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
readable-stream "~1.1.9"
stream-counter "~0.2.0"
multipipe@^0.1.2:
version "0.1.2"
resolved "https://registry.yarnpkg.com/multipipe/-/multipipe-0.1.2.tgz#2a8f2ddf70eed564dff2d57f1e1a137d9f05078b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Ko8t33Du1WTf8tV/HhoTfZ8FB4s=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
duplexer2 "0.0.2"
feat(elements): add support for creating custom elements (#22413) PR Close #22413
2018-02-28 12:45:11 -05:00
mutation-observer@^1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/mutation-observer/-/mutation-observer-1.0.3.tgz#42e9222b101bca82e5ba9d5a7acf4a14c0f263d0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-M/O/4rF2h776hV7qGMZUH3utZLO/jK7p8rnNgGkjKUw8zCGjRQPxB8z6+5l8+VjRUQ3dNYu4vjqXYLr+U8ZVNA==
feat(elements): add support for creating custom elements (#22413) PR Close #22413
2018-02-28 12:45:11 -05:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
mute-stream@0.0.5:
version "0.0.5"
resolved "https://registry.yarnpkg.com/mute-stream/-/mute-stream-0.0.5.tgz#8fbfabb0a98a253d3184331f9e8deb7372fac6c0"
integrity sha1-j7+rsKmKJT0xhDMfno3rc3L6xsA=
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
mute-stream@0.0.7, mute-stream@~0.0.4:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.0.7"
resolved "https://registry.yarnpkg.com/mute-stream/-/mute-stream-0.0.7.tgz#3075ce93bc21b8fab43e1bc4da7e8115ed1e7bab"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-MHXOk7whuPq0PhvE2n6BFe0ee6s=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
mz@2.4.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.4.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
resolved "https://registry.yarnpkg.com/mz/-/mz-2.4.0.tgz#987ba9624d89395388c37cb4741e2caf4dd13b1a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-mHupYk2JOVOIw3y0dB4sr03ROxo=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
any-promise "^1.0.0"
object-assign "^4.0.1"
thenify-all "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: to fsevents@2.0.1 (#27469) the old version was failing to compile on MacOS Mojave 10.14.1. PR Close #27469
2018-12-05 13:10:58 -05:00
nan@^2.9.2:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "2.12.1"
resolved "https://registry.yarnpkg.com/nan/-/nan-2.12.1.tgz#7b1aa193e9aa86057e3c7bbd0ac448e770925552"
integrity sha512-JY7V6lRkStKcKTvHO5NVSQRv+RV+FIL5pvDoLiAtSL9pKlC5x9PKQcZDsq7m4FO4d57mkhC6Z+QhAh3Jdk5JFw==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
nanomatch@^1.2.9:
version "1.2.13"
resolved "https://registry.yarnpkg.com/nanomatch/-/nanomatch-1.2.13.tgz#b87a8aa4fc0de8fe6be88895b38983ff265bd119"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-fpoe2T0RbHwBTBUOftAfBPaDEi06ufaUai0mE6Yn1kacc3SnTErfb/h+X94VXzI64rKFHYImXSvdwGGCmwOqCA==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
arr-diff "^4.0.0"
array-unique "^0.3.2"
define-property "^2.0.2"
extend-shallow "^3.0.2"
fragment-cache "^0.2.1"
is-windows "^1.0.2"
kind-of "^6.0.2"
object.pick "^1.3.0"
regex-not "^1.0.0"
snapdragon "^0.8.1"
to-regex "^3.0.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
nash@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/nash/-/nash-3.0.0.tgz#bced3a0cb8434c2ad30d1a0d567cfc0c37128eea"
integrity sha512-M5SahEycXUmko3zOvsBkF6p94CWLhnyy9hfpQ9Qzp+rQkQ8D1OaTlfTl1OBWktq9Fak3oDXKU+ev7tiMaMu+1w==
dependencies:
async "^1.3.0"
flat-arguments "^1.0.0"
lodash "^4.17.5"
minimist "^1.1.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 13:43:04 -05:00
natives@1.1.6, natives@^1.1.0:
version "1.1.6"
resolved "https://registry.yarnpkg.com/natives/-/natives-1.1.6.tgz#a603b4a498ab77173612b9ea1acdec4d980f00bb"
integrity sha512-6+TDFewD4yxY14ptjKaS63GVdtKiES1pTPyxn9Jb0rBqPMZ7VcCiooEhPNsr+mqHtMGxa/5c/HhcC4uPEUw/nA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
ncp@1.0.x:
version "1.0.1"
resolved "https://registry.yarnpkg.com/ncp/-/ncp-1.0.1.tgz#d15367e5cb87432ba117d2bf80fdf45aecfb4246"
integrity sha1-0VNn5cuHQyuhF9K/gP30Wuz7QkY=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
needle@^2.2.1:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "2.2.4"
resolved "https://registry.yarnpkg.com/needle/-/needle-2.2.4.tgz#51931bff82533b1928b7d1d69e01f1b00ffd2a4e"
integrity sha512-HyoqEb4wr/rsoaIDfTH2aVL9nWtQqba2/HvMv+++m8u0dz808MaagKILxtfeSN7QU7nvbQ79zk3vYOJp9zsNEA==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
debug "^2.1.2"
iconv-lite "^0.4.4"
sax "^1.2.4"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
negotiator@0.5.3:
version "0.5.3"
resolved "https://registry.yarnpkg.com/negotiator/-/negotiator-0.5.3.tgz#269d5c476810ec92edbe7b6c2f28316384f9a7e8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Jp1cR2gQ7JLtvntsLygxY4T5p+g=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
negotiator@0.6.1:
version "0.6.1"
resolved "https://registry.yarnpkg.com/negotiator/-/negotiator-0.6.1.tgz#2b327184e8992101177b28563fb5e7102acd0ca9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-KzJxhOiZIQEXeyhWP7XnECrNDKk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
neo-async@^2.6.0:
version "2.6.0"
resolved "https://registry.yarnpkg.com/neo-async/-/neo-async-2.6.0.tgz#b9d15e4d71c6762908654b5183ed38b753340835"
integrity sha512-MFh0d/Wa7vkKO3Y3LlacqAEeHK0mckVqzDieUKTT+KGxi+zIpeVsFxymkIiRpbpDziHc290Xr9A1O4Om7otoRA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
next-tick@1:
version "1.0.0"
resolved "https://registry.yarnpkg.com/next-tick/-/next-tick-1.0.0.tgz#ca86d1fe8828169b0120208e3dc8424b9db8342c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-yobR/ogoFpsBICCOPchCS524NCw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
nice-try@^1.0.4:
version "1.0.5"
resolved "https://registry.yarnpkg.com/nice-try/-/nice-try-1.0.5.tgz#a3378a7696ce7d223e88fc9b764bd7ef1089e366"
integrity sha512-1nh45deeb5olNY7eX82BkPO7SSxR5SSYJiPTrTdFUVYwAl8CKMA5N9PjTYkHiRjisVcxcQ1HXdLhx2qxxJzLNQ==
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
node-fetch-npm@^2.0.2:
version "2.0.2"
resolved "https://registry.yarnpkg.com/node-fetch-npm/-/node-fetch-npm-2.0.2.tgz#7258c9046182dca345b4208eda918daf33697ff7"
integrity sha512-nJIxm1QmAj4v3nfCvEeCrYSoVwXyxLnaPBK5W1W5DGEJwjlKuC2VEUycGw5oxk+4zZahRrB84PUJJgEmhFTDFw==
dependencies:
encoding "^0.1.11"
json-parse-better-errors "^1.0.0"
safe-buffer "^5.1.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
node-fetch@^2.2.0:
version "2.3.0"
resolved "https://registry.yarnpkg.com/node-fetch/-/node-fetch-2.3.0.tgz#1a1d940bbfb916a1d3e0219f037e89e71f8c5fa5"
integrity sha512-MOd8pV3fxENbryESLgVIeaGKrdl+uaYhCSSVkjeOb/31/njTpcis5aWfdqgNlHIrKOLRbMnfPINPOML2CIFeXA==
node-forge@^0.7.1, node-forge@^0.7.5:
version "0.7.6"
resolved "https://registry.yarnpkg.com/node-forge/-/node-forge-0.7.6.tgz#fdf3b418aee1f94f0ef642cd63486c77ca9724ac"
integrity sha512-sol30LUpz1jQFBjOKwbjxijiE3b6pjd74YwfD0fJOKPjF+fONKb2Yg8rYgS6+bK6VDl+/wfr4IYpC7jDzLUIfw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"node-libs-browser@>= 0.4.0 <=0.6.0":
version "0.6.0"
resolved "https://registry.yarnpkg.com/node-libs-browser/-/node-libs-browser-0.6.0.tgz#244806d44d319e048bc8607b5cc4eaf9a29d2e3c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-JEgG1E0xngSLyGB7XMTq+aKdLjw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
assert "^1.1.1"
browserify-zlib "~0.1.4"
buffer "^4.9.0"
console-browserify "^1.1.0"
constants-browserify "0.0.1"
crypto-browserify "~3.2.6"
domain-browser "^1.1.1"
events "^1.0.0"
http-browserify "^1.3.2"
https-browserify "0.0.0"
os-browserify "~0.1.2"
path-browserify "0.0.0"
process "^0.11.0"
punycode "^1.2.4"
querystring-es3 "~0.2.0"
readable-stream "^1.1.13"
stream-browserify "^1.0.0"
string_decoder "~0.10.25"
timers-browserify "^1.0.1"
tty-browserify "0.0.0"
url "~0.10.1"
util "~0.10.3"
vm-browserify "0.0.4"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
node-pre-gyp@^0.10.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.10.3"
resolved "https://registry.yarnpkg.com/node-pre-gyp/-/node-pre-gyp-0.10.3.tgz#3070040716afdc778747b61b6887bf78880b80fc"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-d1xFs+C/IPS8Id0qPTZ4bUT8wWryfR/OzzAFxweG+uLN85oPzyo2Iw6bVlLQ/JOdgNonXLCoRyqDzDWq4iw72A==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
detect-libc "^1.0.2"
mkdirp "^0.5.1"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
needle "^2.2.1"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
nopt "^4.0.1"
npm-packlist "^1.1.6"
npmlog "^4.0.2"
rc "^1.2.7"
rimraf "^2.6.1"
semver "^5.3.0"
tar "^4"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
node-source-walk@~1.4.0:
version "1.4.2"
resolved "https://registry.yarnpkg.com/node-source-walk/-/node-source-walk-1.4.2.tgz#311ee1e18d8795874bc2229426d572cf0c356256"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-MR7h4Y2HlYdLwiKUJtVyzww1YlY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
acorn "^1.0.3"
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
node-uuid@1.4.8, node-uuid@~1.4.7:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.4.8"
resolved "https://registry.yarnpkg.com/node-uuid/-/node-uuid-1.4.8.tgz#b040eb0923968afabf8d32fb1f17f1167fdab907"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-sEDrCSOWivq/jTL7HxfxFn/auQc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
node-watch@0.3.4:
version "0.3.4"
resolved "https://registry.yarnpkg.com/node-watch/-/node-watch-0.3.4.tgz#755f64ef5f8ad4acb5bafd2c4e7f4fb6a8db0214"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-dV9k71+K1Ky1uv0sTn9PtqjbAhQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: move zone.js to angular repo (#30962) PR Close #30962
2019-05-31 11:56:07 -04:00
nodejs-websocket@^1.7.2:
version "1.7.2"
resolved "https://registry.yarnpkg.com/nodejs-websocket/-/nodejs-websocket-1.7.2.tgz#94abd1e248f57d4d1c663dec3831015c6dad98a6"
integrity sha512-PFX6ypJcCNDs7obRellR0DGTebfUhw1SXGKe2zpB+Ng1DQJhdzbzx1ob+AvJCLzy2TJF4r8cCDqMQqei1CZdPQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
nopt@3.0.x, nopt@^3.0.1, nopt@~3.0.1:
version "3.0.6"
resolved "https://registry.yarnpkg.com/nopt/-/nopt-3.0.6.tgz#c6465dbf08abcd4db359317f79ac68a646b28ff9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-xkZdvwirzU2zWTF/eaxopkayj/k=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
abbrev "1"
nopt@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/nopt/-/nopt-4.0.1.tgz#d0d4685afd5415193c8c7505602d0d17cd64474d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-0NRoWv1UFRk8jHUFYC0NF81kR00=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
abbrev "1"
osenv "^0.1.4"
nopt@~1.0.10:
version "1.0.10"
resolved "https://registry.yarnpkg.com/nopt/-/nopt-1.0.10.tgz#6ddd21bd2a31417b92727dd585f8a6f37608ebee"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-bd0hvSoxQXuScn3Vhfim83YI6+4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
abbrev "1"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
normalize-package-data@^2.3.0, normalize-package-data@^2.3.2, normalize-package-data@^2.3.4, normalize-package-data@^2.3.5, normalize-package-data@^2.4.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.4.0"
resolved "https://registry.yarnpkg.com/normalize-package-data/-/normalize-package-data-2.4.0.tgz#12f95a307d58352075a04907b84ac8be98ac012f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-9jjUFbTPfEy3R/ad/2oNbKtW9Hgovl5O1FvFWKkKblNXoN/Oou6+9+KKohPK13Yc3/TyunyWhJp6gvRNR/PPAw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
hosted-git-info "^2.1.4"
is-builtin-module "^1.0.0"
semver "2 || 3 || 4 || 5"
validate-npm-package-license "^3.0.1"
refactor: add a commit-msg git hook to check commit messages (#22969) The commit command will fail if the commit message header does not follow the Angular convetions as defined in /CONTRIBUTING.md. You can force the commit by adding the `--no-verify` option. NOTE: You should remove all unused hooks (in <angular>/.git/hooks) before running `yarn` so that husky hooks are installed correctly. PR Close #22969
2018-03-23 19:07:33 -04:00
normalize-path@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/normalize-path/-/normalize-path-1.0.0.tgz#32d0e472f91ff345701c15a8311018d3b0a90379"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-MtDkcvkf80VwHBWoMRAY07CpA3k=
refactor: add a commit-msg git hook to check commit messages (#22969) The commit command will fail if the commit message header does not follow the Angular convetions as defined in /CONTRIBUTING.md. You can force the commit by adding the `--no-verify` option. NOTE: You should remove all unused hooks (in <angular>/.git/hooks) before running `yarn` so that husky hooks are installed correctly. PR Close #22969
2018-03-23 19:07:33 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
normalize-path@^2.0.0, normalize-path@^2.0.1, normalize-path@^2.1.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.1.1"
resolved "https://registry.yarnpkg.com/normalize-path/-/normalize-path-2.1.1.tgz#1ab28b556e198363a8c1a6f7e6fa20137fe6aed9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-GrKLVW4Zg2Oowab35vogE3/mrtk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
remove-trailing-separator "^1.0.1"
build(compiler-cli): upgrade chokidar to latest version (#28797) Fixes #28771 PR Close #28797
2019-02-18 08:11:03 -05:00
normalize-path@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/normalize-path/-/normalize-path-3.0.0.tgz#0dcd69ff23a1c9b11fd0978316644a0388216a65"
integrity sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
normalize-url@2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/normalize-url/-/normalize-url-2.0.1.tgz#835a9da1551fa26f70e92329069a23aa6574d7e6"
integrity sha512-D6MUW4K/VzoJ4rJ01JFKxDrtY1v9wrgzCX5f2qj/lzH1m/lW6MhUZFKerVsnyjOhOsYzI9Kqqak+10l4LvLpMw==
dependencies:
prepend-http "^2.0.0"
query-string "^5.0.1"
sort-keys "^2.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
npm-bundled@^1.0.1:
test(bazel): Upgrade CLI dependencies for schematics test (#28872) This commit makes the integration test for bazel-schematics more robust by removing package.json.replace. Instead of replacing the file, the test script now just overrides Angular packages with the local ones. This commit also fixes running the test locally by providing default argument for CI_CHROMEDRIVER_VERSION_ARG. PR Close #28872
2019-02-20 12:58:42 -05:00
version "1.0.6"
resolved "https://registry.yarnpkg.com/npm-bundled/-/npm-bundled-1.0.6.tgz#e7ba9aadcef962bb61248f91721cd932b3fe6bdd"
integrity sha512-8/JCaftHwbd//k6y2rEWp6k1wxVfpFzB6t1p825+cUb7Ym2XQfhwIC5KwhrvzZRJu+LtDE585zVaS32+CGtf0g==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
test(bazel): Cleanup bazel-schematics integration test (#28351) PR Close #28351
2019-01-24 14:51:20 -05:00
npm-package-arg@6.1.0, npm-package-arg@^6.0.0, npm-package-arg@^6.1.0:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "6.1.0"
resolved "https://registry.yarnpkg.com/npm-package-arg/-/npm-package-arg-6.1.0.tgz#15ae1e2758a5027efb4c250554b85a737db7fcc1"
integrity sha512-zYbhP2k9DbJhA0Z3HKUePUgdB1x7MfIfKssC+WLPFMKTBZKpZh5m13PgexJjCq6KW7j17r0jHWcCpxEqnnncSA==
dependencies:
hosted-git-info "^2.6.0"
osenv "^0.1.5"
semver "^5.5.0"
validate-npm-package-name "^3.0.0"
test(bazel): Upgrade CLI dependencies for schematics test (#28872) This commit makes the integration test for bazel-schematics more robust by removing package.json.replace. Instead of replacing the file, the test script now just overrides Angular packages with the local ones. This commit also fixes running the test locally by providing default argument for CI_CHROMEDRIVER_VERSION_ARG. PR Close #28872
2019-02-20 12:58:42 -05:00
npm-packlist@^1.1.12:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/npm-packlist/-/npm-packlist-1.2.0.tgz#55a60e793e272f00862c7089274439a4cc31fc7f"
integrity sha512-7Mni4Z8Xkx0/oegoqlcao/JpPCPEMtUvsmB0q7mgvlMinykJLSRTYuFqoQLYgGY8biuxIeiHO+QNJKbCfljewQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
ignore-walk "^3.0.1"
npm-bundled "^1.0.1"
test(bazel): Upgrade CLI dependencies for schematics test (#28872) This commit makes the integration test for bazel-schematics more robust by removing package.json.replace. Instead of replacing the file, the test script now just overrides Angular packages with the local ones. This commit also fixes running the test locally by providing default argument for CI_CHROMEDRIVER_VERSION_ARG. PR Close #28872
2019-02-20 12:58:42 -05:00
npm-packlist@^1.1.6:
version "1.4.0"
resolved "https://registry.yarnpkg.com/npm-packlist/-/npm-packlist-1.4.0.tgz#b2c0867af2a396e0734343d2b6b3f7934db935f2"
integrity sha512-zCAmKshsFx2MhOsXdYmZd1DO2d8ts80kVASSWX6lv8654i0edCnNCoEqwVsMygl1BSroCPW6Zh5Dcw+ann775g==
dependencies:
ignore-walk "^3.0.1"
npm-bundled "^1.0.1"
test(bazel): Cleanup bazel-schematics integration test (#28351) PR Close #28351
2019-01-24 14:51:20 -05:00
npm-pick-manifest@^2.2.3:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "2.2.3"
resolved "https://registry.yarnpkg.com/npm-pick-manifest/-/npm-pick-manifest-2.2.3.tgz#32111d2a9562638bb2c8f2bf27f7f3092c8fae40"
integrity sha512-+IluBC5K201+gRU85vFlUwX3PFShZAbAgDNp2ewJdWMVSppdo/Zih0ul2Ecky/X7b51J7LrrUAP+XOmOCvYZqA==
dependencies:
figgy-pudding "^3.5.1"
npm-package-arg "^6.0.0"
semver "^5.4.1"
npm-registry-fetch@^3.8.0:
version "3.8.0"
resolved "https://registry.yarnpkg.com/npm-registry-fetch/-/npm-registry-fetch-3.8.0.tgz#aa7d9a7c92aff94f48dba0984bdef4bd131c88cc"
integrity sha512-hrw8UMD+Nob3Kl3h8Z/YjmKamb1gf7D1ZZch2otrIXM3uFLB5vjEY6DhMlq80z/zZet6eETLbOXcuQudCB3Zpw==
dependencies:
JSONStream "^1.3.4"
bluebird "^3.5.1"
figgy-pudding "^3.4.1"
lru-cache "^4.1.3"
make-fetch-happen "^4.0.1"
npm-package-arg "^6.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
npm-run-path@^2.0.0:
version "2.0.2"
resolved "https://registry.yarnpkg.com/npm-run-path/-/npm-run-path-2.0.2.tgz#35a9232dfa35d7067b4cb2ddf2357b1871536c5f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-NakjLfo11wZ7TLLd8jV7GHFTbF8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
path-key "^2.0.0"
npmconf@2.0.9:
version "2.0.9"
resolved "https://registry.yarnpkg.com/npmconf/-/npmconf-2.0.9.tgz#5c87e5fb308104eceeca781e3d9115d216351ef2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-XIfl+zCBBOzuyngePZEV0hY1HvI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
config-chain "~1.1.8"
inherits "~2.0.0"
ini "^1.2.0"
mkdirp "^0.5.0"
nopt "~3.0.1"
once "~1.3.0"
osenv "^0.1.0"
semver "2 || 3 || 4"
uid-number "0.0.5"
npmlog@^4.0.2:
version "4.1.2"
resolved "https://registry.yarnpkg.com/npmlog/-/npmlog-4.1.2.tgz#08a7f2a8bf734604779a9efa4ad5cc717abb954b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-2uUqazuKlTaSI/dC8AzicUck7+IrEaOnN/e0jd3Xtt1KcGpwx30v50mL7oPyr/h9bL3E4aZccVwpwP+5W9Vjkg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
are-we-there-yet "~1.1.2"
console-control-strings "~1.1.0"
gauge "~2.7.3"
set-blocking "~2.0.0"
null-check@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/null-check/-/null-check-1.0.0.tgz#977dffd7176012b9ec30d2a39db5cf72a0439edd"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-l33/1xdgErnsMNKjnbXPcqBDnt0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
number-is-nan@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/number-is-nan/-/number-is-nan-1.0.1.tgz#097b602b53422a522c1afb8790318336941a011d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-CXtgK1NCKlIsGvuHkDGDNpQaAR0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
oauth-sign@~0.8.1, oauth-sign@~0.8.2:
version "0.8.2"
resolved "https://registry.yarnpkg.com/oauth-sign/-/oauth-sign-0.8.2.tgz#46a6ab7f0aead8deae9ec0565780b7d4efeb9d43"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Rqarfwrq2N6unsBWV4C31O/rnUM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
oauth-sign@~0.9.0:
version "0.9.0"
resolved "https://registry.yarnpkg.com/oauth-sign/-/oauth-sign-0.9.0.tgz#47a7b016baa68b5fa0ecf3dee08a85c679ac6455"
integrity sha512-fexhUFFPTGV8ybAtSIGbV6gOkSv8UtRbDBnAyLQw4QPKkgNlsH2ByPGtMUqdWkos6YCRmAqViwgZrJc/mRDzZQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
object-assign@4.1.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/object-assign/-/object-assign-4.1.0.tgz#7a3b3d0e98063d43f4c03f2e8ae6cd51a86883a0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ejs9DpgGPUP0wD8uiubNUahog6A=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
object-assign@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/object-assign/-/object-assign-3.0.0.tgz#9bedd5ca0897949bca47e7ff408062d549f587f2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-m+3VygiXlJvKR+f/QIBi1Un1h/I=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
object-assign@^4, object-assign@^4.0.1, object-assign@^4.1.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "4.1.1"
resolved "https://registry.yarnpkg.com/object-assign/-/object-assign-4.1.1.tgz#2109adc7965887cfc05cbbd442cac8bfbb360863"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-IQmtx5ZYh8/AXLvUQsrIv7s2CGM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
object-component@0.0.3:
version "0.0.3"
resolved "https://registry.yarnpkg.com/object-component/-/object-component-0.0.3.tgz#f0c69aa50efc95b866c186f400a33769cb2f1291"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8MaapQ78lbhmwYb0AKM3acsvEpE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
object-copy@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/object-copy/-/object-copy-0.1.0.tgz#7e7d858b781bd7c991a41ba975ed3812754e998c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-fn2Fi3gb18mRpBupde04EnVOmYw=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
copy-descriptor "^0.1.0"
define-property "^0.2.5"
kind-of "^3.0.3"
object-visit@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/object-visit/-/object-visit-1.0.1.tgz#f79c4493af0c5377b59fe39d395e41042dd045bb"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-95xEk68MU3e1n+OdOV5BBC3QRbs=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
isobject "^3.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
object.defaults@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/object.defaults/-/object.defaults-1.1.0.tgz#3a7f868334b407dea06da16d88d5cd29e435fecf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-On+GgzS0B96gbaFtiNXNKeQ1/s8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
array-each "^1.0.1"
array-slice "^1.0.0"
for-own "^1.0.0"
isobject "^3.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
object.map@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/object.map/-/object.map-1.0.1.tgz#cf83e59dc8fcc0ad5f4250e1f78b3b81bd801d37"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-z4Plncj8wK1fQlDh94s7gb2AHTc=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
for-own "^1.0.0"
make-iterator "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
object.omit@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/object.omit/-/object.omit-2.0.1.tgz#1a9c744829f39dbb858c76ca3579ae2a54ebd1fa"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Gpx0SCnznbuFjHbKNXmuKlTr0fo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
for-own "^0.1.4"
is-extendable "^0.1.1"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
object.pick@^1.2.0, object.pick@^1.3.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.3.0"
resolved "https://registry.yarnpkg.com/object.pick/-/object.pick-1.3.0.tgz#87a10ac4c1694bd2e1cbf53591a66141fb5dd747"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-h6EKxMFpS9Lhy/U1kaZhQftd10c=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
isobject "^3.0.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
on-finished@^2.2.0, on-finished@~2.3.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.3.0"
resolved "https://registry.yarnpkg.com/on-finished/-/on-finished-2.3.0.tgz#20f1336481b083cd75337992a16971aa2d906947"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-IPEzZIGwg811M3mSoWlxqi2QaUc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
ee-first "1.1.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
on-headers@^1.0.0, on-headers@~1.0.0, on-headers@~1.0.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/on-headers/-/on-headers-1.0.1.tgz#928f5d0f470d49342651ea6794b0857c100693f7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ko9dD0cNSTQmUepnlLCFfBAGk/c=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
once@^1.3.0, once@^1.3.1, once@^1.4.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.4.0"
resolved "https://registry.yarnpkg.com/once/-/once-1.4.0.tgz#583b1aa775961d4b113ac17d9c50baef9dd76bd1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-WDsap3WWHUsROsF9nFC6753Xa9E=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
wrappy "1"
once@~1.3.0:
version "1.3.3"
resolved "https://registry.yarnpkg.com/once/-/once-1.3.3.tgz#b2e261557ce4c314ec8304f3fa82663e4297ca20"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-suJhVXzkwxTsgwTz+oJmPkKXyiA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
wrappy "1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
onetime@^1.0.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/onetime/-/onetime-1.1.0.tgz#a1f7838f8314c516f05ecefcbc4ccfe04b4ed789"
integrity sha1-ofeDj4MUxRbwXs78vEzP4EtO14k=
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
onetime@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/onetime/-/onetime-2.0.1.tgz#067428230fd67443b2794b22bba528b6867962d4"
integrity sha1-BnQoIw/WdEOyeUsiu6UotoZ5YtQ=
dependencies:
mimic-fn "^1.0.0"
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
open@0.0.5:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.0.5"
resolved "https://registry.yarnpkg.com/open/-/open-0.0.5.tgz#42c3e18ec95466b6bf0dc42f3a2945c3f0cad8fc"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-QsPhjslUZra/DcQvOilFw/DK2Pw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update @angular/cli version to 8.0.0-beta.13 (#29873) This commit updates the version of @angular/cli to the recently pushed 8.0.0-beta.13. This is necessary as the CI has started to fail with a module hoisting issue caused by a relative import in the CLI, which is fixed in the latest (emergency) release. PR Close #29873
2019-04-12 18:51:39 -04:00
open@6.1.0:
version "6.1.0"
resolved "https://registry.yarnpkg.com/open/-/open-6.1.0.tgz#0e7e671b883976a4e5251b5d1ca905ab6f4be78f"
integrity sha512-Vqch7NFb/WsMujhqfq+B3u0xkssRjZlxh+NSsBSphpcgaFD7gfB0SUBfR91E9ygBlyNGNogXR2cUB8rRfoo2kQ==
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
dependencies:
is-wsl "^1.1.0"
build: update to rules_nodejs 0.38 (#32889) PR Close #32889
2019-09-27 18:49:59 -04:00
opener@~1.4.0:
version "1.4.3"
resolved "https://registry.yarnpkg.com/opener/-/opener-1.4.3.tgz#5c6da2c5d7e5831e8ffa3964950f8d6674ac90b8"
integrity sha1-XG2ixdflgx6P+jlklQ+NZnSskLg=
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
opn@^5.3.0:
test(bazel): Cleanup bazel-schematics integration test (#28351) PR Close #28351
2019-01-24 14:51:20 -05:00
version "5.4.0"
resolved "https://registry.yarnpkg.com/opn/-/opn-5.4.0.tgz#cb545e7aab78562beb11aa3bfabc7042e1761035"
integrity sha512-YF9MNdVy/0qvJvDtunAOzFw9iasOQHpVthTCvGzxt61Il64AYSGdK+rYwld7NAfk9qJ7dt+hymBNSc9LNYS+Sw==
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
dependencies:
is-wsl "^1.1.0"
build: update to rules_nodejs 0.38 (#32889) PR Close #32889
2019-09-27 18:49:59 -04:00
optimist@0.6.x, optimist@^0.6.1, optimist@~0.6.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.6.1"
resolved "https://registry.yarnpkg.com/optimist/-/optimist-0.6.1.tgz#da3ea74686fa21a19a111c326e90eb15a0196686"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-2j6nRob6IaGaERwybpDrFaAZZoY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
minimist "~0.0.1"
wordwrap "~0.0.2"
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
optionator@^0.8.1:
version "0.8.2"
resolved "https://registry.yarnpkg.com/optionator/-/optionator-0.8.2.tgz#364c5e409d3f4d6301d6c0b4c05bba50180aeb64"
integrity sha1-NkxeQJ0/TWMB1sC0wFu6UBgK62Q=
dependencies:
deep-is "~0.1.3"
fast-levenshtein "~2.0.4"
levn "~0.3.0"
prelude-ls "~1.1.2"
type-check "~0.3.2"
wordwrap "~1.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
ora@0.2.3:
version "0.2.3"
resolved "https://registry.yarnpkg.com/ora/-/ora-0.2.3.tgz#37527d220adcd53c39b73571d754156d5db657a4"
integrity sha1-N1J9Igrc1Tw5tzVx11QVbV22V6Q=
dependencies:
chalk "^1.1.1"
cli-cursor "^1.0.2"
cli-spinners "^0.1.2"
object-assign "^4.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
orchestrator@^0.3.0:
version "0.3.8"
resolved "https://registry.yarnpkg.com/orchestrator/-/orchestrator-0.3.8.tgz#14e7e9e2764f7315fbac184e506c7aa6df94ad7e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-FOfp4nZPcxX7rBhOUGx6pt+UrX4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
end-of-stream "~0.1.5"
sequencify "~0.0.7"
stream-consume "~0.1.0"
ordered-read-streams@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/ordered-read-streams/-/ordered-read-streams-0.1.0.tgz#fd565a9af8eb4473ba69b6ed8a34352cb552f126"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-/VZamvjrRHO6abbtijQ1LLVS8SY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
os-browserify@~0.1.2:
version "0.1.2"
resolved "https://registry.yarnpkg.com/os-browserify/-/os-browserify-0.1.2.tgz#49ca0293e0b19590a5f5de10c7f265a617d8fe54"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ScoCk+CxlZCl9d4Qx/JlphfY/lQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
os-homedir@^1.0.0, os-homedir@^1.0.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/os-homedir/-/os-homedir-1.0.2.tgz#ffbc4988336e0e833de0c168c7ef152121aa7fb3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-/7xJiDNuDoM94MFox+8VISGqf7M=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
os-locale@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/os-locale/-/os-locale-2.1.0.tgz#42bc2900a6b5b8bd17376c8e882b65afccf24bf2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-3sslG3zJbEYcaC4YVAvDorjGxc7tv6KVATnLPZONiljsUncvihe9BQoVCEs0RZ1kmf4Hk9OBqlZfJZWI4GanKA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
execa "^0.7.0"
lcid "^1.0.0"
mem "^1.1.0"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
os-locale@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/os-locale/-/os-locale-3.1.0.tgz#a802a6ee17f24c10483ab9935719cef4ed16bf1a"
integrity sha512-Z8l3R4wYWM40/52Z+S265okfFj8Kt2cC2MKY+xNi3kFs+XGI7WXu/I309QQQYbRW4ijiZ+yxs9pqEhJh0DqW3Q==
dependencies:
execa "^1.0.0"
lcid "^2.0.0"
mem "^4.0.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
os-shim@^0.1.2:
version "0.1.3"
resolved "https://registry.yarnpkg.com/os-shim/-/os-shim-0.1.3.tgz#6b62c3791cf7909ea35ed46e17658bb417cb3917"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-a2LDeRz3kJ6jXtRuF2WLtBfLORc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
os-tmpdir@^1.0.0, os-tmpdir@~1.0.1, os-tmpdir@~1.0.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/os-tmpdir/-/os-tmpdir-1.0.2.tgz#bbe67406c79aa85c5cfec766fe5734555dfa1274"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-u+Z0BseaqFxc/sdm/lc0VV36EnQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
osenv@^0.1.0, osenv@^0.1.4, osenv@^0.1.5:
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
version "0.1.5"
resolved "https://registry.yarnpkg.com/osenv/-/osenv-0.1.5.tgz#85cdfafaeb28e8677f416e287592b5f3f49ea410"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-0CWcCECdMVc2Rw3U5w9ZjqX6ga6ubk1xDVKxtBQPK7wis/0F2r9T6k4ydGYhecl7YUBxBVxhL5oisPsNxAPe2g==
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
dependencies:
os-homedir "^1.0.0"
os-tmpdir "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"over@>= 0.0.5 < 1":
version "0.0.5"
resolved "https://registry.yarnpkg.com/over/-/over-0.0.5.tgz#f29852e70fd7e25f360e013a8ec44c82aedb5708"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8phS5w/X4l82DgE6jsRMgq7bVwg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
p-cancelable@^0.4.0:
version "0.4.1"
resolved "https://registry.yarnpkg.com/p-cancelable/-/p-cancelable-0.4.1.tgz#35f363d67d52081c8d9585e37bcceb7e0bbcb2a0"
integrity sha512-HNa1A8LvB1kie7cERyy21VNeHb2CWJJYqyyC2o3klWFfMGlFmWv2Z7sFgZH8ZiaYL95ydToKTFVXgMV/Os0bBQ==
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
p-defer@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/p-defer/-/p-defer-1.0.0.tgz#9f6eb182f6c9aa8cd743004a7d4f96b196b0fb0c"
integrity sha1-n26xgvbJqozXQwBKfU+WsZaw+ww=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
p-finally@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/p-finally/-/p-finally-1.0.0.tgz#3fbcfb15b899a44123b34b6dcc18b724336a2cae"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-P7z7FbiZpEEjs0ttzBi3JDNqLK4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
p-is-promise@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/p-is-promise/-/p-is-promise-1.1.0.tgz#9c9456989e9f6588017b0434d56097675c3da05e"
integrity sha1-nJRWmJ6fZYgBewQ01WCXZ1w9oF4=
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
p-is-promise@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/p-is-promise/-/p-is-promise-2.0.0.tgz#7554e3d572109a87e1f3f53f6a7d85d1b194f4c5"
integrity sha512-pzQPhYMCAgLAKPWD2jC3Se9fEfrD9npNos0y150EeqZll7akhEgGhTW/slB6lHku8AvYGiJ+YJ5hfHKePPgFWg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
p-limit@^1.1.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.3.0"
resolved "https://registry.yarnpkg.com/p-limit/-/p-limit-1.3.0.tgz#b86bd5f0c25690911c7590fcbfc2010d54b3ccb8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-vvcXsLAJ9Dr5rQOPk7toZQZJApBl2K4J6dANSsEuh6QI41JYcsS/qhTGa9ErIUUgK3WNQoJYvylxvjqmiqEA9Q==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
p-try "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
p-limit@^2.0.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/p-limit/-/p-limit-2.2.0.tgz#417c9941e6027a9abcba5092dd2904e255b5fbc2"
integrity sha512-pZbTJpoUsCzV48Mc9Nh51VbwO0X9cuPFE8gYwx9BTCt9SF8/b7Zljd2fVgOxhIF/HDTKgpVzs+GPhyKfjLLFRQ==
dependencies:
p-try "^2.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
p-locate@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/p-locate/-/p-locate-2.0.0.tgz#20a0103b222a70c8fd39cc2e580680f3dde5ec43"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-IKAQOyIqcMj9OcwuWAaA893l7EM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
p-limit "^1.1.0"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
p-locate@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/p-locate/-/p-locate-3.0.0.tgz#322d69a05c0264b25997d9f40cd8a891ab0064a4"
integrity sha512-x+12w/To+4GFfgJhBEpiDcLozRJGegY+Ei7/z0tSLkMmxGZNybVMSfWj9aJn8Z5Fc7dBUNJOOVgPv2H7IwulSQ==
dependencies:
p-limit "^2.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
p-timeout@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/p-timeout/-/p-timeout-2.0.1.tgz#d8dd1979595d2dc0139e1fe46b8b646cb3cdf038"
integrity sha512-88em58dDVB/KzPEx1X0N3LwFfYZPyDc4B6eF38M1rk9VTZMbxXXgjugz8mmwpS9Ox4BDZ+t6t3QP5+/gazweIA==
dependencies:
p-finally "^1.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
p-try@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/p-try/-/p-try-1.0.0.tgz#cbc79cdbaf8fd4228e13f621f2b1a237c1b207b3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-y8ec26+P1CKOE/Yh8rGiN8GyB7M=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
p-try@^2.0.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/p-try/-/p-try-2.2.0.tgz#cb2868540e313d61de58fafbe35ce9004d5540e6"
integrity sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
package-json@^4.0.0:
version "4.0.1"
resolved "https://registry.yarnpkg.com/package-json/-/package-json-4.0.1.tgz#8869a0401253661c4c4ca3da6c2121ed555f5eed"
integrity sha1-iGmgQBJTZhxMTKPabCEh7VVfXu0=
dependencies:
got "^6.7.1"
registry-auth-token "^3.0.1"
registry-url "^3.0.3"
semver "^5.1.0"
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
pacote@9.5.0:
version "9.5.0"
resolved "https://registry.yarnpkg.com/pacote/-/pacote-9.5.0.tgz#85f3013a3f6dd51c108b0ccabd3de8102ddfaeda"
integrity sha512-aUplXozRbzhaJO48FaaeClmN+2Mwt741MC6M3bevIGZwdCaP7frXzbUOfOWa91FPHoLITzG0hYaKY363lxO3bg==
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
dependencies:
test(bazel): Cleanup bazel-schematics integration test (#28351) PR Close #28351
2019-01-24 14:51:20 -05:00
bluebird "^3.5.3"
cacache "^11.3.2"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
figgy-pudding "^3.5.1"
get-stream "^4.1.0"
glob "^7.1.3"
test(bazel): Cleanup bazel-schematics integration test (#28351) PR Close #28351
2019-01-24 14:51:20 -05:00
lru-cache "^5.1.1"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
make-fetch-happen "^4.0.1"
minimatch "^3.0.4"
minipass "^2.3.5"
mississippi "^3.0.0"
mkdirp "^0.5.1"
normalize-package-data "^2.4.0"
npm-package-arg "^6.1.0"
npm-packlist "^1.1.12"
test(bazel): Cleanup bazel-schematics integration test (#28351) PR Close #28351
2019-01-24 14:51:20 -05:00
npm-pick-manifest "^2.2.3"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
npm-registry-fetch "^3.8.0"
osenv "^0.1.5"
promise-inflight "^1.0.1"
promise-retry "^1.1.1"
protoduck "^5.0.1"
rimraf "^2.6.2"
safe-buffer "^5.1.2"
semver "^5.6.0"
ssri "^6.0.1"
test(bazel): Cleanup bazel-schematics integration test (#28351) PR Close #28351
2019-01-24 14:51:20 -05:00
tar "^4.4.8"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
unique-filename "^1.1.1"
which "^1.3.1"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
pako@~0.2.0, pako@~0.2.5:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.2.9"
resolved "https://registry.yarnpkg.com/pako/-/pako-0.2.9.tgz#f3f7522f4ef782348da8161bad9ecfd51bf83a75"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8/dSL073gjSNqBYbrZ7P1Rv4OnU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
pako@~1.0.2:
version "1.0.6"
resolved "https://registry.yarnpkg.com/pako/-/pako-1.0.6.tgz#0101211baa70c4bca4a0f63f2206e97b7dfaf258"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-lQe48YPsMJAig+yngZ87Lus+NF+3mtu7DVOBu6b/gHO1YpKwIj5AWjZ/TOS7i46HD/UixzWb1zeWDZfGZ3iYcg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
parallel-transform@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/parallel-transform/-/parallel-transform-1.1.0.tgz#d410f065b05da23081fcd10f28854c29bda33b06"
integrity sha1-1BDwZbBdojCB/NEPKIVMKb2jOwY=
dependencies:
cyclist "~0.2.2"
inherits "^2.0.3"
readable-stream "^2.1.5"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
parse-filepath@^1.0.1:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/parse-filepath/-/parse-filepath-1.0.2.tgz#a632127f53aaf3d15876f5872f3ffac763d6c891"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-pjISf1Oq89FYdvWHLz/6x2PWyJE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
is-absolute "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
map-cache "^0.2.0"
path-root "^0.1.1"
parse-github-repo-url@^1.3.0:
version "1.4.1"
resolved "https://registry.yarnpkg.com/parse-github-repo-url/-/parse-github-repo-url-1.4.1.tgz#9e7d8bb252a6cb6ba42595060b7bf6df3dbc1f50"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nn2LslKmy2ukJZUGC3v23z28H1A=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
parse-glob@^3.0.4:
version "3.0.4"
resolved "https://registry.yarnpkg.com/parse-glob/-/parse-glob-3.0.4.tgz#b2c376cfb11f35513badd173ef0bb6e3a388391c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ssN2z7EfNVE7rdFz7wu246OIORw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
glob-base "^0.3.0"
is-dotfile "^1.0.0"
is-extglob "^1.0.0"
is-glob "^2.0.0"
build: allow bazel build //... (#22168) Also switch our CircleCI commands to just bazel build //... bazel test //... as this is easier to understand. Note, the reason this commit removes `firebase-tools` is: 1) firebase-tools has an optional dependency on https://www.npmjs.com/package/@google-cloud/functions-emulator 2) yarn's `--ignore-optional` doesn't work for transitive deps, so there's no way to yarn install without getting that functions-emulator package 3) functions-emulator has a transitive dep on `grpc` 4) the version of `grpc` we get has `BUILD` files and no `WORKSPACE` file so it always breaks `bazel build ...` It could be solved by any of: 1) remove firebase-tools - this is what I did 2) fix yarn so you can omit optional deps of a transitive dep 3) make functions-emulator depend transitively on a more recent `grpc` version 4) patch `grpc` after install by doing an `rm` command in our postinstall or something In its place we must install protobufjs. This is needed by the ngc-wrapped test, which needs jasmine as well as bazel's worker mode dependencies, and therefore cannot simply rely on node_modules = "@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules" PR Close #22168
2018-03-20 15:34:27 -04:00
parse-json@^2.2.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/parse-json/-/parse-json-2.2.0.tgz#f480f40434ef80741f8469099f8dea18f55a4dc9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-9ID0BDTvgHQfhGkJn43qGPVaTck=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
error-ex "^1.2.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
parse-json@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/parse-json/-/parse-json-4.0.0.tgz#be35f5425be1f7f6c747184f98a788cb99477ee0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-vjX1Qlvh9/bHRxhPmKeIy5lHfuA=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
error-ex "^1.3.1"
json-parse-better-errors "^1.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
parse-passwd@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/parse-passwd/-/parse-passwd-1.0.0.tgz#6d5b934a456993b23d37f40a382d6f1666a8e5c6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-bVuTSkVpk7I9N/QKOC1vFmao5cY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
parseqs@0.0.5:
version "0.0.5"
resolved "https://registry.yarnpkg.com/parseqs/-/parseqs-0.0.5.tgz#d5208a3738e46766e291ba2ea173684921a8b89d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-1SCKNzjkZ2bikbouoXNoSSGouJ0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
better-assert "~1.0.0"
parseuri@0.0.5:
version "0.0.5"
resolved "https://registry.yarnpkg.com/parseuri/-/parseuri-0.0.5.tgz#80204a50d4dbb779bfdc6ebe2778d90e4bce320a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-gCBKUNTbt3m/3G6+J3jZDkvOMgo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
better-assert "~1.0.0"
parseurl@~1.3.0, parseurl@~1.3.1, parseurl@~1.3.2:
version "1.3.2"
resolved "https://registry.yarnpkg.com/parseurl/-/parseurl-1.3.2.tgz#fc289d4ed8993119460c156253262cdc8de65bf3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-/CidTtiZMRlGDBViUyYs3I3mW/M=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
pascalcase@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/pascalcase/-/pascalcase-0.1.1.tgz#b363e55e8006ca6fe21784d2db22bd15d7917f14"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-s2PlXoAGym/iF4TS2yK9FdeRfxQ=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
passerror@1.1.1, passerror@^1.1.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.1.1"
resolved "https://registry.yarnpkg.com/passerror/-/passerror-1.1.1.tgz#a25b88dbdd910a29603aec7dcb96e9a7a97687b4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-oluI292RCilgOux9y5bpp6l2h7Q=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
path-browserify@0.0.0:
version "0.0.0"
resolved "https://registry.yarnpkg.com/path-browserify/-/path-browserify-0.0.0.tgz#a0b870729aae214005b7d5032ec2cbbb0fb4451a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-oLhwcpquIUAFt9UDLsLLuw+0RRo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
path-dirname@^1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/path-dirname/-/path-dirname-1.0.2.tgz#cc33d24d525e099a5388c0336c6e32b9160609e0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-zDPSTVJeCZpTiMAzbG4yuRYGCeA=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
path-exists@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/path-exists/-/path-exists-2.1.0.tgz#0feb6c64f0fc518d9a754dd5efb62c7022761f4b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-D+tsZPD8UY2adU3V77YscCJ2H0s=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
pinkie-promise "^2.0.0"
path-exists@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/path-exists/-/path-exists-3.0.0.tgz#ce0ebeaa5f78cb18925ea7d810d7b59b010fd515"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-zg6+ql94yxiSXqfYENe1mwEP1RU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
path-is-absolute@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/path-is-absolute/-/path-is-absolute-1.0.1.tgz#174b9268735534ffbc7ace6bf53a5a9e1b5c5f5f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-F0uSaHNVNP+8es5r9TpanhtcX18=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
path-is-inside@^1.0.1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/path-is-inside/-/path-is-inside-1.0.2.tgz#365417dede44430d1c11af61027facf074bdfc53"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-NlQX3t5EQw0cEa9hAn+s8HS9/FM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
path-key@^2.0.0, path-key@^2.0.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.0.1"
resolved "https://registry.yarnpkg.com/path-key/-/path-key-2.0.1.tgz#411cadb574c5a140d3a4b1910d40d80cc9f40b40"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-QRyttXTFoUDTpLGRDUDYDMn0C0A=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
path-parse@^1.0.5:
version "1.0.5"
resolved "https://registry.yarnpkg.com/path-parse/-/path-parse-1.0.5.tgz#3c1adf871ea9cd6c9431b6ea2bd74a0ff055c4c1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-PBrfhx6pzWyUMbbqK9dKD/BVxME=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
path-parse@^1.0.6:
version "1.0.6"
resolved "https://registry.yarnpkg.com/path-parse/-/path-parse-1.0.6.tgz#d62dbb5679405d72c4737ec58600e9ddcf06d24c"
integrity sha512-GSmOT2EbHrINBf9SR7CDELwlJ8AENk3Qn7OikK4nFYAu3Ote2+JYNVvkpAEQm3/TLNEJFD/xZJjzyxg3KBWOzw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
path-root-regex@^0.1.0:
version "0.1.2"
resolved "https://registry.yarnpkg.com/path-root-regex/-/path-root-regex-0.1.2.tgz#bfccdc8df5b12dc52c8b43ec38d18d72c04ba96d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-v8zcjfWxLcUsi0PsONGNcsBLqW0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
path-root@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/path-root/-/path-root-0.1.1.tgz#9a4a6814cac1c0cd73360a95f32083c8ea4745b7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-mkpoFMrBwM1zNgqV8yCDyOpHRbc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
path-root-regex "^0.1.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
path-to-regexp@0.1.7:
version "0.1.7"
resolved "https://registry.yarnpkg.com/path-to-regexp/-/path-to-regexp-0.1.7.tgz#df604178005f522f15eb4490e7247a1bfaa67f8c"
integrity sha1-32BBeABfUi8V60SQ5yR6G/qmf4w=
path-to-regexp@^1.7.0:
version "1.7.0"
resolved "https://registry.yarnpkg.com/path-to-regexp/-/path-to-regexp-1.7.0.tgz#59fde0f435badacba103a84e9d3bc64e96b9937d"
integrity sha1-Wf3g9DW62suhA6hOnTvGTpa5k30=
dependencies:
isarray "0.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
path-type@^1.0.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/path-type/-/path-type-1.1.0.tgz#59c44f7ee491da704da415da5a4070ba4f8fe441"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-WcRPfuSR2nBNpBXaWkBwuk+P5EE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
graceful-fs "^4.1.2"
pify "^2.0.0"
pinkie-promise "^2.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
path-type@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/path-type/-/path-type-3.0.0.tgz#cef31dc8e0a1a3bb0d105c0cd97cf3bf47f4e36f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-T2ZUsdZFHgA3u4e5PfPbjd7HDDpxPnQb5jN0SrDsjNSuVXHJqtwTnWqG0B1jZrgmJ/7lj1EmVIByWt1gxGkWvg==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
pify "^3.0.0"
build(bazel): remove @ts-api-guardian_deps yarn_install (#29799) PR Close #29799
2019-04-09 21:08:13 -04:00
pathval@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/pathval/-/pathval-1.1.0.tgz#b942e6d4bde653005ef6b71361def8727d0645e0"
integrity sha1-uULm1L3mUwBe9rcTYd74cn0GReA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
pause-stream@0.0.11:
version "0.0.11"
resolved "https://registry.yarnpkg.com/pause-stream/-/pause-stream-0.0.11.tgz#fe5a34b0cbce12b5aa6a2b403ee2e73b602f1445"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-/lo0sMvOErWqaitAPuLnO2AvFEU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
through "~2.3"
pause@0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/pause/-/pause-0.1.0.tgz#ebc8a4a8619ff0b8a81ac1513c3434ff469fdb74"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-68ikqGGf8LioGsFRPDQ0/0af23Q=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
pbkdf2-compat@2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/pbkdf2-compat/-/pbkdf2-compat-2.0.1.tgz#b6e0c8fa99494d94e0511575802a59a5c142f288"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-tuDI+plJTZTgURV1gCpZpcFC8og=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
pegjs@^0.10.0:
version "0.10.0"
resolved "https://registry.yarnpkg.com/pegjs/-/pegjs-0.10.0.tgz#cf8bafae6eddff4b5a7efb185269eaaf4610ddbd"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-z4uvrm7d/0tafvsYUmnqr0YQ3b0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
performance-now@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/performance-now/-/performance-now-2.1.0.tgz#6309f4e0e5fa913ec1c69307ae364b4b377c9e7b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Ywn04OX6kT7BxpMHrjZLSzd8nns=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
pify@^2.0.0, pify@^2.3.0:
version "2.3.0"
resolved "https://registry.yarnpkg.com/pify/-/pify-2.3.0.tgz#ed141a6ac043a849ea588498e7dca8b15330e90c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-7RQaasBDqEnqWISY59yosVMw6Qw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
pify@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/pify/-/pify-3.0.0.tgz#e5a4acd2c101fdf3d9a4d07f0dbc4db49dd28176"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-5aSs0sEB/fPZpNB/DbxNtJ3SgXY=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
pify@^4.0.0:
version "4.0.1"
resolved "https://registry.yarnpkg.com/pify/-/pify-4.0.1.tgz#4b2cd25c50d598735c50292224fd8c6df41e3231"
integrity sha512-uB80kBFb/tfd68bVleG9T5GGsGPjJrLAUpR5PZIrhBnIaRTQRjqdJSsIKkOP6OAIFbj7GOrcudc5pNjZ+geV2g==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
pinkie-promise@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/pinkie-promise/-/pinkie-promise-2.0.1.tgz#2135d6dfa7a358c069ac9b178776288228450ffa"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ITXW36ejWMBprJsXh3YogihFD/o=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
pinkie "^2.0.0"
pinkie@^2.0.0:
version "2.0.4"
resolved "https://registry.yarnpkg.com/pinkie/-/pinkie-2.0.4.tgz#72556b80cfa0d48a974e80e77248e80ed4f7f870"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-clVrgM+g1IqXToDnckjoDtT3+HA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: downgrade `gulp-clang-format` to 1.0.23 (#31295) The `gulp format*` tasks have been broken since 5eb742621. These include the `gulp format:enforce` task, which is what runs on CI to enforce consistent code style. Here is what (I believe) happened: - I assume formatting was failing in 5eb742621 (moving `zone.js` into `angular/angular`). The reason must have been that [this glob pattern][1] matches `packages/zone.js/` (which is a directory) and passes it to `clang-format` claiming it is a file. - I further assume that in an attempt to fix the issue, `gulp-clang-format` was updated to the latest version (1.0.27) in 5eb742621. - `gulp format:enforce` stopped complaining, so everyone thought formatting was fine and moved on. - Formatting still wasn't fine, but the task completed successfully nevertheless :scream: - The reason is that angular/gulp-clang-format@55b697c5c (and subsequent commits) changed the way the `done()` callback was called, leaving it to `clang-format` to call it (while previously it was also called when the associated stream ended). - In the old version of `clang-format` that we are using (1.0.41), there is a bug (which has been fixed in angular/clang-format@4cce2c4ee): The callback is not called [unless the process exits with an error][2]. One can also see that the `gulp format:enforce` task is not completed in `gulp lint`. Example output from [build 374722][3]: ``` yarn gulp lint ... Starting 'format:enforce'... Starting 'validate-commit-messages'... ... Finished 'validate-commit-messages' after 833 ms Starting 'tools:build'... Finished 'tools:build' after 1.75 s Starting 'tslint'... Finished 'tslint' after 19 s Done in 21.82s. ``` Notice that all tasks have a corresponding "Finished X` log, except for `format:enforce`. For reference: The problem was originally reported by @ocombe on Slack ([discussion][4]). --- This commit fixes the issue by downgrading `gulp-clang-format` to 1.0.23. The linting failures due to formatting issues will be addressed in subsequent commits. [1]: https://github.com/angular/angular/blob/a8f3b317f/tools/gulp-tasks/format.js#L13 [2]: https://github.com/angular/clang-format/blob/b8c7df0b7/index.js#L95 [3]: https://circleci.com/gh/angular/angular/374722 [4]: https://angular-team.slack.com/archives/C042EU9T5/p1561480241191000 PR Close #31295
2019-06-26 14:09:32 -04:00
pkginfo@0.3.x, pkginfo@^0.3.0:
Revert "build: update gulp-clang-format dependency (#27712)" (#27759) This reverts commit d766ad01db0b595560cfa6e9b5a0b97dd0f4458e. As discussed per chat, we want to temporarily revert that change because `gulp-clang-format` expects a more recent version of `clang-format` which comes with new style updates. In order to make sure that the formatting will be enforced in the meanwhile, we need to revert the update. PR Close #27759
2018-12-19 11:40:12 -05:00
version "0.3.1"
resolved "https://registry.yarnpkg.com/pkginfo/-/pkginfo-0.3.1.tgz#5b29f6a81f70717142e09e765bbeab97b4f81e21"
integrity sha1-Wyn2qB9wcXFC4J52W76rl7T4HiE=
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
pkginfo@0.x.x:
version "0.4.1"
resolved "https://registry.yarnpkg.com/pkginfo/-/pkginfo-0.4.1.tgz#b5418ef0439de5425fc4995042dced14fb2a84ff"
integrity sha1-tUGO8EOd5UJfxJlQQtztFPsqhP8=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
plugin-error@^0.1.2:
version "0.1.2"
resolved "https://registry.yarnpkg.com/plugin-error/-/plugin-error-0.1.2.tgz#3b9bb3335ccf00f425e07437e19276967da47ace"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-O5uzM1zPAPQl4HQ34ZJ2ln2kes4=
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
dependencies:
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
ansi-cyan "^0.1.1"
ansi-red "^0.1.1"
arr-diff "^1.0.1"
arr-union "^2.0.1"
extend-shallow "^1.1.2"
build: update `conventional-changelog` and simplify `changelog` gulp task (#25838) The version prefix issue has been fixed with conventional-changelog/conventional-changelog#179. PR Close #25838
2018-09-06 04:36:27 -04:00
style: update gulp task to format untracked and diff files separately (#24969) PR Close #24969
2018-09-10 21:19:14 -04:00
plugin-error@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/plugin-error/-/plugin-error-1.0.1.tgz#77016bd8919d0ac377fdcdd0322328953ca5781c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-L1zP0dk7vGweZME2i+EeakvUNqSrdiI3F91TwEoYiGrAfUXmVv6fJIq4g82PAXxNsWOp0J7ZqQy/3Szz0ajTxA==
style: update gulp task to format untracked and diff files separately (#24969) PR Close #24969
2018-09-10 21:19:14 -04:00
dependencies:
ansi-colors "^1.0.1"
arr-diff "^4.0.0"
arr-union "^3.1.0"
extend-shallow "^3.0.2"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
portfinder@^1.0.13:
version "1.0.20"
resolved "https://registry.yarnpkg.com/portfinder/-/portfinder-1.0.20.tgz#bea68632e54b2e13ab7b0c4775e9b41bf270e44a"
integrity sha512-Yxe4mTyDzTd59PZJY4ojZR8F+E5e97iq2ZOHPz3HDgSvYC5siNad2tLooQ5y5QHyQhc3xVqvyk/eNA3wuoa7Sw==
dependencies:
async "^1.5.2"
debug "^2.2.0"
mkdirp "0.5.x"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
posix-character-classes@^0.1.0:
version "0.1.1"
resolved "https://registry.yarnpkg.com/posix-character-classes/-/posix-character-classes-0.1.1.tgz#01eac0fe3b5af71a2a6c02feabb8c1fef7e00eab"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-AerA/jta9xoqbAL+q7jB/vfgDqs=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
prelude-ls@~1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/prelude-ls/-/prelude-ls-1.1.2.tgz#21932a549f5e52ffd9a827f570e04be62a97da54"
integrity sha1-IZMqVJ9eUv/ZqCf1cOBL5iqX2lQ=
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
prepend-http@^1.0.1:
version "1.0.4"
resolved "https://registry.yarnpkg.com/prepend-http/-/prepend-http-1.0.4.tgz#d4f4562b0ce3696e41ac52d0e002e57a635dc6dc"
integrity sha1-1PRWKwzjaW5BrFLQ4ALlemNdxtw=
prepend-http@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/prepend-http/-/prepend-http-2.0.0.tgz#e92434bfa5ea8c19f41cdfd401d741a3c819d897"
integrity sha1-6SQ0v6XqjBn0HN/UAddBo8gZ2Jc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
preserve@^0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/preserve/-/preserve-0.2.0.tgz#815ed1f6ebc65926f865b310c0713bcb3315ce4b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-gV7R9uvGWSb4ZbMQwHE7yzMVzks=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
prettier@^1.7.4:
version "1.16.4"
resolved "https://registry.yarnpkg.com/prettier/-/prettier-1.16.4.tgz#73e37e73e018ad2db9c76742e2647e21790c9717"
integrity sha512-ZzWuos7TI5CKUeQAtFd6Zhm2s6EpAD/ZLApIhsF9pRvRtM1RFo61dM/4MSRUA0SuLugA/zgrZD8m0BaY46Og7g==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
pretty-hrtime@^1.0.0:
version "1.0.3"
resolved "https://registry.yarnpkg.com/pretty-hrtime/-/pretty-hrtime-1.0.3.tgz#b7e3ea42435a4c9b2759d99e0f201eb195802ee1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-t+PqQkNaTJsnWdmeDyAesZWALuE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
private@^0.1.6, private@~0.1.5:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.1.8"
resolved "https://registry.yarnpkg.com/private/-/private-0.1.8.tgz#2381edb3689f7a53d653190060fcf822d2f368ff"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-VvivMrbvd2nKkiG38qjULzlc+4Vx4wm/whI9pQD35YrARNnhxeiRktSOhSukRLFNlzg6Br/cJPet5J/u19r/mg==
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
process-nextick-args@^2.0.0, process-nextick-args@~2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/process-nextick-args/-/process-nextick-args-2.0.0.tgz#a37d732f4271b4ab1ad070d35508e8290788ffaa"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-MtEC1TqN0EU5nephaJ4rAtThHtC86dNN9qCuEhtshvpVBkAW5ZO7BASN9REnF9eoXGcRub+pFuKEpOHE+HbEMw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
process-nextick-args@~1.0.6:
version "1.0.7"
resolved "https://registry.yarnpkg.com/process-nextick-args/-/process-nextick-args-1.0.7.tgz#150e20b756590ad3f91093f25a4f2ad8bff30ba3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-FQ4gt1ZZCtP5EJPyWk8q2L/zC6M=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
process@^0.11.0, process@~0.11.0:
version "0.11.10"
resolved "https://registry.yarnpkg.com/process/-/process-0.11.10.tgz#7332300e840161bda3e69a1d1d91a7d4bc16f182"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-czIwDoQBYb2j5podHZGn1LwW8YI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
progress@1.1.8:
version "1.1.8"
resolved "https://registry.yarnpkg.com/progress/-/progress-1.1.8.tgz#e260c78f6161cdd9b0e56cc3e0a85de17c7a57be"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-4mDHj2Fhzdmw5WzD4Khd4Xx6V74=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
progress@^2.0.0:
version "2.0.3"
resolved "https://registry.yarnpkg.com/progress/-/progress-2.0.3.tgz#7e8cf8d8f5b8f239c1bc68beb4eb78567d572ef8"
integrity sha512-7PiHtLll5LdnKIMw100I+8xJXR5gW2QwWYkT6iJva0bXitZKa/XMrSbdmg3r2Xnaidz9Qumd0VPaMrZlF9V9sA==
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
promise-inflight@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/promise-inflight/-/promise-inflight-1.0.1.tgz#98472870bf228132fcbdd868129bad12c3c029e3"
integrity sha1-mEcocL8igTL8vdhoEputEsPAKeM=
promise-retry@^1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/promise-retry/-/promise-retry-1.1.1.tgz#6739e968e3051da20ce6497fb2b50f6911df3d6d"
integrity sha1-ZznpaOMFHaIM5kl/srUPaRHfPW0=
dependencies:
err-code "^1.0.0"
retry "^0.10.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
prompt@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/prompt/-/prompt-1.0.0.tgz#8e57123c396ab988897fb327fd3aedc3e735e4fe"
integrity sha1-jlcSPDlquYiJf7Mn/Trtw+c15P4=
dependencies:
colors "^1.1.2"
pkginfo "0.x.x"
read "1.0.x"
revalidator "0.1.x"
utile "0.3.x"
winston "2.1.x"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
promzard@0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/promzard/-/promzard-0.3.0.tgz#26a5d6ee8c7dee4cb12208305acfb93ba382a9ee"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-JqXW7ox97kyxIggwWs+5O6OCqe4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
read "1"
proto-list@~1.2.1:
version "1.2.4"
resolved "https://registry.yarnpkg.com/proto-list/-/proto-list-1.2.4.tgz#212d5bfe1318306a420f6402b8e26ff39647a849"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-IS1b/hMYMGpCD2QCuOJv85ZHqEk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.10 (#29694) PR Close #29694
2019-04-03 19:56:20 -04:00
protobufjs@6.8.8:
version "6.8.8"
resolved "https://registry.yarnpkg.com/protobufjs/-/protobufjs-6.8.8.tgz#c8b4f1282fd7a90e6f5b109ed11c84af82908e7c"
integrity sha512-AAmHtD5pXgZfi7GMpllpO3q1Xw1OYldr+dMUlAnffGTAhqkg72WdmSY71uKBF/JuyiKs8psYbtKrhi0ASCD8qw==
dependencies:
"@protobufjs/aspromise" "^1.1.2"
"@protobufjs/base64" "^1.1.2"
"@protobufjs/codegen" "^2.0.4"
"@protobufjs/eventemitter" "^1.1.0"
"@protobufjs/fetch" "^1.1.0"
"@protobufjs/float" "^1.0.2"
"@protobufjs/inquire" "^1.1.0"
"@protobufjs/path" "^1.1.2"
"@protobufjs/pool" "^1.1.0"
"@protobufjs/utf8" "^1.1.0"
"@types/long" "^4.0.0"
"@types/node" "^10.1.0"
long "^4.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
protochain@^1.0.5:
version "1.0.5"
resolved "https://registry.yarnpkg.com/protochain/-/protochain-1.0.5.tgz#991c407e99de264aadf8f81504b5e7faf7bfa260"
integrity sha1-mRxAfpneJkqt+PgVBLXn+ve/omA=
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
protoduck@^5.0.1:
version "5.0.1"
resolved "https://registry.yarnpkg.com/protoduck/-/protoduck-5.0.1.tgz#03c3659ca18007b69a50fd82a7ebcc516261151f"
integrity sha512-WxoCeDCoCBY55BMvj4cAEjdVUFGRWed9ZxPlqTKYyw1nDDTQ4pqmnIMAGfJlg7Dx35uB/M+PHJPTmGOvaCaPTg==
dependencies:
genfun "^5.0.0"
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
protractor@^5.4.2:
version "5.4.2"
resolved "https://registry.yarnpkg.com/protractor/-/protractor-5.4.2.tgz#329efe37f48b2141ab9467799be2d4d12eb48c13"
integrity sha512-zlIj64Cr6IOWP7RwxVeD8O4UskLYPoyIcg0HboWJL9T79F1F0VWtKkGTr/9GN6BKL+/Q/GmM7C9kFVCfDbP5sA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
"@types/q" "^0.0.32"
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
"@types/selenium-webdriver" "^3.0.0"
blocking-proxy "^1.0.0"
browserstack "^1.5.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
chalk "^1.1.3"
glob "^7.0.3"
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
jasmine "2.8.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
jasminewd2 "^2.1.0"
optimist "~0.6.0"
q "1.4.1"
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
saucelabs "^1.5.0"
selenium-webdriver "3.6.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
source-map-support "~0.4.0"
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
webdriver-js-extender "2.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
webdriver-manager "^12.0.6"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
proxy-addr@~2.0.4:
version "2.0.4"
resolved "https://registry.yarnpkg.com/proxy-addr/-/proxy-addr-2.0.4.tgz#ecfc733bf22ff8c6f407fa275327b9ab67e48b93"
integrity sha512-5erio2h9jp5CHGwcybmxmVqHmnCBZeewlfJ0pex+UW7Qny7OOZXTtH56TGNyBizkgiOwhJtMKrVzDTeKcySZwA==
dependencies:
forwarded "~0.1.2"
ipaddr.js "1.8.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
prr@~1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/prr/-/prr-1.0.1.tgz#d3fc114ba06995a45ec6893f484ceb1d78f5f476"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-0/wRS6BplaRexok/SEzrHXj19HY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
pseudomap@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/pseudomap/-/pseudomap-1.0.2.tgz#f052a28da70e618917ef0a8ac34c1ae5a68286b3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8FKijacOYYkX7wqKw0wa5aaChrM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
psl@^1.1.24:
version "1.1.31"
resolved "https://registry.yarnpkg.com/psl/-/psl-1.1.31.tgz#e9aa86d0101b5b105cbe93ac6b784cd547276184"
integrity sha512-/6pt4+C+T+wZUieKR620OpzN/LlnNKuWjy1iFLQ/UG35JqHlR/89MP1d96dUfkf6Dne3TuLQzOYEYshJ+Hx8mw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"pullstream@>= 0.4.1 < 1":
version "0.4.1"
resolved "https://registry.yarnpkg.com/pullstream/-/pullstream-0.4.1.tgz#d6fb3bf5aed697e831150eb1002c25a3f8ae1314"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-1vs79a7Wl+gxFQ6xACwlo/iuExQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
over ">= 0.0.5 < 1"
readable-stream "~1.0.31"
setimmediate ">= 1.0.2 < 2"
slice-stream ">= 1.0.0 < 2"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
pump@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/pump/-/pump-2.0.1.tgz#12399add6e4cf7526d973cbc8b5ce2e2908b3909"
integrity sha512-ruPMNRkN3MHP1cWJc9OWr+T/xDP0jhXYCLfJcBuX54hhfIBnaQmAUMfDcG4DM5UMWByBbJY69QSphm3jtDKIkA==
dependencies:
end-of-stream "^1.1.0"
once "^1.3.1"
pump@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/pump/-/pump-3.0.0.tgz#b4a2116815bde2f4e1ea602354e8c75565107a64"
integrity sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww==
dependencies:
end-of-stream "^1.1.0"
once "^1.3.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
pumpify@^1.3.3, pumpify@^1.4.0, pumpify@^1.5.1:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "1.5.1"
resolved "https://registry.yarnpkg.com/pumpify/-/pumpify-1.5.1.tgz#36513be246ab27570b1a374a5ce278bfd74370ce"
integrity sha512-oClZI37HvuUJJxSKKrC17bZ9Cu0ZYhEAGPsPUy9KlMUmv9dKX2o77RUmq7f3XjIxbwyGwYzbzQ1L2Ks8sIradQ==
dependencies:
duplexify "^3.6.0"
inherits "^2.0.3"
pump "^2.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
punycode@1.3.2:
version "1.3.2"
resolved "https://registry.yarnpkg.com/punycode/-/punycode-1.3.2.tgz#9653a036fb7c1ee42342f2325cceefea3926c48d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-llOgNvt8HuQjQvIyXM7v6jkmxI0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
punycode@^1.2.4, punycode@^1.3.2, punycode@^1.4.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.4.1"
resolved "https://registry.yarnpkg.com/punycode/-/punycode-1.4.1.tgz#c0d5a63b2718800ad8e1eb0fa5269c84dd41845e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wNWmOycYgArY4esPpSachN1BhF4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
punycode@^2.1.0:
version "2.1.1"
resolved "https://registry.yarnpkg.com/punycode/-/punycode-2.1.1.tgz#b58b010ac40c22c5657616c8d2c2c02c7bf479ec"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
q@1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/q/-/q-1.0.1.tgz#11872aeedee89268110b10a718448ffb10112a14"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-EYcq7t7okmgRCxCnGESP+xARKhQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
q@1.4.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.4.1"
resolved "https://registry.yarnpkg.com/q/-/q-1.4.1.tgz#55705bcd93c5f3673530c2c2cbc0c2b3addc286e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-VXBbzZPF82c1MMLCy8DCs63cKG4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
q@^1.1.2, q@^1.4.1, q@^1.5.1, q@~1.5.0:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.5.1"
resolved "https://registry.yarnpkg.com/q/-/q-1.5.1.tgz#7e32f75b41381291d04611f1bf14109ac00651d7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-fjL3W0E4EpHQRhHxvxQQmsAGUdc=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
qjobs@^1.1.4:
version "1.2.0"
resolved "https://registry.yarnpkg.com/qjobs/-/qjobs-1.2.0.tgz#c45e9c61800bd087ef88d7e256423bdd49e5d071"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-8YOJEHtxpySA3fFDyCRxA+UUV+fA+rTWnuWvylOK/NCjhY+b4ocCtmu8TtsWb+mYeU+GCHf/S66KZF/AsteKHg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
qs@4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/qs/-/qs-4.0.0.tgz#c31d9b74ec27df75e543a86c78728ed8d4623607"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wx2bdOwn33XlQ6hseHKO2NRiNgc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
qs@5.2.0:
version "5.2.0"
resolved "https://registry.yarnpkg.com/qs/-/qs-5.2.0.tgz#a9f31142af468cb72b25b30136ba2456834916be"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-qfMRQq9GjLcrJbMBNrokVoNJFr4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
qs@6.5.2, qs@~6.5.1, qs@~6.5.2:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "6.5.2"
resolved "https://registry.yarnpkg.com/qs/-/qs-6.5.2.tgz#cb3ae806e8740444584ef154ce8ee98d403f3e36"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-N5ZAX4/LxJmF+7wN74pUD6qAh9/wnvdQcjq9TZjevvXzSUo7bfmw91saqMjzGS2xq91/odN2dW/WOl7qQHNDGA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to rules_nodejs 0.38 (#32889) PR Close #32889
2019-09-27 18:49:59 -04:00
qs@~2.3.3:
version "2.3.3"
resolved "https://registry.yarnpkg.com/qs/-/qs-2.3.3.tgz#e9e85adbe75da0bbe4c8e0476a086290f863b404"
integrity sha1-6eha2+ddoLvkyOBHaghikPhjtAQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
qs@~5.1.0:
version "5.1.0"
resolved "https://registry.yarnpkg.com/qs/-/qs-5.1.0.tgz#4d932e5c7ea411cca76a312d39a606200fd50cd9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-TZMuXH6kEcynajEtOaYGIA/VDNk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
qs@~6.2.0:
version "6.2.3"
resolved "https://registry.yarnpkg.com/qs/-/qs-6.2.3.tgz#1cfcb25c10a9b2b483053ff39f5dfc9233908cfe"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-HPyyXBCpsrSDBT/zn138kjOQjP4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
qs@~6.4.0:
version "6.4.0"
resolved "https://registry.yarnpkg.com/qs/-/qs-6.4.0.tgz#13e26d28ad6b0ffaa91312cd3bf708ed351e7233"
integrity sha1-E+JtKK1rD/qpExLNO/cI7TUecjM=
query-string@^5.0.1:
version "5.1.1"
resolved "https://registry.yarnpkg.com/query-string/-/query-string-5.1.1.tgz#a78c012b71c17e05f2e3fa2319dd330682efb3cb"
integrity sha512-gjWOsm2SoGlgLEdAGt7a6slVOk9mGiXmPFMqrEhLQ68rhQuBnpfs3+EmlvqKyxnCo9/PPlF+9MtY02S1aFg+Jw==
dependencies:
decode-uri-component "^0.2.0"
object-assign "^4.1.0"
strict-uri-encode "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
querystring-es3@~0.2.0:
version "0.2.1"
resolved "https://registry.yarnpkg.com/querystring-es3/-/querystring-es3-0.2.1.tgz#9ec61f79049875707d69414596fd907a4d711e73"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nsYfeQSYdXB9aUFFlv2Qek1xHnM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
querystring@0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/querystring/-/querystring-0.2.0.tgz#b209849203bb25df820da756e747005878521620"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-sgmEkgO7Jd+CDadW50cAWHhSFiA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
quick-lru@^1.0.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/quick-lru/-/quick-lru-1.1.0.tgz#4360b17c61136ad38078397ff11416e186dcfbb8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Q2CxfGETatOAeDl/8RQW4Ybc+7g=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
random-bytes@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/random-bytes/-/random-bytes-1.0.0.tgz#4f68a1dc0ae58bd3fb95848c30324db75d64360b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-T2ih3Arli9P7lYSMMDJNt11kNgs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
randomatic@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/randomatic/-/randomatic-3.0.0.tgz#d35490030eb4f7578de292ce6dfb04a91a128923"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-VdxFOIEY3mNO5PtSRkkle/hPJDHvQhK21oa73K4yAc9qmp6N429gAyF1gZMOTMeS0/AYzaV/2Trcef+NaIonSA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
is-number "^4.0.0"
kind-of "^6.0.0"
math-random "^1.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
range-parser@^1.2.0, range-parser@~1.2.0:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/range-parser/-/range-parser-1.2.0.tgz#f49be6b487894ddc40dcc94a322f611092e00d5e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-9JvmtIeJTdxA3MlKMi9hEJLgDV4=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
range-parser@~1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/range-parser/-/range-parser-1.0.3.tgz#6872823535c692e2c2a0103826afd82c2e0ff175"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-aHKCNTXGkuLCoBA4Jq/YLC4P8XU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
raw-body@2.3.3:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "2.3.3"
resolved "https://registry.yarnpkg.com/raw-body/-/raw-body-2.3.3.tgz#1b324ece6b5706e153855bc1148c65bb7f6ea0c3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-9esiElv1BrZoI3rCDuOuKCBRbuApGGaDPQfjSflGxdy4oyzqghxu6klEkkVIvBje+FF0BX9coEv8KqW6X/7njw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
bytes "3.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
http-errors "1.6.3"
iconv-lite "0.4.23"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
unpipe "1.0.0"
raw-body@~2.1.2, raw-body@~2.1.5:
version "2.1.7"
resolved "https://registry.yarnpkg.com/raw-body/-/raw-body-2.1.7.tgz#adfeace2e4fb3098058014d08c072dcc59758774"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-rf6s4uT7MJgFgBTQjActzFl1h3Q=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
bytes "2.4.0"
iconv-lite "0.4.13"
unpipe "1.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
rc@^1.0.1, rc@^1.1.6, rc@^1.2.7:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.2.8"
resolved "https://registry.yarnpkg.com/rc/-/rc-1.2.8.tgz#cd924bf5200a075b83c188cd6b9e211b7fc0d3ed"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-y3bGgqKj3QBdxLbLkomlohkvsA8gdAiUQlSBJnBhfn+BPxg4bc62d8TcBW15wavDfgexCgccckhcZvywyQYPOw==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
deep-extend "^0.6.0"
ini "~1.3.0"
minimist "^1.2.0"
strip-json-comments "~2.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
react-tools@0.12.1:
version "0.12.1"
resolved "https://registry.yarnpkg.com/react-tools/-/react-tools-0.12.1.tgz#cd016e2f1b80d35a6006100305c068925e25e3d2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-zQFuLxuA01pgBhADBcBokl4l49I=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
commoner "^0.10.0"
jstransform "^8.2.0"
read-pkg-up@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/read-pkg-up/-/read-pkg-up-1.0.1.tgz#9d63c13276c065918d57f002a57f40a1b643fb02"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nWPBMnbAZZGNV/ACpX9AobZD+wI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
find-up "^1.0.0"
read-pkg "^1.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
read-pkg-up@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/read-pkg-up/-/read-pkg-up-3.0.0.tgz#3ed496685dba0f8fe118d0691dc51f4a1ff96f07"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-PtSWaF26D4/hGNBpHcUfSh/5bwc=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
find-up "^2.0.0"
read-pkg "^3.0.0"
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
read-pkg-up@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/read-pkg-up/-/read-pkg-up-4.0.0.tgz#1b221c6088ba7799601c808f91161c66e58f8978"
integrity sha512-6etQSH7nJGsK0RbG/2TeDzZFa8shjQ1um+SwQQ5cwKy0dhSXdOncEhb1CPpvQG4h7FyOV6EB6YlV0yJvZQNAkA==
dependencies:
find-up "^3.0.0"
read-pkg "^3.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
read-pkg@^1.0.0, read-pkg@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/read-pkg/-/read-pkg-1.1.0.tgz#f5ffaa5ecd29cb31c0474bca7d756b6bb29e3f28"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-9f+qXs0pyzHAR0vKfXVra7KePyg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
load-json-file "^1.0.0"
normalize-package-data "^2.3.2"
path-type "^1.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
read-pkg@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/read-pkg/-/read-pkg-3.0.0.tgz#9cbc686978fee65d16c00e2b19c237fcf6e38389"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-nLxoaXj+5l0WwA4rGcI3/Pbjg4k=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
load-json-file "^4.0.0"
normalize-package-data "^2.3.2"
path-type "^3.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
read@1, read@1.0.7, read@1.0.x:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.7"
resolved "https://registry.yarnpkg.com/read/-/read-1.0.7.tgz#b3da19bd052431a97671d44a42634adf710b40c4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-s9oZvQUkMal2cdRKQmNK33ELQMQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
mute-stream "~0.0.4"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
"readable-stream@1 || 2", readable-stream@^2.0.0, readable-stream@^2.0.1, readable-stream@^2.0.2, readable-stream@^2.0.4, readable-stream@^2.0.5, readable-stream@^2.0.6, readable-stream@^2.1.5, readable-stream@^2.2.2, readable-stream@^2.3.0, readable-stream@^2.3.5, readable-stream@~2.3.6:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "2.3.6"
resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-2.3.6.tgz#b11c27d88b8ff1fbe070643cf94b0c79ae1b0aaf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-tQtKA9WIAhBF3+VLAseyMqZeBjW0AHJoxOtYqSUZNJxauErmLbVm2FW1y+J/YA9dUrAC39ITejlZWhVIwawkKw==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
core-util-is "~1.0.0"
inherits "~2.0.3"
isarray "~1.0.0"
process-nextick-args "~2.0.0"
safe-buffer "~5.1.1"
string_decoder "~1.1.1"
util-deprecate "~1.0.1"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
"readable-stream@>=1.0.33-1 <1.1.0-0", readable-stream@~1.0.0, readable-stream@~1.0.31:
version "1.0.34"
resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-1.0.34.tgz#125820e34bc842d2f2aaafafe4c2916ee32c157c"
integrity sha1-Elgg40vIQtLyqq+v5MKRbuMsFXw=
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
dependencies:
core-util-is "~1.0.0"
inherits "~2.0.1"
isarray "0.0.1"
string_decoder "~0.10.x"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
readable-stream@^1.0.27-1, readable-stream@^1.1.13, readable-stream@^1.1.8, readable-stream@~1.1.8, readable-stream@~1.1.9:
version "1.1.14"
resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-1.1.14.tgz#7cf4c54ef648e3813084c636dd2079e166c081d9"
integrity sha1-fPTFTvZI44EwhMY23SB54WbAgdk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
core-util-is "~1.0.0"
inherits "~2.0.1"
isarray "0.0.1"
string_decoder "~0.10.x"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
readable-stream@~2.0.0, readable-stream@~2.0.5, readable-stream@~2.0.6:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.0.6"
resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-2.0.6.tgz#8f90341e68a53ccc928788dacfcd11b36eb9b78e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-j5A0HmilPMySh4jaz80Rs265t44=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
core-util-is "~1.0.0"
inherits "~2.0.1"
isarray "~1.0.0"
process-nextick-args "~1.0.6"
string_decoder "~0.10.x"
util-deprecate "~1.0.1"
build(compiler-cli): upgrade chokidar to latest version (#28797) Fixes #28771 PR Close #28797
2019-02-18 08:11:03 -05:00
readdirp@^2.0.0, readdirp@^2.2.1:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "2.2.1"
resolved "https://registry.yarnpkg.com/readdirp/-/readdirp-2.2.1.tgz#0e87622a3325aa33e892285caf8b4e846529a525"
integrity sha512-1JU/8q+VgFZyxwrJ+SVIOsh+KywWGpds3NTqikiKpDMZWScmAYyKIgqkO+ARvNWJfXeXR1zxz7aHF4u4CyH6vQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
graceful-fs "^4.1.11"
micromatch "^3.1.10"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
readable-stream "^2.0.2"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
readline2@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/readline2/-/readline2-1.0.1.tgz#41059608ffc154757b715d9989d199ffbf372e35"
integrity sha1-QQWWCP/BVHV7cV2ZidGZ/783LjU=
dependencies:
code-point-at "^1.0.0"
is-fullwidth-code-point "^1.0.0"
mute-stream "0.0.5"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
recast@^0.11.17:
version "0.11.23"
resolved "https://registry.yarnpkg.com/recast/-/recast-0.11.23.tgz#451fd3004ab1e4df9b4e4b66376b2a21912462d3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-RR/TAEqx5N+bTktmN2sqIZEkYtM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
ast-types "0.9.6"
esprima "~3.1.0"
private "~0.1.5"
source-map "~0.5.0"
rechoir@^0.6.2:
version "0.6.2"
resolved "https://registry.yarnpkg.com/rechoir/-/rechoir-0.6.2.tgz#85204b54dba82d5742e28c96756ef43af50e3384"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-hSBLVNuoLVdC4oyWdW70OvUOM4Q=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
resolve "^1.1.6"
redent@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/redent/-/redent-1.0.0.tgz#cf916ab1fd5f1f16dfb20822dd6ec7f730c2afde"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-z5Fqsf1fHxbfsggi3W7H9zDCr94=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
indent-string "^2.1.0"
strip-indent "^1.0.1"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
redent@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/redent/-/redent-2.0.0.tgz#c1b2007b42d57eb1389079b3c8333639d5e1ccaa"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wbIAe0LVfrE4kHmzyDM2OdXhzKo=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
indent-string "^3.0.0"
strip-indent "^2.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
reflect-metadata@^0.1.3:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.1.12"
resolved "https://registry.yarnpkg.com/reflect-metadata/-/reflect-metadata-0.1.12.tgz#311bf0c6b63cd782f228a81abe146a2bfa9c56f2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-n+IyV+nGz3+0q3/Yf1ra12KpCyi001bi4XFxSjbiWWjfqb52iTTtpGXmCCAOWWIAn9KEuFZKGqBERHmrtScZ3A==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
regenerator-runtime@^0.11.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.11.1"
resolved "https://registry.yarnpkg.com/regenerator-runtime/-/regenerator-runtime-0.11.1.tgz#be05ad7f9bf7d22e056f9726cee5017fbf19e2e9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-MguG95oij0fC3QV3URf4V2SDYGJhJnJGqvIIgdECeODCT98wSWDAJ94SSuVpYQUoTcGUIL6L4yNB7j1DFFHSBg==
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
regenerator-runtime@^0.9.5:
version "0.9.6"
resolved "https://registry.yarnpkg.com/regenerator-runtime/-/regenerator-runtime-0.9.6.tgz#d33eb95d0d2001a4be39659707c51b0cb71ce029"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-0z65XQ0gAaS+OWWXB8UbDLcc4Ck=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
regex-cache@^0.4.2:
version "0.4.4"
resolved "https://registry.yarnpkg.com/regex-cache/-/regex-cache-0.4.4.tgz#75bdc58a2a1496cec48a12835bc54c8d562336dd"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-nVIZwtCjkC9YgvWkpM55B5rBhBYRZhAaJbgcFYXXsHnbZ9UZI9nnVWYZpBlCqv9ho2eZryPnWrZGsOdPwVWXWQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-equal-shallow "^0.1.3"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
regex-not@^1.0.0, regex-not@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/regex-not/-/regex-not-1.0.2.tgz#1f4ece27e00b0b65e0247a6810e6a85d83a5752c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-J6SDjUgDxQj5NusnOtdFxDwN/+HWykR8GELwctJ7mdqhcyy1xEc4SRFHUXvxTp661YaVKAjfRLZ9cCqS6tn32A==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
extend-shallow "^3.0.2"
safe-regex "^1.1.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
registry-auth-token@^3.0.1:
version "3.3.2"
resolved "https://registry.yarnpkg.com/registry-auth-token/-/registry-auth-token-3.3.2.tgz#851fd49038eecb586911115af845260eec983f20"
integrity sha512-JL39c60XlzCVgNrO+qq68FoNb56w/m7JYvGR2jT5iR1xBrUA3Mfx5Twk5rqTThPmQKMWydGmq8oFtDlxfrmxnQ==
dependencies:
rc "^1.1.6"
safe-buffer "^5.0.1"
registry-url@^3.0.3:
version "3.1.0"
resolved "https://registry.yarnpkg.com/registry-url/-/registry-url-3.1.0.tgz#3d4ef870f73dde1d77f0cf9a381432444e174942"
integrity sha1-PU74cPc93h138M+aOBQyRE4XSUI=
dependencies:
rc "^1.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
remove-trailing-separator@^1.0.1:
version "1.1.0"
resolved "https://registry.yarnpkg.com/remove-trailing-separator/-/remove-trailing-separator-1.1.0.tgz#c24bce2a283adad5bc3f58e0d48249b92379d8ef"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wkvOKig62tW8P1jg1IJJuSN52O8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
repeat-element@^1.1.2:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "1.1.3"
resolved "https://registry.yarnpkg.com/repeat-element/-/repeat-element-1.1.3.tgz#782e0d825c0c5a3bb39731f84efee6b742e6b1ce"
integrity sha512-ahGq0ZnV5m5XtZLMb+vP76kcAM5nkLqk0lpqAuojSKGgQtn4eRi4ZZGm2olo2zKFH+sMsWaqOCW1dqAnOru72g==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
repeat-string@^0.2.2:
version "0.2.2"
resolved "https://registry.yarnpkg.com/repeat-string/-/repeat-string-0.2.2.tgz#c7a8d3236068362059a7e4651fc6884e8b1fb4ae"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-x6jTI2BoNiBZp+RlH8aITosftK4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
repeat-string@^1.5.2, repeat-string@^1.6.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.6.1"
resolved "https://registry.yarnpkg.com/repeat-string/-/repeat-string-1.6.1.tgz#8dcae470e1c88abc2d600fff4a776286da75e637"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-jcrkcOHIirwtYA//Sndihtp15jc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
repeating@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/repeating/-/repeating-2.0.1.tgz#5214c53a926d3552707527fbab415dbc08d06dda"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-UhTFOpJtNVJwdSf7q0FdvAjQbdo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-finite "^1.0.0"
replace-ext@0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/replace-ext/-/replace-ext-0.0.1.tgz#29bbd92078a739f0bcce2b4ee41e837953522924"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-KbvZIHinOfC8zitO5B6DeVNSKSQ=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
replace-ext@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/replace-ext/-/replace-ext-1.0.0.tgz#de63128373fcbf7c3ccfa4de5a480c45a67958eb"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-3mMSg3P8v3w8z6TeWkgMRaZ5WOs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
request-progress@0.3.1:
version "0.3.1"
resolved "https://registry.yarnpkg.com/request-progress/-/request-progress-0.3.1.tgz#0721c105d8a96ac6b2ce8b2c89ae2d5ecfcf6b3a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ByHBBdipasayzossia4tXs/Pazo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
throttleit "~0.0.2"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
request@2.75.0:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
version "2.75.0"
resolved "https://registry.yarnpkg.com/request/-/request-2.75.0.tgz#d2b8268a286da13eaa5d01adf5d18cc90f657d93"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-0rgmiihtoT6qXQGt9dGMyQ9lfZM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
aws-sign2 "~0.6.0"
aws4 "^1.2.1"
bl "~1.1.2"
caseless "~0.11.0"
combined-stream "~1.0.5"
extend "~3.0.0"
forever-agent "~0.6.1"
form-data "~2.0.0"
har-validator "~2.0.6"
hawk "~3.1.3"
http-signature "~1.1.0"
is-typedarray "~1.0.0"
isstream "~0.1.2"
json-stringify-safe "~5.0.1"
mime-types "~2.1.7"
node-uuid "~1.4.7"
oauth-sign "~0.8.1"
qs "~6.2.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
stringstream "~0.0.4"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
tough-cookie "~2.3.0"
tunnel-agent "~0.4.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
request@2.x, request@^2.87.0:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "2.87.0"
resolved "https://registry.yarnpkg.com/request/-/request-2.87.0.tgz#32f00235cd08d482b4d0d68db93a829c0ed5756e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-fcogkm7Az5bsS6Sl0sibkbhcKsnyon/jV1kF3ajGmF0c8HrttdKTPRT9hieOaQHA5HEq6r8OyWOo/o781C1tNw==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
aws-sign2 "~0.7.0"
aws4 "^1.6.0"
caseless "~0.12.0"
combined-stream "~1.0.5"
extend "~3.0.1"
forever-agent "~0.6.1"
form-data "~2.3.1"
har-validator "~5.0.3"
http-signature "~1.2.0"
is-typedarray "~1.0.0"
isstream "~0.1.2"
json-stringify-safe "~5.0.1"
mime-types "~2.1.17"
oauth-sign "~0.8.2"
performance-now "^2.1.0"
qs "~6.5.1"
safe-buffer "^5.1.1"
tough-cookie "~2.3.3"
tunnel-agent "^0.6.0"
uuid "^3.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
request@^2.72.0, request@^2.74.0, request@^2.79.0, request@^2.81.0, request@^2.85.0, request@^2.88.0:
version "2.88.0"
resolved "https://registry.yarnpkg.com/request/-/request-2.88.0.tgz#9c2fca4f7d35b592efe57c7f0a55e81052124fef"
integrity sha512-NAqBSrijGLZdM0WZNsInLJpkJokL72XYjUpnB0iwsRgxh7dB6COrHnTBNwN0E+lHDAJzu7kLAkDeY08z2/A0hg==
dependencies:
aws-sign2 "~0.7.0"
aws4 "^1.8.0"
caseless "~0.12.0"
combined-stream "~1.0.6"
extend "~3.0.2"
forever-agent "~0.6.1"
form-data "~2.3.2"
har-validator "~5.1.0"
http-signature "~1.2.0"
is-typedarray "~1.0.0"
isstream "~0.1.2"
json-stringify-safe "~5.0.1"
mime-types "~2.1.19"
oauth-sign "~0.9.0"
performance-now "^2.1.0"
qs "~6.5.2"
safe-buffer "^5.1.2"
tough-cookie "~2.4.3"
tunnel-agent "^0.6.0"
uuid "^3.3.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
request@~2.74.0:
version "2.74.0"
resolved "https://registry.yarnpkg.com/request/-/request-2.74.0.tgz#7693ca768bbb0ea5c8ce08c084a45efa05b892ab"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-dpPKdou7DqXIzgjAhKRe+gW4kqs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
aws-sign2 "~0.6.0"
aws4 "^1.2.1"
bl "~1.1.2"
caseless "~0.11.0"
combined-stream "~1.0.5"
extend "~3.0.0"
forever-agent "~0.6.1"
form-data "~1.0.0-rc4"
har-validator "~2.0.6"
hawk "~3.1.3"
http-signature "~1.1.0"
is-typedarray "~1.0.0"
isstream "~0.1.2"
json-stringify-safe "~5.0.1"
mime-types "~2.1.7"
node-uuid "~1.4.7"
oauth-sign "~0.8.1"
qs "~6.2.0"
stringstream "~0.0.4"
tough-cookie "~2.3.0"
tunnel-agent "~0.4.1"
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
require-dir@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/require-dir/-/require-dir-1.0.0.tgz#c2639de72960ea1ee280279f2da35e03c6536b2d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-PUJcQVTP4n6F8Un1GEEWhqnmBMfukVsL5gqwBxt7RF+nP+9hSOLJ/vSs5iUoXw1UWDgzqg9B/IIb15kfQKWsAQ==
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
require-directory@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/require-directory/-/require-directory-2.1.1.tgz#8c64ad5fd30dab1c976e2344ffe7f792a6a6df42"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-jGStX9MNqxyXbiNE/+f3kqam30I=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
require-main-filename@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/require-main-filename/-/require-main-filename-1.0.1.tgz#97f717b69d48784f5f526a6c5aa8ffdda055a4d1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-l/cXtp1IeE9fUmpsWqj/3aBVpNE=
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
require-main-filename@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/require-main-filename/-/require-main-filename-2.0.0.tgz#d0b329ecc7cc0f61649f62215be69af54aa8989b"
integrity sha512-NKN5kMDylKuldxYLSUfrbo5Tuzh4hd+2E8NPPX02mZtn1VuREQToYe/ZdlJy+J3uCpfaiGF05e7B8W0iXbQHmg==
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
requirejs@2.3.5:
version "2.3.5"
resolved "https://registry.yarnpkg.com/requirejs/-/requirejs-2.3.5.tgz#617b9acbbcb336540ef4914d790323a8d4b861b0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-svnO+aNcR/an9Dpi44C7KSAy5fFGLtmPbaaCeQaklUz8BQhS64tWWIIlvEA5jrWICzlO/X9KSzSeXFnZdBu8nw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
requires-port@1.x.x, requires-port@^1.0.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.0"
resolved "https://registry.yarnpkg.com/requires-port/-/requires-port-1.0.0.tgz#925d2601d39ac485e091cf0da5c6e694dc3dcaff"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-kl0mAdOaxIXgkc8NpcbmlNw9yv8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
resolve-dir@^1.0.0, resolve-dir@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/resolve-dir/-/resolve-dir-1.0.1.tgz#79a40644c362be82f26effe739c9bb5382046f43"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-eaQGRMNivoLybv/nOcm7U4IEb0M=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
expand-tilde "^2.0.0"
global-modules "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
resolve-url@^0.2.1:
version "0.2.1"
resolved "https://registry.yarnpkg.com/resolve-url/-/resolve-url-0.2.1.tgz#2c637fe77c893afd2a663fe21aa9080068e2052a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-LGN/53yJOv0qZj/iGqkIAGjiBSo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
resolve@0.2.3:
version "0.2.3"
resolved "https://registry.yarnpkg.com/resolve/-/resolve-0.2.3.tgz#f1eb7fb76436f91d87fd19c5f973fe7d506f6571"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8et/t2Q2+R2H/RnF+XP+fVBvZXE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
resolve@1.8.1, resolve@^1.1.6, resolve@^1.1.7, resolve@^1.3.2:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.8.1"
resolved "https://registry.yarnpkg.com/resolve/-/resolve-1.8.1.tgz#82f1ec19a423ac1fbd080b0bab06ba36e84a7a26"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-AicPrAC7Qu1JxPCZ9ZgCZlY35QgFnNqc+0LtbRNxnVw4TXvjQ72wnuL9JQcEBgXkI9JM8MsT9kaQoHcpCRJOYA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
path-parse "^1.0.5"
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
resolve@^0.7.1:
version "0.7.4"
resolved "https://registry.yarnpkg.com/resolve/-/resolve-0.7.4.tgz#395a9ef9e873fbfe12bd14408bd91bb936003d69"
integrity sha1-OVqe+ehz+/4SvRRAi9kbuTYAPWk=
build: update to nodejs rules 0.27 (#29210) PR Close #29210
2019-03-14 22:35:00 -04:00
resolve@^1.10.0:
version "1.10.0"
resolved "https://registry.yarnpkg.com/resolve/-/resolve-1.10.0.tgz#3bdaaeaf45cc07f375656dfd2e54ed0810b101ba"
integrity sha512-3sUr9aq5OfSg2S9pNtPA9hL1FVEAjvfOC4leW0SNf/mpnaakz2a9femSd6LqAww2RaFctwyf1lCqnTHuF1rxDg==
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
dependencies:
path-parse "^1.0.6"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
response-time@~2.3.1:
version "2.3.2"
resolved "https://registry.yarnpkg.com/response-time/-/response-time-2.3.2.tgz#ffa71bab952d62f7c1d49b7434355fbc68dffc5a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-/6cbq5UtYvfB1Jt0NDVfvGjf/Fo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
depd "~1.1.0"
on-headers "~1.0.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
responselike@1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/responselike/-/responselike-1.0.2.tgz#918720ef3b631c5642be068f15ade5a46f4ba1e7"
integrity sha1-kYcg7ztjHFZCvgaPFa3lpG9Loec=
dependencies:
lowercase-keys "^1.0.0"
restore-cursor@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/restore-cursor/-/restore-cursor-1.0.1.tgz#34661f46886327fed2991479152252df92daa541"
integrity sha1-NGYfRohjJ/7SmRR5FSJS35LapUE=
dependencies:
exit-hook "^1.0.0"
onetime "^1.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
restore-cursor@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/restore-cursor/-/restore-cursor-2.0.0.tgz#9f7ee287f82fd326d4fd162923d62129eee0dfaf"
integrity sha1-n37ih/gv0ybU/RYpI9YhKe7g368=
dependencies:
onetime "^2.0.0"
signal-exit "^3.0.2"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
ret@~0.1.10:
version "0.1.15"
resolved "https://registry.yarnpkg.com/ret/-/ret-0.1.15.tgz#b8a4825d5bdb1fc3f6f53c2bc33f81388681c7bc"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-TTlYpa+OL+vMMNG24xSlQGEJ3B/RzEfUlLct7b5G/ytav+wPrplCpVMFuwzXbkecJrb6IYo1iFb0S9v37754mg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
retry-axios@0.3.2, retry-axios@^0.3.2:
version "0.3.2"
resolved "https://registry.yarnpkg.com/retry-axios/-/retry-axios-0.3.2.tgz#5757c80f585b4cc4c4986aa2ffd47a60c6d35e13"
integrity sha512-jp4YlI0qyDFfXiXGhkCOliBN1G7fRH03Nqy8YdShzGqbY5/9S2x/IR6C88ls2DFkbWuL3ASkP7QD3pVrNpPgwQ==
retry-request@^3.0.0:
version "3.3.2"
resolved "https://registry.yarnpkg.com/retry-request/-/retry-request-3.3.2.tgz#fd8e0079e7b0dfc7056e500b6f089437db0da4df"
integrity sha512-WIiGp37XXDC6e7ku3LFoi7LCL/Gs9luGeeqvbPRb+Zl6OQMw4RCRfSaW+aLfE6lhz1R941UavE6Svl3Dm5xGIQ==
dependencies:
request "^2.81.0"
through2 "^2.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
retry@^0.10.0:
version "0.10.1"
resolved "https://registry.yarnpkg.com/retry/-/retry-0.10.1.tgz#e76388d217992c252750241d3d3956fed98d8ff4"
integrity sha1-52OI0heZLCUnUCQdPTlW/tmNj/Q=
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
revalidator@0.1.x:
version "0.1.8"
resolved "https://registry.yarnpkg.com/revalidator/-/revalidator-0.1.8.tgz#fece61bfa0c1b52a206bd6b18198184bdd523a3b"
integrity sha1-/s5hv6DBtSoga9axgZgYS91SOjs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
rewire@2.5.2:
version "2.5.2"
resolved "https://registry.yarnpkg.com/rewire/-/rewire-2.5.2.tgz#6427de7b7feefa7d36401507eb64a5385bc58dc7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ZCfee3/u+n02QBUH62SlOFvFjcc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
rfdc@^1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/rfdc/-/rfdc-1.1.2.tgz#e6e72d74f5dc39de8f538f65e00c36c18018e349"
integrity sha512-92ktAgvZhBzYTIK0Mja9uen5q5J3NRVMoDkJL2VMwq6SXjVCgqvQeVP2XAaUY6HT+XpQYeLSjb3UoitBryKmdA==
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
rfdc@^1.1.4:
version "1.1.4"
resolved "https://registry.yarnpkg.com/rfdc/-/rfdc-1.1.4.tgz#ba72cc1367a0ccd9cf81a870b3b58bd3ad07f8c2"
integrity sha512-5C9HXdzK8EAqN7JDif30jqsBzavB7wLpaubisuQIGHWf2gUXSpzy6ArX/+Da8RjFpagWsCn+pIgxTMAmKw9Zug==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
right-align@^0.1.1:
version "0.1.3"
resolved "https://registry.yarnpkg.com/right-align/-/right-align-0.1.3.tgz#61339b722fe6a3515689210d24e14c96148613ef"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-YTObci/mo1FWiSENJOFMlhSGE+8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
align-text "^0.1.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
rimraf@2, rimraf@2.6.2, rimraf@^2.2.8, rimraf@^2.5.2, rimraf@^2.6.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.6.2"
resolved "https://registry.yarnpkg.com/rimraf/-/rimraf-2.6.2.tgz#2ed8150d24a16ea8651e6d6ef0f47c4158ce7a36"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-lreewLK/BlghmxtfH36YYVg1i8IAce4TI7oao75I1g245+6BctqTVQiBP3YUJ9C6DQOXJmkYR9X9fCLtCOJc5w==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
glob "^7.0.5"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
rimraf@2.x.x, rimraf@^2.5.4, rimraf@^2.6.1, rimraf@^2.6.2:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "2.6.3"
resolved "https://registry.yarnpkg.com/rimraf/-/rimraf-2.6.3.tgz#b2d104fe0d8fb27cf9e0a1cda8262dd3833c6cab"
integrity sha512-mwqeW5XsA2qAejG46gYdENaxXjx9onRNCfn7L0duuP4hCuTIi/QO7PDK07KJfp1d+izWPrzEJDcSqBa0OZQriA==
dependencies:
glob "^7.1.3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ripemd160@0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/ripemd160/-/ripemd160-0.2.0.tgz#2bf198bde167cacfa51c0a928e84b68bbe171fce"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-K/GYveFnys+lHAqSjoS2i74XH84=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
rndm@1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/rndm/-/rndm-1.2.0.tgz#f33fe9cfb52bbfd520aa18323bc65db110a1b76c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-8z/pz7Urv9UgqhgyO8ZdsRCht2w=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
rollup-plugin-amd@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/rollup-plugin-amd/-/rollup-plugin-amd-3.0.0.tgz#c09efa5e00ae092cfe581a62fb6f0b01bf788ec1"
integrity sha512-nlazscW4UdlCKef12oxlombIWSicuHZDiY8fyU0dhpB7CQFb3JTX/qq17zDccn+K2QBbIvXlGdTusyQi5eMUIQ==
dependencies:
"@buxlabs/amd-to-es6" "^0.12.0"
rollup-pluginutils "^2.0.1"
build: update to nodejs rules 0.27 (#29210) PR Close #29210
2019-03-14 22:35:00 -04:00
rollup-plugin-commonjs@^9.2.1:
version "9.2.1"
resolved "https://registry.yarnpkg.com/rollup-plugin-commonjs/-/rollup-plugin-commonjs-9.2.1.tgz#bb151ca8fa23600c7a03e25f9f0a45b1ee922dac"
integrity sha512-X0A/Cp/t+zbONFinBhiTZrfuUaVwRIp4xsbKq/2ohA2CDULa/7ONSJTelqxon+Vds2R2t2qJTqJQucKUC8GKkw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: update to nodejs rules 0.27 (#29210) PR Close #29210
2019-03-14 22:35:00 -04:00
estree-walker "^0.5.2"
magic-string "^0.25.1"
resolve "^1.10.0"
rollup-pluginutils "^2.3.3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
rollup-plugin-json@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/rollup-plugin-json/-/rollup-plugin-json-4.0.0.tgz#a18da0a4b30bf5ca1ee76ddb1422afbb84ae2b9e"
integrity sha512-hgb8N7Cgfw5SZAkb3jf0QXii6QX/FOkiIq2M7BAQIEydjHvTyxXHQiIzZaTFgx1GK0cRCHOCBHIyEkkLdWKxow==
dependencies:
rollup-pluginutils "^2.5.0"
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
rollup-plugin-node-resolve@^4.0.0:
build: update to nodejs rules 0.27 (#29210) PR Close #29210
2019-03-14 22:35:00 -04:00
version "4.0.1"
resolved "https://registry.yarnpkg.com/rollup-plugin-node-resolve/-/rollup-plugin-node-resolve-4.0.1.tgz#f95765d174e5daeef9ea6268566141f53aa9d422"
integrity sha512-fSS7YDuCe0gYqKsr5OvxMloeZYUSgN43Ypi1WeRZzQcWtHgFayV5tUSPYpxuaioIIWaBXl6NrVk0T2/sKwueLg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
builtin-modules "^3.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
is-module "^1.0.0"
build: update to nodejs rules 0.27 (#29210) PR Close #29210
2019-03-14 22:35:00 -04:00
resolve "^1.10.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
rollup-plugin-node-resolve@~4.2.3:
version "4.2.4"
resolved "https://registry.yarnpkg.com/rollup-plugin-node-resolve/-/rollup-plugin-node-resolve-4.2.4.tgz#7d370f8d6fd3031006a0032c38262dd9be3c6250"
integrity sha512-t/64I6l7fZ9BxqD3XlX4ZeO6+5RLKyfpwE2CiPNUKa+GocPlQhf/C208ou8y3AwtNsc6bjSk/8/6y/YAyxCIvw==
dependencies:
"@types/resolve" "0.0.8"
builtin-modules "^3.1.0"
is-module "^1.0.0"
resolve "^1.10.0"
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
rollup-plugin-sourcemaps@^0.4.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.4.2"
resolved "https://registry.yarnpkg.com/rollup-plugin-sourcemaps/-/rollup-plugin-sourcemaps-0.4.2.tgz#62125aa94087aadf7b83ef4dfaf629b473135e87"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-YhJaqUCHqt97g+9N+vYptHMTXoc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
rollup-pluginutils "^2.0.1"
source-map-resolve "^0.5.0"
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
rollup-plugin-terser@~4.0.4:
version "4.0.4"
resolved "https://registry.yarnpkg.com/rollup-plugin-terser/-/rollup-plugin-terser-4.0.4.tgz#6f661ef284fa7c27963d242601691dc3d23f994e"
integrity sha512-wPANT5XKVJJ8RDUN0+wIr7UPd0lIXBo4UdJ59VmlPCtlFsE20AM+14pe+tk7YunCsWEiuzkDBY3QIkSCjtrPXg==
dependencies:
"@babel/code-frame" "^7.0.0"
jest-worker "^24.0.0"
serialize-javascript "^1.6.1"
terser "^3.14.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
rollup-pluginutils@^2.0.1:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "2.3.0"
resolved "https://registry.yarnpkg.com/rollup-pluginutils/-/rollup-pluginutils-2.3.0.tgz#478ace04bd7f6da2e724356ca798214884738fc4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-xB6hsRsjdJdIYWEyYUJy/3ki5g69wrf0luHPGNK3ZSocV6HLNfio59l3dZ3TL4xUwEKgROhFi9jOCt6c5gfUWw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
estree-walker "^0.5.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
micromatch "^2.3.11"
build: update to nodejs rules 0.27 (#29210) PR Close #29210
2019-03-14 22:35:00 -04:00
rollup-pluginutils@^2.3.3:
version "2.4.1"
resolved "https://registry.yarnpkg.com/rollup-pluginutils/-/rollup-pluginutils-2.4.1.tgz#de43ab54965bbf47843599a7f3adceb723de38db"
integrity sha512-wesMQ9/172IJDIW/lYWm0vW0LiKe5Ekjws481R7z9WTRtmO59cqyM/2uUlxvf6yzm/fElFmHUobeQOYz46dZJw==
dependencies:
estree-walker "^0.6.0"
micromatch "^3.1.10"
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
rollup-pluginutils@^2.5.0:
version "2.6.0"
resolved "https://registry.yarnpkg.com/rollup-pluginutils/-/rollup-pluginutils-2.6.0.tgz#203706edd43dfafeaebc355d7351119402fc83ad"
integrity sha512-aGQwspEF8oPKvg37u3p7h0cYNwmJR1sCBMZGZ5b9qy8HGtETknqjzcxrDRrcAnJNXN18lBH4Q9vZYth/p4n8jQ==
dependencies:
estree-walker "^0.6.0"
micromatch "^3.1.10"
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
rollup@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/rollup/-/rollup-1.1.0.tgz#461a7534b55be48aa4a6e6810a1543a5769e75d1"
integrity sha512-NK03gkkOz0CchHBMGomcNqa6U3jLNzHuWK9SI0+1FV475JA6cQxVtjlDcQoKKDNIQ3IwYumIlgoKYDEWUyFBwQ==
dependencies:
"@types/estree" "0.0.39"
"@types/node" "*"
acorn "^6.0.5"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
rollup@~1.11.3:
version "1.11.3"
resolved "https://registry.yarnpkg.com/rollup/-/rollup-1.11.3.tgz#6f436db2a2d6b63f808bf60ad01a177643dedb81"
integrity sha512-81MR7alHcFKxgWzGfG7jSdv+JQxSOIOD/Fa3iNUmpzbd7p+V19e1l9uffqT8/7YAHgGOzmoPGN3Fx3L2ptOf5g==
dependencies:
"@types/estree" "0.0.39"
"@types/node" "^11.13.9"
acorn "^6.1.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
router@^1.3.1:
version "1.3.3"
resolved "https://registry.yarnpkg.com/router/-/router-1.3.3.tgz#c142f6b5ea4d6b3359022ca95b6580bd217f89cf"
integrity sha1-wUL2tepNazNZAiypW2WAvSF/ic8=
dependencies:
array-flatten "2.1.1"
debug "2.6.9"
methods "~1.1.2"
parseurl "~1.3.2"
path-to-regexp "0.1.7"
setprototypeof "1.1.0"
utils-merge "1.0.1"
rsvp@^3.6.2:
version "3.6.2"
resolved "https://registry.yarnpkg.com/rsvp/-/rsvp-3.6.2.tgz#2e96491599a96cde1b515d5674a8f7a91452926a"
integrity sha512-OfWGQTb9vnwRjwtA2QwpG2ICclHC3pgXZO5xt8H2EfgDquO0qVdSb5T88L4qJVAEugbS56pAuV4XZM58UX8ulw==
run-async@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/run-async/-/run-async-0.1.0.tgz#c8ad4a5e110661e402a7d21b530e009f25f8e389"
integrity sha1-yK1KXhEGYeQCp9IbUw4AnyX444k=
dependencies:
once "^1.3.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
run-async@^2.2.0:
version "2.3.0"
resolved "https://registry.yarnpkg.com/run-async/-/run-async-2.3.0.tgz#0371ab4ae0bdd720d4166d7dfda64ff7a445a6c0"
integrity sha1-A3GrSuC91yDUFm19/aZP96RFpsA=
dependencies:
is-promise "^2.1.0"
run-queue@^1.0.0, run-queue@^1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/run-queue/-/run-queue-1.0.3.tgz#e848396f057d223f24386924618e25694161ec47"
integrity sha1-6Eg5bwV9Ij8kOGkkYY4laUFh7Ec=
dependencies:
aproba "^1.1.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
rx-lite@^3.1.2:
version "3.1.2"
resolved "https://registry.yarnpkg.com/rx-lite/-/rx-lite-3.1.2.tgz#19ce502ca572665f3b647b10939f97fd1615f102"
integrity sha1-Gc5QLKVyZl87ZHsQk5+X/RYV8QI=
build: update angular cli packages to latest beta (#29720) PR Close #29720
2019-04-05 02:38:16 -04:00
rxjs@6.4.0, rxjs@^6.4.0:
build(bazel): do not build rxjs from source under Bazel (#28720) PR Close #28720
2019-02-13 19:31:29 -05:00
version "6.4.0"
resolved "https://registry.yarnpkg.com/rxjs/-/rxjs-6.4.0.tgz#f3bb0fe7bda7fb69deac0c16f17b50b0b8790504"
integrity sha512-Z9Yfa11F6B9Sg/BK9MnqnQ+aQYicPLtilXBp2yUtDt2JRCE0h26d33EnfO3ZxoNxG0T92OUucP3Ct7cpfkdFfw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
feat(core): upgrade rxjs to 6.0.0-alpha.4 (#22573) PR Close #22573
2018-02-27 17:06:06 -05:00
tslib "^1.9.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update rxjs to 6.5.3 (#32812) PR Close #32812
2019-09-23 04:44:21 -04:00
rxjs@^6.5.3:
version "6.5.3"
resolved "https://registry.yarnpkg.com/rxjs/-/rxjs-6.5.3.tgz#510e26317f4db91a7eb1de77d9dd9ba0a4899a3a"
integrity sha512-wuYsAYYFdWTAnAaPoKGNhfpWwKZbJW+HgAJ+mImp+Epl7BG8oNWBCTyRM8gba9k4lk8BgWdoYm21Mo/RYhhbgA==
dependencies:
tslib "^1.9.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
safe-buffer@5.1.2, safe-buffer@^5.0.1, safe-buffer@^5.1.1, safe-buffer@^5.1.2, safe-buffer@~5.1.0, safe-buffer@~5.1.1:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "5.1.2"
resolved "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.1.2.tgz#991ec69d296e0313747d59bdfd2b745c35f8828d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
safe-regex@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/safe-regex/-/safe-regex-1.1.0.tgz#40a3669f3b077d1e943d44629e157dd48023bf2e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-QKNmnzsHfR6UPURinhV91IAjvy4=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
ret "~0.1.10"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
"safer-buffer@>= 2.1.2 < 3", safer-buffer@^2.0.2:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "2.1.2"
resolved "https://registry.yarnpkg.com/safer-buffer/-/safer-buffer-2.1.2.tgz#44fa161b0187b9549dd84bb91802f9bd8385cd6a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
sauce-connect-launcher@^1.2.4:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.2.4"
resolved "https://registry.yarnpkg.com/sauce-connect-launcher/-/sauce-connect-launcher-1.2.4.tgz#8d38f85242a9fbede1b2303b559f7e20c5609a1c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-X2vfwulR6brUGiicXKxPm1GJ7dBEeP1II450Uv4bHGrcGOapZNgzJvn9aioea5IC5BPp/7qjKdE3xbbTBIVXMA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
adm-zip "~0.4.3"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
async "^2.1.2"
https-proxy-agent "^2.2.1"
lodash "^4.16.6"
rimraf "^2.5.4"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: downgrade to sauce-connect v4.5.1 (#28659) We currently face a lot of flakiness with our Saucelabs CI jobs. These randomly exceed the 10min CircleCI no-output limit because something throws off `sauce-connect` in a long-lasting loop where it tries to connect to some of their Saucelabs servers. The initial assumption from the Saucelabs team was that we might have some invalid firewall rules, but this does not answer why this happens _randomly_, so the latest update from the support is that there have been some changes in the latest version of `sauce-connect` version that **could** cause this flakiness. I've manually did multiple test runs and was only able to reproduce the issues with v4.5.3 (latest version), so it might be worth downgrading to v4.5.1. This is also what the Saucelabs support proposed us to do (though it's not guaranteed that v4.5.1 is unaffected by the same issue) PR Close #28659
2019-02-12 12:36:28 -05:00
"sauce-connect@https://saucelabs.com/downloads/sc-4.5.1-linux.tar.gz":
ci: move local and saucelabs unit tests to circle (#27937) Moving the tests over to CircleCI in pretty much "as-is" state just so that we can drop the dependency on Travis. In the followup changes we plan to migrate these tests to run on sauce under bazel. @gregmagolan is working on that. I've previously verified that all the tests executed in legacy-unit-tests-local already under bazel. Therefore the legacy-unit-tests-local job is strictly not necessary any more, but given how flaky legacy-unit-tests-saucelabs is, it is good to have the -local job just so that we can quickly determine if any failure is a flake or legit issue (the bazel version of these tests could theoretically run in a slightly different way and fail or not fail in a different way, so having -lcoal job is just an extra safety check). This change was coauthored with @devversion PR Close #27937
2019-01-04 14:58:33 -05:00
version "0.0.0"
ci: downgrade to sauce-connect v4.5.1 (#28659) We currently face a lot of flakiness with our Saucelabs CI jobs. These randomly exceed the 10min CircleCI no-output limit because something throws off `sauce-connect` in a long-lasting loop where it tries to connect to some of their Saucelabs servers. The initial assumption from the Saucelabs team was that we might have some invalid firewall rules, but this does not answer why this happens _randomly_, so the latest update from the support is that there have been some changes in the latest version of `sauce-connect` version that **could** cause this flakiness. I've manually did multiple test runs and was only able to reproduce the issues with v4.5.3 (latest version), so it might be worth downgrading to v4.5.1. This is also what the Saucelabs support proposed us to do (though it's not guaranteed that v4.5.1 is unaffected by the same issue) PR Close #28659
2019-02-12 12:36:28 -05:00
resolved "https://saucelabs.com/downloads/sc-4.5.1-linux.tar.gz#5ca9328724c5ff16b12ea49e7a748d44f7305be5"
ci: move local and saucelabs unit tests to circle (#27937) Moving the tests over to CircleCI in pretty much "as-is" state just so that we can drop the dependency on Travis. In the followup changes we plan to migrate these tests to run on sauce under bazel. @gregmagolan is working on that. I've previously verified that all the tests executed in legacy-unit-tests-local already under bazel. Therefore the legacy-unit-tests-local job is strictly not necessary any more, but given how flaky legacy-unit-tests-saucelabs is, it is good to have the -local job just so that we can quickly determine if any failure is a flake or legit issue (the bazel version of these tests could theoretically run in a slightly different way and fail or not fail in a different way, so having -lcoal job is just an extra safety check). This change was coauthored with @devversion PR Close #27937
2019-01-04 14:58:33 -05:00
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
saucelabs@^1.5.0:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.5.0"
resolved "https://registry.yarnpkg.com/saucelabs/-/saucelabs-1.5.0.tgz#9405a73c360d449b232839919a86c396d379fd9d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-jlX3FGdWvYf4Q3LFfFWS1QvPg3IGCGWxIc8QBFdPTbpTJnt/v17FHXYVAn7C8sHf1yUXo2c7yIM0isDryfYtHQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
https-proxy-agent "^2.2.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
sax@>=0.6.0, sax@^1.2.4:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.2.4"
resolved "https://registry.yarnpkg.com/sax/-/sax-1.2.4.tgz#2816234e2378bddc4e5354fab5caa895df7100d9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-NqVDv9TpANUjFm0N8uM5GxL36UgKi9/atZw+x7YFnQ8ckwFGKrl4xX4yWtrey3UJm5nP1kUbnYgLopqWNSRhWw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
selenium-webdriver@3.5.0:
version "3.5.0"
resolved "https://registry.yarnpkg.com/selenium-webdriver/-/selenium-webdriver-3.5.0.tgz#9036c82874e6c0f5cbff0a0f18223bc31c99cb77"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-1bCZYRfDy7vsu1dkLrclTLvWPxSo6rOIkxZXvB2wnzeWkEoiTKpw612EUGA3jRZxPzAzI9OlxuULJV8ge1vVXQ==
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
jszip "^3.1.3"
rimraf "^2.5.4"
tmp "0.0.30"
xml2js "^0.4.17"
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
selenium-webdriver@3.6.0, selenium-webdriver@^3.0.1:
version "3.6.0"
resolved "https://registry.yarnpkg.com/selenium-webdriver/-/selenium-webdriver-3.6.0.tgz#2ba87a1662c020b8988c981ae62cb2a01298eafc"
integrity sha512-WH7Aldse+2P5bbFBO4Gle/nuQOdVwpHMTL6raL3uuBj/vPG07k6uzt3aiahu352ONBr5xXh0hDlM3LhtXPOC4Q==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
jszip "^3.1.3"
rimraf "^2.5.4"
tmp "0.0.30"
xml2js "^0.4.17"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to latest karma-sauce-launcher version (#27634) PR Close #27634
2018-12-12 17:07:21 -05:00
selenium-webdriver@^4.0.0-alpha.1:
version "4.0.0-alpha.1"
resolved "https://registry.yarnpkg.com/selenium-webdriver/-/selenium-webdriver-4.0.0-alpha.1.tgz#cc93415e21d2dc1dfd85dfc5f6b55f3ac53933b1"
integrity sha512-z88rdjHAv3jmTZ7KSGUkTvo4rGzcDGMq0oXWHNIDK96Gs31JKVdu9+FMtT4KBrVoibg8dUicJDok6GnqqttO5Q==
dependencies:
jszip "^3.1.3"
rimraf "^2.5.4"
tmp "0.0.30"
xml2js "^0.4.17"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
semver-diff@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/semver-diff/-/semver-diff-2.1.0.tgz#4bbb8437c8d37e4b0cf1a68fd726ec6d645d6d36"
integrity sha1-S7uEN8jTfksM8aaP1ybsbWRdbTY=
dependencies:
semver "^5.0.3"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
semver-intersect@1.4.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/semver-intersect/-/semver-intersect-1.4.0.tgz#bdd9c06bedcdd2fedb8cd352c3c43ee8c61321f3"
integrity sha512-d8fvGg5ycKAq0+I6nfWeCx6ffaWJCsBYU0H2Rq56+/zFePYfT8mXkB3tWBSjR5BerkHNZ5eTPIk1/LBYas35xQ==
dependencies:
semver "^5.0.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
"semver@2 || 3 || 4", semver@^4.1.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "4.3.6"
resolved "https://registry.yarnpkg.com/semver/-/semver-4.3.6.tgz#300bc6e0e86374f7ba61068b5b1ecd57fc6532da"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-MAvG4OhjdPe6YQaLWx7NV/xlMto=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
"semver@2 || 3 || 4 || 5", semver@5.6.0, semver@^5.0.0, semver@^5.0.1, semver@^5.0.3, semver@^5.1.0, semver@^5.3.0, semver@^5.4.1, semver@^5.5.0, semver@^5.6.0:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "5.6.0"
resolved "https://registry.yarnpkg.com/semver/-/semver-5.6.0.tgz#7e74256fbaa49c75aa7c7a205cc22799cac80004"
integrity sha512-RS9R6R35NYgQn++fkDWaOmqGoj4Ek9gGs+DPxNUZKuwE183xjJroKvyo1IzVFeXvUrvmALy6FWD5xrdJT25gMg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
semver@5.1.0:
version "5.1.0"
resolved "https://registry.yarnpkg.com/semver/-/semver-5.1.0.tgz#85f2cf8550465c4df000cf7d86f6b054106ab9e5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-hfLPhVBGXE3wAM99hvawVBBqueU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
semver@5.4.1:
version "5.4.1"
resolved "https://registry.yarnpkg.com/semver/-/semver-5.4.1.tgz#e059c09d8571f0540823733433505d3a2f00b18e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-WfG/X9+oATh81XtllIo/I8gOiY9EXRdv1cQdyykeXK17YcUW3EXUAi2To4pcH6nZtJPr7ZOpM5OMyWJZm+8Rsg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
semver@5.5.0:
version "5.5.0"
resolved "https://registry.yarnpkg.com/semver/-/semver-5.5.0.tgz#dc4bbc7a6ca9d916dee5d43516f0092b58f7b8ab"
integrity sha512-4SJ3dm0WAwWy/NVeioZh5AntkdJoWKxHxcmyP622fOkgHa4z3R0TdBJICINyaSDE6uNwVc8gZr+ZinwZAH4xIA==
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
semver@6.0.0:
version "6.0.0"
resolved "https://registry.yarnpkg.com/semver/-/semver-6.0.0.tgz#05e359ee571e5ad7ed641a6eec1e547ba52dea65"
integrity sha512-0UewU+9rFapKFnlbirLi3byoOuhrSsli/z/ihNnvM24vgF+8sNBiI1LZPBSH9wJKUwaUbw+s3hToDLCXkrghrQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
semver@~5.0.1:
version "5.0.3"
resolved "https://registry.yarnpkg.com/semver/-/semver-5.0.3.tgz#77466de589cd5d3c95f138aa78bc569a3cb5d27a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-d0Zt5YnNXTyV8TiqeLxWmjy10no=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
send@0.13.2:
version "0.13.2"
resolved "https://registry.yarnpkg.com/send/-/send-0.13.2.tgz#765e7607c8055452bba6f0b052595350986036de"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-dl52B8gFVFK7pvCwUllTUJhgNt4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
debug "~2.2.0"
depd "~1.1.0"
destroy "~1.0.4"
escape-html "~1.0.3"
etag "~1.7.0"
fresh "0.3.0"
http-errors "~1.3.1"
mime "1.3.4"
ms "0.7.1"
on-finished "~2.3.0"
range-parser "~1.0.3"
statuses "~1.2.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
send@0.16.2:
version "0.16.2"
resolved "https://registry.yarnpkg.com/send/-/send-0.16.2.tgz#6ecca1e0f8c156d141597559848df64730a6bbc1"
integrity sha512-E64YFPUssFHEFBvpbbjr44NCLtI1AohxQ8ZSiJjQLskAdKuriYEP6VyGEsRDH8ScozGpkaX1BGvhanqCwkcEZw==
dependencies:
debug "2.6.9"
depd "~1.1.2"
destroy "~1.0.4"
encodeurl "~1.0.2"
escape-html "~1.0.3"
etag "~1.8.1"
fresh "0.5.2"
http-errors "~1.6.2"
mime "1.4.1"
ms "2.0.0"
on-finished "~2.3.0"
range-parser "~1.2.0"
statuses "~1.4.0"
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
seq@^0.3.5:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.3.5"
resolved "https://registry.yarnpkg.com/seq/-/seq-0.3.5.tgz#ae02af3a424793d8ccbf212d69174e0c54dffe38"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-rgKvOkJHk9jMvyEtaRdODFTf/jg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
chainsaw ">=0.0.7 <0.1"
hashish ">=0.0.2 <0.1"
sequencify@~0.0.7:
version "0.0.7"
resolved "https://registry.yarnpkg.com/sequencify/-/sequencify-0.0.7.tgz#90cff19d02e07027fd767f5ead3e7b95d1e7380c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-kM/xnQLgcCf9dn9erT57ldHnOAw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
serialize-javascript@^1.6.1:
version "1.7.0"
resolved "https://registry.yarnpkg.com/serialize-javascript/-/serialize-javascript-1.7.0.tgz#d6e0dfb2a3832a8c94468e6eb1db97e55a192a65"
integrity sha512-ke8UG8ulpFOxO8f8gRYabHQe/ZntKlcig2Mp+8+URDP1D8vJZ0KUt7LYo07q25Z/+JVSgpr/cui9PIp5H6/+nA==
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
serializerr@1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/serializerr/-/serializerr-1.0.3.tgz#12d4c5aa1c3ffb8f6d1dc5f395aa9455569c3f91"
integrity sha1-EtTFqhw/+49tHcXzlaqUVVacP5E=
dependencies:
protochain "^1.0.5"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
serve-favicon@~2.3.0:
version "2.3.2"
resolved "https://registry.yarnpkg.com/serve-favicon/-/serve-favicon-2.3.2.tgz#dd419e268de012ab72b319d337f2105013f9381f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-3UGeJo3gEqtysxnTN/IQUBP5OB8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
etag "~1.7.0"
fresh "0.3.0"
ms "0.7.2"
parseurl "~1.3.1"
serve-index@~1.7.2:
version "1.7.3"
resolved "https://registry.yarnpkg.com/serve-index/-/serve-index-1.7.3.tgz#7a057fc6ee28dc63f64566e5fa57b111a86aecd2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-egV/xu4o3GP2RWbl+lexEahq7NI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
accepts "~1.2.13"
batch "0.5.3"
debug "~2.2.0"
escape-html "~1.0.3"
http-errors "~1.3.1"
mime-types "~2.1.9"
parseurl "~1.3.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
serve-static@1.13.2:
version "1.13.2"
resolved "https://registry.yarnpkg.com/serve-static/-/serve-static-1.13.2.tgz#095e8472fd5b46237db50ce486a43f4b86c6cec1"
integrity sha512-p/tdJrO4U387R9oMjb1oj7qSMaMfmOyd4j9hOFoxZe2baQszgHcSWjuya/CiT5kgZZKRudHNOA0pYXOl8rQ5nw==
dependencies:
encodeurl "~1.0.2"
escape-html "~1.0.3"
parseurl "~1.3.2"
send "0.16.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
serve-static@~1.10.0:
version "1.10.3"
resolved "https://registry.yarnpkg.com/serve-static/-/serve-static-1.10.3.tgz#ce5a6ecd3101fed5ec09827dac22a9c29bfb0535"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-zlpuzTEB/tXsCYJ9rCKpwpv7BTU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
escape-html "~1.0.3"
parseurl "~1.3.1"
send "0.13.2"
set-blocking@^2.0.0, set-blocking@~2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/set-blocking/-/set-blocking-2.0.0.tgz#045f9782d011ae9a6803ddd382b24392b3d890f7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-BF+XgtARrppoA93TgrJDkrPYkPc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
set-value@^0.4.3:
version "0.4.3"
resolved "https://registry.yarnpkg.com/set-value/-/set-value-0.4.3.tgz#7db08f9d3d22dc7f78e53af3c3bf4666ecdfccf1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-fbCPnT0i3H945Trzw79GZuzfzPE=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
extend-shallow "^2.0.1"
is-extendable "^0.1.1"
is-plain-object "^2.0.1"
to-object-path "^0.3.0"
set-value@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/set-value/-/set-value-2.0.0.tgz#71ae4a88f0feefbbf52d1ea604f3fb315ebb6274"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-hw0yxk9GT/Hr5yJEYnHNKYXkIA8mVJgd9ditYZCe16ZczcaELYYcfvaXesNACk2O8O0nTiPQcQhGUQj8JLzeeg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
extend-shallow "^2.0.1"
is-extendable "^0.1.1"
is-plain-object "^2.0.3"
split-string "^3.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"setimmediate@>= 1.0.1 < 2", "setimmediate@>= 1.0.2 < 2":
version "1.0.5"
resolved "https://registry.yarnpkg.com/setimmediate/-/setimmediate-1.0.5.tgz#290cbb232e306942d7d7ea9b83732ab7856f8285"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-KQy7Iy4waULX1+qbg3Mqt4VvgoU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
setprototypeof@1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/setprototypeof/-/setprototypeof-1.1.0.tgz#d0bd85536887b6fe7c0d818cb962d9d91c54e656"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-BvE/TwpZX4FXExxOxZyRGQQv651MSwmWKZGqvmPcRIjDqWub67kTKuIMx43cZZrS/cBBzwBcNDWoFxt2XEFIpQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
sha.js@2.2.6:
version "2.2.6"
resolved "https://registry.yarnpkg.com/sha.js/-/sha.js-2.2.6.tgz#17ddeddc5f722fb66501658895461977867315ba"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-F93t3F9yL7ZlAWWIlUYZd4ZzFbo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
shebang-command@^1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/shebang-command/-/shebang-command-1.2.0.tgz#44aac65b695b03398968c39f363fee5deafdf1ea"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-RKrGW2lbAzmJaMOfNj/uXer98eo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
shebang-regex "^1.0.0"
shebang-regex@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/shebang-regex/-/shebang-regex-1.0.0.tgz#da42f49740c0b42db2ca9728571cb190c98efea3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-2kL0l0DAtC2yypcoVxyxkMmO/qM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
shell-quote@1.6.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.6.1"
resolved "https://registry.yarnpkg.com/shell-quote/-/shell-quote-1.6.1.tgz#f4781949cce402697127430ea3b3c5476f481767"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-9HgZSczkAmlxJ0MOo7PFR29IF2c=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
array-filter "~0.0.0"
array-map "~0.0.0"
array-reduce "~0.0.0"
jsonify "~0.0.0"
build: add postinstall-patches.js script suitable for postinstall patching of dependencies (#22669) Because sometimes one has to do what one has to do... PR Close #22669
2018-03-08 23:23:33 -05:00
shelljs@^0.8.1:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.8.2"
resolved "https://registry.yarnpkg.com/shelljs/-/shelljs-0.8.2.tgz#345b7df7763f4c2340d584abb532c5f752ca9e35"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-pRXeNrCA2Wd9itwhvLp5LZQvPJ0wU6bcjaTMywHHGX5XWhVN2nzSu7WV0q+oUY7mGK3mgSkDDzP3MgjqdyIgbQ==
ci: validate commit messages correctly when not on master (#19685) PR Close #19685
2017-10-12 07:28:43 -04:00
dependencies:
glob "^7.0.0"
interpret "^1.0.0"
rechoir "^0.6.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
sigmund@~1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/sigmund/-/sigmund-1.0.1.tgz#3ff21f198cad2175f9f3b781853fd94d0d19b590"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-P/IfGYytIXX587eBhT/ZTQ0ZtZA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
sign-addon@0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/sign-addon/-/sign-addon-0.2.0.tgz#c8da20b7afe719d42714142226252358d5b604e9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-yNogt6/nGdQnFBQiJiUjWNW2BOk=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
babel-polyfill "6.16.0"
deepcopy "0.6.3"
es6-error "4.0.0"
es6-promisify "5.0.0"
jsonwebtoken "7.1.9"
mz "2.4.0"
request "2.75.0"
source-map-support "0.4.3"
stream-to-promise "2.2.0"
when "3.7.7"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
signal-exit@^3.0.0, signal-exit@^3.0.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "3.0.2"
resolved "https://registry.yarnpkg.com/signal-exit/-/signal-exit-3.0.2.tgz#b5fdc08f1287ea1178628e415e25132b73646c6d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-tf3AjxKH6hF4Yo5BXiUTK3NkbG0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"slice-stream@>= 1.0.0 < 2":
version "1.0.0"
resolved "https://registry.yarnpkg.com/slice-stream/-/slice-stream-1.0.0.tgz#5b33bd66f013b1a7f86460b03d463dec39ad3ea0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-WzO9ZvATsaf4ZGCwPUY97DmtPqA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
readable-stream "~1.0.31"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
slide@^1.1.5:
version "1.1.6"
resolved "https://registry.yarnpkg.com/slide/-/slide-1.1.6.tgz#56eb027d65b4d2dce6cb2e2d32c4d4afc9e1d707"
integrity sha1-VusCfWW00tzmyy4tMsTUr8nh1wc=
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
smart-buffer@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/smart-buffer/-/smart-buffer-4.0.1.tgz#07ea1ca8d4db24eb4cac86537d7d18995221ace3"
integrity sha512-RFqinRVJVcCAL9Uh1oVqE6FZkqsyLiVOYEZ20TqIOjuX7iFVJ+zsbs4RIghnw/pTs7mZvt8ZHhvm1ZUrR4fykg==
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
snakeize@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/snakeize/-/snakeize-0.1.0.tgz#10c088d8b58eb076b3229bb5a04e232ce126422d"
integrity sha1-EMCI2LWOsHazIpu1oE4jLOEmQi0=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
snapdragon-node@^2.0.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/snapdragon-node/-/snapdragon-node-2.1.1.tgz#6c175f86ff14bdb0724563e8f3c1b021a286853b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-O27l4xaMYt/RSQ5TR3vpWCAB5Kb/czIcqUFOM/C4fYcLnbZUc1PkjTAMjof2pBWaSTwOUd6qUHcFGVGj7aIwnw==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
define-property "^1.0.0"
isobject "^3.0.0"
snapdragon-util "^3.0.1"
snapdragon-util@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/snapdragon-util/-/snapdragon-util-3.0.1.tgz#f956479486f2acd79700693f6f7b805e45ab56e2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-mbKkMdQKsjX4BAL4bRYTj21edOf8cN7XHdYUJEe+Zn99hVEYcMvKPct1IqNe7+AZPirn8BCDOQBHQZknqmKlZQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
kind-of "^3.2.0"
snapdragon@^0.8.1:
version "0.8.2"
resolved "https://registry.yarnpkg.com/snapdragon/-/snapdragon-0.8.2.tgz#64922e7c565b0e14204ba1aa7d6964278d25182d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-FtyOnWN/wCHTVXOMwvSv26d+ko5vWlIDD6zoUJ7LW8vh+ZBC8QdljveRP+crNrtBwioEUWy/4dMtbBjA4ioNlg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
base "^0.11.1"
debug "^2.2.0"
define-property "^0.2.5"
extend-shallow "^2.0.1"
map-cache "^0.2.2"
source-map "^0.5.6"
source-map-resolve "^0.5.0"
use "^3.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
sntp@1.x.x:
version "1.0.9"
resolved "https://registry.yarnpkg.com/sntp/-/sntp-1.0.9.tgz#6541184cc90aeea6c6e7b35e2659082443c66198"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ZUEYTMkK7qbG57NeJlkIJEPGYZg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
hoek "2.x.x"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
socket.io-adapter@~1.1.0:
version "1.1.1"
resolved "https://registry.yarnpkg.com/socket.io-adapter/-/socket.io-adapter-1.1.1.tgz#2a805e8a14d6372124dd9159ad4502f8cb07f06b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-KoBeihTWNyEk3ZFZrUUC+MsH8Gs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to latest karma version (#27735) Updates to the latest Karma version that includes karma-runner/karma@cc2eff2 and should be able to properly restart disconnected browsers. This was a long-term Karma bug and affected CI flakiness significantly. PR Close #27735
2018-12-18 13:50:48 -05:00
socket.io-client@2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/socket.io-client/-/socket.io-client-2.1.1.tgz#dcb38103436ab4578ddb026638ae2f21b623671f"
integrity sha512-jxnFyhAuFxYfjqIgduQlhzqTcOEQSn+OHKVfAxWaNWa7ecP7xSNk2Dx/3UEsDcY7NcFafxvNvKPmmO7HTwTxGQ==
dependencies:
backo2 "1.0.2"
base64-arraybuffer "0.1.5"
component-bind "1.0.0"
component-emitter "1.2.1"
debug "~3.1.0"
engine.io-client "~3.2.0"
has-binary2 "~1.0.2"
has-cors "1.1.0"
indexof "0.0.1"
object-component "0.0.3"
parseqs "0.0.5"
parseuri "0.0.5"
socket.io-parser "~3.2.0"
to-array "0.1.4"
socket.io-parser@~3.2.0:
version "3.2.0"
resolved "https://registry.yarnpkg.com/socket.io-parser/-/socket.io-parser-3.2.0.tgz#e7c6228b6aa1f814e6148aea325b51aa9499e077"
integrity sha512-FYiBx7rc/KORMJlgsXysflWx/RIvtqZbyGLlHZvjfmPTPeuD/I8MaW7cfFrj5tRltICJdgwflhfZ3NVVbVLFQA==
dependencies:
component-emitter "1.2.1"
debug "~3.1.0"
isarray "2.0.1"
socket.io@2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/socket.io/-/socket.io-2.1.1.tgz#a069c5feabee3e6b214a75b40ce0652e1cfb9980"
integrity sha512-rORqq9c+7W0DAK3cleWNSyfv/qKXV99hV4tZe+gGLfBECw3XEhBy7x85F3wypA9688LKjtwO9pX9L33/xQI8yA==
dependencies:
debug "~3.1.0"
engine.io "~3.2.0"
has-binary2 "~1.0.2"
socket.io-adapter "~1.1.0"
socket.io-client "2.1.1"
socket.io-parser "~3.2.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
socks-proxy-agent@^4.0.0:
version "4.0.1"
resolved "https://registry.yarnpkg.com/socks-proxy-agent/-/socks-proxy-agent-4.0.1.tgz#5936bf8b707a993079c6f37db2091821bffa6473"
integrity sha512-Kezx6/VBguXOsEe5oU3lXYyKMi4+gva72TwJ7pQY5JfqUx2nMk7NXA6z/mpNqIlfQjWYVfeuNvQjexiTaTn6Nw==
dependencies:
agent-base "~4.2.0"
socks "~2.2.0"
socks@~2.2.0:
version "2.2.2"
resolved "https://registry.yarnpkg.com/socks/-/socks-2.2.2.tgz#f061219fc2d4d332afb4af93e865c84d3fa26e2b"
integrity sha512-g6wjBnnMOZpE0ym6e0uHSddz9p3a+WsBaaYQaBaSCJYvrC4IXykQR9MNGjLQf38e9iIIhp3b1/Zk8YZI3KGJ0Q==
dependencies:
ip "^1.1.5"
smart-buffer "^4.0.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
sort-keys@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/sort-keys/-/sort-keys-2.0.0.tgz#658535584861ec97d730d6cf41822e1f56684128"
integrity sha1-ZYU1WEhh7JfXMNbPQYIuH1ZoQSg=
dependencies:
is-plain-obj "^1.0.0"
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
source-list-map@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/source-list-map/-/source-list-map-2.0.1.tgz#3993bd873bfc48479cca9ea3a547835c7c154b34"
integrity sha512-qnQ7gVMxGNxsiL4lEuJwe/To8UnK7fAnmbGEEH8RpLouuKbeEm0lhbQVFIrNSuB+G7tVrAlVsZgETT5nljf+Iw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
source-list-map@~0.1.7:
version "0.1.8"
resolved "https://registry.yarnpkg.com/source-list-map/-/source-list-map-0.1.8.tgz#c550b2ab5427f6b3f21f5afead88c4f5587b2106"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-xVCyq1Qn9rPyH1r+rYjE9Vh7IQY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
source-map-resolve@^0.5.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.5.2"
resolved "https://registry.yarnpkg.com/source-map-resolve/-/source-map-resolve-0.5.2.tgz#72e2cc34095543e43b2c62b2c4c10d4a9054f259"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-MjqsvNwyz1s0k81Goz/9vRBe9SZdB09Bdw+/zYyO+3CuPk6fouTaxscHkgtE8jKvf01kVfl8riHzERQ/kefaSA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
atob "^2.1.1"
decode-uri-component "^0.2.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
resolve-url "^0.2.1"
source-map-url "^0.4.0"
urix "^0.1.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
source-map-support@0.4.3:
version "0.4.3"
resolved "https://registry.yarnpkg.com/source-map-support/-/source-map-support-0.4.3.tgz#693c8383d4389a4569486987c219744dfc601685"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-aTyDg9Q4mkVpSGmHwhl0TfxgFoU=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
source-map "^0.5.3"
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
source-map-support@0.5.9:
version "0.5.9"
resolved "https://registry.yarnpkg.com/source-map-support/-/source-map-support-0.5.9.tgz#41bc953b2534267ea2d605bccfa7bfa3111ced5f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-gR6Rw4MvUlYy83vP0vxoVNzM6t8MUXqNuRsuBmBHQDu1Fh6X015FrLdgoDKcNdkwGubozq0P4N0Q37UyFVr1EA==
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
dependencies:
buffer-from "^1.0.0"
source-map "^0.6.0"
build: update source-map-support to get rid of Node's DeprecationWarning (#27538) Removes the following when bazel runs any of our jasmine_node_tests: (node:85494) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. I was able to find the source of the warning by running the target with the following tags: ``` bazel test packages/language-service/... --test_arg=--node_options=--throw-deprecation ``` PR Close #27538
2018-12-07 03:20:32 -05:00
source-map-support@~0.4.0:
version "0.4.18"
resolved "https://registry.yarnpkg.com/source-map-support/-/source-map-support-0.4.18.tgz#0286a6de8be42641338594e97ccea75f0a2c585f"
integrity sha512-try0/JqxPLF9nOjvSta7tVondkP5dwgyLDjVoyMDlmjugT2lRZ1OfsrYTkCd2hkDnJTKRbO/Rl3orm8vlsUzbA==
dependencies:
source-map "^0.5.6"
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
source-map-support@~0.5.10:
version "0.5.12"
resolved "https://registry.yarnpkg.com/source-map-support/-/source-map-support-0.5.12.tgz#b4f3b10d51857a5af0138d3ce8003b201613d599"
integrity sha512-4h2Pbvyy15EE02G+JOZpUCmqWJuqrs+sEkzewTm++BPi7Hvn/HwcqLAcNxYAyI0x13CpPPn+kMjl+hplXMHITQ==
dependencies:
buffer-from "^1.0.0"
source-map "^0.6.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
source-map-url@^0.4.0:
version "0.4.0"
resolved "https://registry.yarnpkg.com/source-map-url/-/source-map-url-0.4.0.tgz#3e935d7ddd73631b97659956d55128e87b5084a3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-PpNdfd1zYxuXZZlW1VEo6HtQhKM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
source-map@0.1.31:
version "0.1.31"
resolved "https://registry.yarnpkg.com/source-map/-/source-map-0.1.31.tgz#9f704d0d69d9e138a81badf6ebb4fde33d151c61"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-n3BNDWnZ4TioG63267T94z0VHGE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
amdefine ">=0.0.4"
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
source-map@0.5.6:
version "0.5.6"
resolved "https://registry.yarnpkg.com/source-map/-/source-map-0.5.6.tgz#75ce38f52bf0733c5a7f0c118d81334a2bb5f412"
integrity sha1-dc449SvwczxafwwRjYEzSiu19BI=
build: remove redundant `@types/source-map` dependency (#31468) In version 0.6.1 that we are using, `source-map` ships with [its own typings][1], so there is no need to use `@types/source-map`. The types were even removed from `DefinitelyTyped` in DefinitelyTyped/DefinitelyTyped@1792bfaa2. [1]: https://github.com/mozilla/source-map/blob/0.6.1/package.json#L72 PR Close #31468
2019-07-09 10:40:20 -04:00
source-map@0.7.3, source-map@^0.7.3:
version "0.7.3"
resolved "https://registry.yarnpkg.com/source-map/-/source-map-0.7.3.tgz#5302f8169031735226544092e64981f751750383"
integrity sha512-CkCj6giN3S+n9qrYiBTX5gystlENnRW5jZeNLHpe6aue+SrHcG5VYwujhW9s4dY31mEGsxBDrHR6oI69fTXsaQ==
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
source-map@^0.4.4, source-map@~0.4.1:
version "0.4.4"
resolved "https://registry.yarnpkg.com/source-map/-/source-map-0.4.4.tgz#eba4f5da9c0dc999de68032d8b4f76173652036b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-66T12pwNyZneaAMti092FzZSA2s=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
amdefine ">=0.0.4"
build: add dependencies to be used by ngcc (#24897) PR Close #24897
2018-07-16 02:08:48 -04:00
source-map@^0.5.3, source-map@^0.5.6, source-map@~0.5.0, source-map@~0.5.1:
version "0.5.7"
resolved "https://registry.yarnpkg.com/source-map/-/source-map-0.5.7.tgz#8a039d2d1021d22d1ea14c80d8ea468ba2ef3fcc"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-igOdLRAh0i0eoUyA2OpGi6LvP8w=
build: add dependencies to be used by ngcc (#24897) PR Close #24897
2018-07-16 02:08:48 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
source-map@^0.6.0, source-map@^0.6.1, source-map@~0.6.1:
build: switch from uglify-js to uglify-es (#22669) This enables us to minify ES2015 code. PR Close #22669
2018-03-10 00:01:53 -05:00
version "0.6.1"
resolved "https://registry.yarnpkg.com/source-map/-/source-map-0.6.1.tgz#74722af32e9614e9c287a8d0bbde48b5e2f1a263"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==
build: switch from uglify-js to uglify-es (#22669) This enables us to minify ES2015 code. PR Close #22669
2018-03-10 00:01:53 -05:00
build: add dependencies to be used by ngcc (#24897) PR Close #24897
2018-07-16 02:08:48 -04:00
sourcemap-codec@^1.4.1:
version "1.4.1"
resolved "https://registry.yarnpkg.com/sourcemap-codec/-/sourcemap-codec-1.4.1.tgz#c8fd92d91889e902a07aee392bdd2c5863958ba2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-hX1eNBNuilj8yfFnECh0DzLgwKpBLMIvmhgEhixXNui8lMLBInTI8Kyxt++RwJnMNu7cAUo635L2+N1TxMJCzA==
build: add dependencies to be used by ngcc (#24897) PR Close #24897
2018-07-16 02:08:48 -04:00
build: update to nodejs rules 0.27 (#29210) PR Close #29210
2019-03-14 22:35:00 -04:00
sourcemap-codec@^1.4.4:
version "1.4.4"
resolved "https://registry.yarnpkg.com/sourcemap-codec/-/sourcemap-codec-1.4.4.tgz#c63ea927c029dd6bd9a2b7fa03b3fec02ad56e9f"
integrity sha512-CYAPYdBu34781kLHkaW3m6b/uUSyMOC2R61gcYMWooeuaGtjof86ZA/8T+qVPPt7np1085CR9hmMGrySwEc8Xg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
sparkles@^1.0.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/sparkles/-/sparkles-1.0.1.tgz#008db65edce6c50eec0c5e228e1945061dd0437c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-dSO0DDYUahUt/0/pD/Is3VIm5TGJjludZ0HVymmhYF6eNA53PVLhnUk0znSYbH8IYBuJdCE+1luR22jNLMaQdw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
spawn-sync@1.0.15:
version "1.0.15"
resolved "https://registry.yarnpkg.com/spawn-sync/-/spawn-sync-1.0.15.tgz#b00799557eb7fb0c8376c29d44e8a1ea67e57476"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-sAeZVX63+wyDdsKdROih6mfldHY=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
concat-stream "^1.4.7"
os-shim "^0.1.2"
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
spawn-wrap@^1.4.2:
version "1.4.2"
resolved "https://registry.yarnpkg.com/spawn-wrap/-/spawn-wrap-1.4.2.tgz#cff58e73a8224617b6561abdc32586ea0c82248c"
integrity sha512-vMwR3OmmDhnxCVxM8M+xO/FtIp6Ju/mNaDfCMMW7FDcLRTPFWUswec4LXJHTJE2hwTI9O0YBfygu4DalFl7Ylg==
dependencies:
foreground-child "^1.5.6"
mkdirp "^0.5.0"
os-homedir "^1.0.1"
rimraf "^2.6.2"
signal-exit "^3.0.2"
which "^1.3.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
spdx-correct@^3.0.0:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "3.1.0"
resolved "https://registry.yarnpkg.com/spdx-correct/-/spdx-correct-3.1.0.tgz#fb83e504445268f154b074e218c87c003cd31df4"
integrity sha512-lr2EZCctC2BNR7j7WzJ2FpDznxky1sjfxvvYEyzxNyb6lZXHODmEoJeFu4JupYlkfha1KZpJyoqiJ7pgA1qq8Q==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
spdx-expression-parse "^3.0.0"
spdx-license-ids "^3.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
spdx-exceptions@^2.1.0:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/spdx-exceptions/-/spdx-exceptions-2.2.0.tgz#2ea450aee74f2a89bfb94519c07fcd6f41322977"
integrity sha512-2XQACfElKi9SlVb1CYadKDXvoajPgBVPn/gOQLrTvHdElaVhr7ZEbqJaRnJLVNeaI4cMEAgVCeBMKF6MWRDCRA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
spdx-expression-parse@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/spdx-expression-parse/-/spdx-expression-parse-3.0.0.tgz#99e119b7a5da00e05491c9fa338b7904823b41d0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-Yg6D3XpRD4kkOmTpdgbUiEJFKghJH03fiC1OPll5h/0sO6neh2jqRDVHOQ4o/LMea0tgCkbMgea5ip/e+MkWyg==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
spdx-exceptions "^2.1.0"
spdx-license-ids "^3.0.0"
spdx-license-ids@^3.0.0:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "3.0.3"
resolved "https://registry.yarnpkg.com/spdx-license-ids/-/spdx-license-ids-3.0.3.tgz#81c0ce8f21474756148bbb5f3bfc0f36bf15d76e"
integrity sha512-uBIcIl3Ih6Phe3XHK1NqboJLdGfwr1UN3k6wSD1dZpmPsIkb8AGNbZYJ1fOBk834+Gxy8rpfDxrS6XLEMZMY2g==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
split-array-stream@^1.0.0:
version "1.0.3"
resolved "https://registry.yarnpkg.com/split-array-stream/-/split-array-stream-1.0.3.tgz#d2b75a8e5e0d824d52fdec8b8225839dc2e35dfa"
integrity sha1-0rdajl4Ngk1S/eyLgiWDncLjXfo=
dependencies:
async "^2.4.0"
is-stream-ended "^0.1.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
split-string@^3.0.1, split-string@^3.0.2:
version "3.1.0"
resolved "https://registry.yarnpkg.com/split-string/-/split-string-3.1.0.tgz#7cb09dda3a86585705c64b39a6466038682e8fe2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-NzNVhJDYpwceVVii8/Hu6DKfD2G+NrQHlS/V/qgv763EYudVwEcMQNxd2lh+0VrUByXN/oJkl5grOhYWvQUYiw==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
extend-shallow "^3.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
split2@^2.0.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/split2/-/split2-2.2.0.tgz#186b2575bcf83e85b7d18465756238ee4ee42493"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-RAb22TG39LhI31MbreBgIuKiIKhVsawfTgEGqKHTK87aG+ul/PB8Sqoi3I7kVdRWiCfrKxK3uo4/YUkpNvhPbw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
through2 "^2.0.2"
split@0.3:
version "0.3.3"
resolved "https://registry.yarnpkg.com/split/-/split-0.3.3.tgz#cd0eea5e63a211dfff7eb0f091c4133e2d0dd28f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-zQ7qXmOiEd//frDwkcQTPi0N0o8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
through "2"
split@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/split/-/split-1.0.1.tgz#605bd9be303aa59fb35f9229fbea0ddec9ea07d9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-mTyOoPbrivtXnwnIxZRFYRrPNtEFKlpB2fvjSnCQUiAA6qAZzqwna5envK4uk6OIeP17CsdF3rSBGYVBsU0Tkg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
through "2"
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
sprintf-js@~1.0.2:
version "1.0.3"
resolved "https://registry.yarnpkg.com/sprintf-js/-/sprintf-js-1.0.3.tgz#04e6926f662895354f3dd015203633b857297e2c"
integrity sha1-BOaSb2YolTVPPdAVIDYzuFcpfiw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
sshpk@^1.7.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.14.2"
resolved "https://registry.yarnpkg.com/sshpk/-/sshpk-1.14.2.tgz#c6fc61648a3d9c4e764fd3fcdf4ea105e492ba98"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-xvxhZIo9nE52T9P8306hBeSSupg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
asn1 "~0.2.3"
assert-plus "^1.0.0"
dashdash "^1.12.0"
getpass "^0.1.1"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
safer-buffer "^2.0.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
optionalDependencies:
bcrypt-pbkdf "^1.0.0"
ecc-jsbn "~0.1.1"
jsbn "~0.1.0"
tweetnacl "~0.14.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
ssri@^6.0.0, ssri@^6.0.1:
version "6.0.1"
resolved "https://registry.yarnpkg.com/ssri/-/ssri-6.0.1.tgz#2a3c41b28dd45b62b63676ecb74001265ae9edd8"
integrity sha512-3Wge10hNcT1Kur4PDFwEieXSCMCJs/7WvSACcrMYrNp+b8kDL1/0wJch5Ni2WrtwEa2IO8OsVfeKIciKCDx/QA==
dependencies:
figgy-pudding "^3.5.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
stack-trace@0.0.x:
version "0.0.10"
resolved "https://registry.yarnpkg.com/stack-trace/-/stack-trace-0.0.10.tgz#547c70b347e8d32b4e108ea1a2a159e5fdde19c0"
integrity sha1-VHxws0fo0ytOEI6hoqFZ5f3eGcA=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
static-extend@^0.1.1:
version "0.1.2"
resolved "https://registry.yarnpkg.com/static-extend/-/static-extend-0.1.2.tgz#60809c39cbff55337226fd5e0b520f341f1fb5c6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-YICcOcv/VTNyJv1eC1IPNB8ftcY=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
define-property "^0.2.5"
object-copy "^0.1.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
statuses@1, "statuses@>= 1.4.0 < 2":
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.5.0"
resolved "https://registry.yarnpkg.com/statuses/-/statuses-1.5.0.tgz#161c7dac177659fd9811f43771fa99381478628c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Fhx9rBd2Wf2YEfQ3cfqZOBR4Yow=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
statuses@~1.2.1:
version "1.2.1"
resolved "https://registry.yarnpkg.com/statuses/-/statuses-1.2.1.tgz#dded45cc18256d51ed40aec142489d5c61026d28"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-3e1FzBglbVHtQK7BQkidXGECbSg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
statuses@~1.3.1:
version "1.3.1"
resolved "https://registry.yarnpkg.com/statuses/-/statuses-1.3.1.tgz#faf51b9eb74aaef3b3acf4ad5f61abf24cb7b93e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+vUbnrdKrvOzrPStX2Gr8ky3uT4=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
statuses@~1.4.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/statuses/-/statuses-1.4.0.tgz#bb73d446da2796106efcc1b601a253d6c46bd087"
integrity sha512-zhSCtt8v2NDrRlPQpCNtw/heZLtfUDqxBM1udqikb/Hbk52LK4nQSwr10u77iopCW5LsyHpuXS0GnEc48mLeew==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
stream-browserify@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/stream-browserify/-/stream-browserify-1.0.0.tgz#bf9b4abfb42b274d751479e44e0ff2656b6f1193"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-v5tKv7QrJ011FHnkTg/yZWtvEZM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
inherits "~2.0.1"
readable-stream "^1.0.27-1"
stream-combiner2@^1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/stream-combiner2/-/stream-combiner2-1.1.1.tgz#fb4d8a1420ea362764e21ad4780397bebcb41cbe"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+02KFCDqNidk4hrUeAOXvry0HL4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
duplexer2 "~0.1.0"
readable-stream "^2.0.2"
stream-combiner@~0.0.4:
version "0.0.4"
resolved "https://registry.yarnpkg.com/stream-combiner/-/stream-combiner-0.0.4.tgz#4d5e433c185261dde623ca3f44c586bcf5c4ad14"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-TV5DPBhSYd3mI8o/RMWGvPXErRQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
duplexer "~0.1.1"
stream-consume@~0.1.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.1.1"
resolved "https://registry.yarnpkg.com/stream-consume/-/stream-consume-0.1.1.tgz#d3bdb598c2bd0ae82b8cac7ac50b1107a7996c48"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-tNa3hzgkjEP7XbCkbRXe1jpg+ievoa0O4SCFlMOYEscGSS4JJsckGL8swUyAa/ApGU3Ae4t6Honor4HhL+tRyg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
stream-counter@~0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/stream-counter/-/stream-counter-0.2.0.tgz#ded266556319c8b0e222812b9cf3b26fa7d947de"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-3tJmVWMZyLDiIoErnPOyb6fZR94=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
readable-stream "~1.1.8"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
stream-each@^1.1.0:
version "1.2.3"
resolved "https://registry.yarnpkg.com/stream-each/-/stream-each-1.2.3.tgz#ebe27a0c389b04fbcc233642952e10731afa9bae"
integrity sha512-vlMC2f8I2u/bZGqkdfLQW/13Zihpej/7PmSiMQsbYddxuTsJp8vRe2x2FvVExZg7FaOds43ROAuFJwPR4MTZLw==
dependencies:
end-of-stream "^1.1.0"
stream-shift "^1.0.0"
build: downgrade `gulp-clang-format` to 1.0.23 (#31295) The `gulp format*` tasks have been broken since 5eb742621. These include the `gulp format:enforce` task, which is what runs on CI to enforce consistent code style. Here is what (I believe) happened: - I assume formatting was failing in 5eb742621 (moving `zone.js` into `angular/angular`). The reason must have been that [this glob pattern][1] matches `packages/zone.js/` (which is a directory) and passes it to `clang-format` claiming it is a file. - I further assume that in an attempt to fix the issue, `gulp-clang-format` was updated to the latest version (1.0.27) in 5eb742621. - `gulp format:enforce` stopped complaining, so everyone thought formatting was fine and moved on. - Formatting still wasn't fine, but the task completed successfully nevertheless :scream: - The reason is that angular/gulp-clang-format@55b697c5c (and subsequent commits) changed the way the `done()` callback was called, leaving it to `clang-format` to call it (while previously it was also called when the associated stream ended). - In the old version of `clang-format` that we are using (1.0.41), there is a bug (which has been fixed in angular/clang-format@4cce2c4ee): The callback is not called [unless the process exits with an error][2]. One can also see that the `gulp format:enforce` task is not completed in `gulp lint`. Example output from [build 374722][3]: ``` yarn gulp lint ... Starting 'format:enforce'... Starting 'validate-commit-messages'... ... Finished 'validate-commit-messages' after 833 ms Starting 'tools:build'... Finished 'tools:build' after 1.75 s Starting 'tslint'... Finished 'tslint' after 19 s Done in 21.82s. ``` Notice that all tasks have a corresponding "Finished X` log, except for `format:enforce`. For reference: The problem was originally reported by @ocombe on Slack ([discussion][4]). --- This commit fixes the issue by downgrading `gulp-clang-format` to 1.0.23. The linting failures due to formatting issues will be addressed in subsequent commits. [1]: https://github.com/angular/angular/blob/a8f3b317f/tools/gulp-tasks/format.js#L13 [2]: https://github.com/angular/clang-format/blob/b8c7df0b7/index.js#L95 [3]: https://circleci.com/gh/angular/angular/374722 [4]: https://angular-team.slack.com/archives/C042EU9T5/p1561480241191000 PR Close #31295
2019-06-26 14:09:32 -04:00
stream-equal@0.1.6:
version "0.1.6"
resolved "https://registry.yarnpkg.com/stream-equal/-/stream-equal-0.1.6.tgz#cc522fab38516012e4d4ee47513b147b72359019"
integrity sha1-zFIvqzhRYBLk1O5HUTsUe3I1kBk=
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
stream-events@^1.0.1, stream-events@^1.0.3:
version "1.0.5"
resolved "https://registry.yarnpkg.com/stream-events/-/stream-events-1.0.5.tgz#bbc898ec4df33a4902d892333d47da9bf1c406d5"
integrity sha512-E1GUzBSgvct8Jsb3v2X15pjzN1tYebtbLaMg+eBOUOAxgbLoSbT2NS91ckc5lJD1KfLjId+jXJRgo0qnV5Nerg==
dependencies:
stubs "^3.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
stream-shift@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/stream-shift/-/stream-shift-1.0.0.tgz#d5c752825e5367e786f78e18e445ea223a155952"
integrity sha1-1cdSgl5TZ+eG944Y5EXqIjoVWVI=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
stream-to-array@~2.3.0:
version "2.3.0"
resolved "https://registry.yarnpkg.com/stream-to-array/-/stream-to-array-2.3.0.tgz#bbf6b39f5f43ec30bc71babcb37557acecf34353"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-u/azn19D7DC8cbq8s3VXrOzzQ1M=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
any-promise "^1.1.0"
stream-to-promise@2.2.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/stream-to-promise/-/stream-to-promise-2.2.0.tgz#b1edb2e1c8cb11289d1b503c08d3f2aef51e650f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-se2y4cjLESidG1A8CNPyrvUeZQ8=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
any-promise "~1.3.0"
end-of-stream "~1.1.0"
stream-to-array "~2.3.0"
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
streamfilter@^1.0.5:
version "1.0.7"
resolved "https://registry.yarnpkg.com/streamfilter/-/streamfilter-1.0.7.tgz#ae3e64522aa5a35c061fd17f67620c7653c643c9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-Gk6KZM+yNA1JpW0KzlZIhjo3EaBJDkYfXtYSbOwNIQ7Zd6006E6+sCFlW1NDvFG/vnXhKmw6TJJgiEQg/8lXfQ==
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
readable-stream "^2.0.2"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
streamroller@0.7.0:
version "0.7.0"
resolved "https://registry.yarnpkg.com/streamroller/-/streamroller-0.7.0.tgz#a1d1b7cf83d39afb0d63049a5acbf93493bdf64b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-WREzfy0r0zUqp3lGO096wRuUp7ho1X6uo/7DJfTlEi0Iv/4gT7YHqXDjKC2ioVGBZtE8QzsQD9nx1nIuoZ57jQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
date-format "^1.2.0"
debug "^3.1.0"
mkdirp "^0.5.1"
readable-stream "^2.3.0"
build: add missing http-server dep to bazel example (#32889) Also update rules_nodejs 0.38.0->0.38.1 PR Close #32889
2019-10-04 08:17:26 -04:00
streamroller@^1.0.6:
version "1.0.6"
resolved "https://registry.yarnpkg.com/streamroller/-/streamroller-1.0.6.tgz#8167d8496ed9f19f05ee4b158d9611321b8cacd9"
integrity sha512-3QC47Mhv3/aZNFpDDVO44qQb9gwB9QggMEE0sQmkTAwBVYdBRWISdsywlkfm5II1Q5y/pmrHflti/IgmIzdDBg==
dependencies:
async "^2.6.2"
date-format "^2.0.0"
debug "^3.2.6"
fs-extra "^7.0.1"
lodash "^4.17.14"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
strict-uri-encode@^1.0.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/strict-uri-encode/-/strict-uri-encode-1.1.0.tgz#279b225df1d582b1f54e65addd4352e18faa0713"
integrity sha1-J5siXfHVgrH1TmWt3UNS4Y+qBxM=
string-format-obj@^1.1.0:
version "1.1.1"
resolved "https://registry.yarnpkg.com/string-format-obj/-/string-format-obj-1.1.1.tgz#c7612ca4e2ad923812a81db192dc291850aa1f65"
integrity sha512-Mm+sROy+pHJmx0P/0Bs1uxIX6UhGJGj6xDGQZ5zh9v/SZRmLGevp+p0VJxV7lirrkAmQ2mvva/gHKpnF/pTb+Q==
string-length@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/string-length/-/string-length-1.0.1.tgz#56970fb1c38558e9e70b728bf3de269ac45adfac"
integrity sha1-VpcPscOFWOnnC3KL894mmsRa36w=
dependencies:
strip-ansi "^3.0.0"
string-template@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/string-template/-/string-template-1.0.0.tgz#9e9f2233dc00f218718ec379a28a5673ecca8b96"
integrity sha1-np8iM9wA8hhxjsN5oopWc+zKi5Y=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
string-width@^1.0.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/string-width/-/string-width-1.0.2.tgz#118bdf5b8cdc51a2a7e70d211e07e2b0b9b107d3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-EYvfW4zcUaKn5w0hHgfisLmxB9M=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
code-point-at "^1.0.0"
is-fullwidth-code-point "^1.0.0"
strip-ansi "^3.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
"string-width@^1.0.2 || 2", string-width@^2.0.0, string-width@^2.1.0, string-width@^2.1.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.1.1"
resolved "https://registry.yarnpkg.com/string-width/-/string-width-2.1.1.tgz#ab93f27a8dc13d28cac815c462143a6d9012ae9e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-nOqH59deCq9SRHlxq1Aw85Jnt4w6KvLKqWVik6oA9ZklXLNIOlqg4F2yrT1MVaTjAqvVwdfeZ7w7aCvJD7ugkw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-fullwidth-code-point "^2.0.0"
strip-ansi "^4.0.0"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
string-width@^3.0.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/string-width/-/string-width-3.1.0.tgz#22767be21b62af1081574306f69ac51b62203961"
integrity sha512-vafcv6KjVZKSgz06oM/H6GDBrAtz8vdhQakGjFIvNrHA6y3HCF1CInLy+QLq8dTJPQ1b+KDUqDFctkdRW44e1w==
dependencies:
emoji-regex "^7.0.1"
is-fullwidth-code-point "^2.0.0"
strip-ansi "^5.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
string_decoder@~0.10.25, string_decoder@~0.10.x:
version "0.10.31"
resolved "https://registry.yarnpkg.com/string_decoder/-/string_decoder-0.10.31.tgz#62e203bc41766c6c28c9fc84301dab1c5310fa94"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-YuIDvEF2bGwoyfyEMB2rHFMQ+pQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
string_decoder@~1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/string_decoder/-/string_decoder-1.1.1.tgz#9cf1611ba62685d7030ae9e4ba34149c3af03fc8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
safe-buffer "~5.1.0"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
stringstream@~0.0.4:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.0.6"
resolved "https://registry.yarnpkg.com/stringstream/-/stringstream-0.0.6.tgz#7880225b0d4ad10e30927d167a1d6f2fd3b33a72"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-87GEBAkegbBcweToUrdzf3eLhWNg06FJTebl4BVJz/JgWy8CvEr9dRtX5qWphiynMSQlxxi+QqN0z5T32SLlhA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
strip-ansi@^3.0.0, strip-ansi@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-3.0.1.tgz#6a385fb8853d952d5ff05d0e8aaf94278dc63dcf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ajhfuIU9lS1f8F0Oiq+UJ43GPc8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
ansi-regex "^2.0.0"
strip-ansi@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-4.0.0.tgz#a8479022eb1ac368a871389b635262c505ee368f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-qEeQIusaw2iocTibY1JixQXuNo8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
ansi-regex "^3.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
strip-ansi@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-5.0.0.tgz#f78f68b5d0866c20b2c9b8c61b5298508dc8756f"
integrity sha512-Uu7gQyZI7J7gn5qLn1Np3G9vcYGTVqB+lFTytnDJv83dd8T22aGH451P3jueT2/QemInJDfxHB5Tde5OzgG1Ow==
dependencies:
ansi-regex "^4.0.0"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
strip-ansi@^5.1.0:
version "5.2.0"
resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-5.2.0.tgz#8c9a536feb6afc962bdfa5b104a5091c1ad9c0ae"
integrity sha512-DuRs1gKbBqsMKIZlrffwlug8MHkcnpjs5VPmL1PAh+mA30U0DTotfDZ0d2UUsXpPmPmMMJ6W773MaA3J+lbiWA==
dependencies:
ansi-regex "^4.1.0"
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
strip-bom-buf@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/strip-bom-buf/-/strip-bom-buf-1.0.0.tgz#1cb45aaf57530f4caf86c7f75179d2c9a51dd572"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-HLRar1dTD0yvhsf3UXnSyaUd1XI=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
is-utf8 "^0.2.1"
strip-bom-stream@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/strip-bom-stream/-/strip-bom-stream-3.0.0.tgz#956bcc5d84430f69256a90ed823765cd858e159c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-lWvMXYRDD2klapDtgjdlzYWOFZw=
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
first-chunk-stream "^2.0.0"
strip-bom-buf "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
strip-bom@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/strip-bom/-/strip-bom-1.0.0.tgz#85b8862f3844b5a6d5ec8467a93598173a36f794"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-hbiGLzhEtabV7IRnqTWYFzo295Q=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
first-chunk-stream "^1.0.0"
is-utf8 "^0.2.0"
strip-bom@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/strip-bom/-/strip-bom-2.0.0.tgz#6219a85616520491f35788bdbf1447a99c7e6b0e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-YhmoVhZSBJHzV4i9vxRHqZx+aw4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
is-utf8 "^0.2.0"
strip-bom@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/strip-bom/-/strip-bom-3.0.0.tgz#2334c18e9c759f7bdd56fdef7e9ae3d588e68ed3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-IzTBjpx1n3vdVv3vfprj1YjmjtM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
strip-eof@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/strip-eof/-/strip-eof-1.0.0.tgz#bb43ff5598a6eb05d89b59fcd129c983313606bf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-u0P/VZim6wXYm1n80SnJgzE2Br8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
strip-indent@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/strip-indent/-/strip-indent-1.0.1.tgz#0c7962a6adefa7bbd4ac366460a638552ae1a0a2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-DHlipq3vp7vUrDZkYKY4VSrhoKI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
get-stdin "^4.0.1"
refactor: add a commit-msg git hook to check commit messages (#22969) The commit command will fail if the commit message header does not follow the Angular convetions as defined in /CONTRIBUTING.md. You can force the commit by adding the `--no-verify` option. NOTE: You should remove all unused hooks (in <angular>/.git/hooks) before running `yarn` so that husky hooks are installed correctly. PR Close #22969
2018-03-23 19:07:33 -04:00
strip-indent@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/strip-indent/-/strip-indent-2.0.0.tgz#5ef8db295d01e6ed6cbf7aab96998d7822527b68"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-XvjbKV0B5u1sv3qrlpmNeCJSe2g=
refactor: add a commit-msg git hook to check commit messages (#22969) The commit command will fail if the commit message header does not follow the Angular convetions as defined in /CONTRIBUTING.md. You can force the commit by adding the `--no-verify` option. NOTE: You should remove all unused hooks (in <angular>/.git/hooks) before running `yarn` so that husky hooks are installed correctly. PR Close #22969
2018-03-23 19:07:33 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
strip-json-comments@~2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/strip-json-comments/-/strip-json-comments-2.0.1.tgz#3c531942e908c2697c0ec344858c286c7ca0a60a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-PFMZQukIwml8DsNEhYwobHygpgo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
stubs@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/stubs/-/stubs-3.0.0.tgz#e8d2ba1fa9c90570303c030b6900f7d5f89abe5b"
integrity sha1-6NK6H6nJBXAwPAMLaQD31fiavls=
superstatic@^6.0.1:
version "6.0.4"
resolved "https://registry.yarnpkg.com/superstatic/-/superstatic-6.0.4.tgz#5c38fe05e2e9513b68d5ba2798925e4839c151dd"
integrity sha512-Nfli9mSPa9fJloKuDeUOdqC1lcw4c4SnxiWPB8s7Yn1iYo7Ja3pj7qc8AXMqHVqn/Kf7QsxBjAeOJTpuJ0mcrQ==
dependencies:
as-array "^2.0.0"
async "^1.5.2"
basic-auth-connect "^1.0.0"
chalk "^1.1.3"
char-spinner "^1.0.1"
compare-semver "^1.0.0"
compression "^1.7.0"
connect "^3.6.2"
connect-query "^1.0.0"
destroy "^1.0.4"
fast-url-parser "^1.1.3"
fs-extra "^0.30.0"
glob "^7.1.2"
glob-slasher "^1.0.1"
home-dir "^1.0.0"
is-url "^1.2.2"
join-path "^1.1.1"
lodash "^4.17.4"
mime-types "^2.1.16"
minimatch "^3.0.4"
morgan "^1.8.2"
nash "^3.0.0"
on-finished "^2.2.0"
on-headers "^1.0.0"
path-to-regexp "^1.7.0"
router "^1.3.1"
rsvp "^3.6.2"
string-length "^1.0.0"
try-require "^1.0.0"
update-notifier "^2.5.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
supports-color@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-2.0.0.tgz#535d045ce6b6363fa40117084629995e9df324c7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-U10EXOa2Nj+kARcIRimZXp3zJMc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
supports-color@^3.1.0, supports-color@^3.1.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "3.2.3"
resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-3.2.3.tgz#65ac0504b3954171d8a64946b2ae3cbb8a5f54f6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ZawFBLOVQXHYpklGsq48u4pfVPY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
has-flag "^1.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
supports-color@^5.3.0:
version "5.5.0"
resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-5.5.0.tgz#e2e69a44ac8772f78a1ec0b35b689df6530efc8f"
integrity sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==
dependencies:
has-flag "^3.0.0"
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
supports-color@^6.1.0:
version "6.1.0"
resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-6.1.0.tgz#0764abc69c63d5ac842dd4867e8d025e880df8f3"
integrity sha512-qe1jfm1Mg7Nq/NSh6XE24gPXROEVsWHxC1LIx//XNlD9iw7YZQGjZNjYN7xGaEG6iKdA8EtNFW6R0gjnVXp+wQ==
dependencies:
has-flag "^3.0.0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
symbol-observable@1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/symbol-observable/-/symbol-observable-1.2.0.tgz#c22688aed4eab3cdc2dfeacbb561660560a00804"
integrity sha512-e900nM8RRtGhlV36KGEU9k65K3mPb1WV70OdjfxlG2EAuM1noi/E/BaW/uMhL7bPEssK8QV57vN3esixjUvcXQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
systemjs@0.18.10:
version "0.18.10"
resolved "https://registry.yarnpkg.com/systemjs/-/systemjs-0.18.10.tgz#4e679dc5bb04dffb9882d40b19c5daa1cd182102"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-TmedxbsE3/uYgtQLGcXaoc0YIQI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
es6-module-loader "^0.17.4"
when "^3.7.2"
tapable@^0.1.8, tapable@~0.1.8:
version "0.1.10"
resolved "https://registry.yarnpkg.com/tapable/-/tapable-0.1.10.tgz#29c35707c2b70e50d07482b5d202e8ed446dafd4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-KcNXB8K3DlDQdIK10gLo7URtr9Q=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
tar-stream@^1.5.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.6.1"
resolved "https://registry.yarnpkg.com/tar-stream/-/tar-stream-1.6.1.tgz#f84ef1696269d6223ca48f6e1eeede3f7e81f395"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-IFLM5wp3QrJODQFPm6/to3LJZrONdBY/otxcvDIQzu217zKye6yVR3hhi9lAjrC2Z+m/j5oDxMPb1qcd8cIvpA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
bl "^1.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
buffer-alloc "^1.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
end-of-stream "^1.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
fs-constants "^1.0.0"
readable-stream "^2.3.0"
to-buffer "^1.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
xtend "^4.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
tar@^4, tar@^4.3.0, tar@^4.4.8:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "4.4.8"
resolved "https://registry.yarnpkg.com/tar/-/tar-4.4.8.tgz#b19eec3fde2a96e64666df9fdb40c5ca1bc3747d"
integrity sha512-LzHF64s5chPQQS0IYBn9IN5h3i98c12bo4NCO7e0sGM2llXQ3p2FGC5sdENN4cTW48O915Sh+x+EXx7XW96xYQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
chownr "^1.1.1"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
fs-minipass "^1.2.5"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
minipass "^2.3.4"
minizlib "^1.1.1"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
mkdirp "^0.5.0"
safe-buffer "^5.1.2"
yallist "^3.0.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
temp@~0.4.0:
version "0.4.0"
resolved "https://registry.yarnpkg.com/temp/-/temp-0.4.0.tgz#671ad63d57be0fe9d7294664b3fc400636678a60"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ZxrWPVe+D+nXKUZks/xABjZnimA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
term-size@^1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/term-size/-/term-size-1.2.0.tgz#458b83887f288fc56d6fffbfad262e26638efa69"
integrity sha1-RYuDiH8oj8Vtb/+/rSYuJmOO+mk=
dependencies:
execa "^0.7.0"
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
terser@^3.14.1:
version "3.17.0"
resolved "https://registry.yarnpkg.com/terser/-/terser-3.17.0.tgz#f88ffbeda0deb5637f9d24b0da66f4e15ab10cb2"
integrity sha512-/FQzzPJmCpjAH9Xvk2paiWrFq+5M6aVOf+2KRbwhByISDX/EujxsK+BAvrhb6H+2rtrLCHK9N01wO014vrIwVQ==
dependencies:
commander "^2.19.0"
source-map "~0.6.1"
source-map-support "~0.5.10"
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
test-exclude@^5.2.2:
version "5.2.3"
resolved "https://registry.yarnpkg.com/test-exclude/-/test-exclude-5.2.3.tgz#c3d3e1e311eb7ee405e092dac10aefd09091eac0"
integrity sha512-M+oxtseCFO3EDtAaGH7iiej3CBkzXqFMbzqYAACdzKui4eZA+pq3tZEwChvOdNfa7xxy8BfbmgJSIr43cC/+2g==
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
dependencies:
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
glob "^7.1.3"
minimatch "^3.0.4"
read-pkg-up "^4.0.0"
require-main-filename "^2.0.0"
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
text-extensions@^1.0.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.7.0"
resolved "https://registry.yarnpkg.com/text-extensions/-/text-extensions-1.7.0.tgz#faaaba2625ed746d568a23e4d0aacd9bf08a8b39"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-AKXZeDq230UaSzaO5s3qQUZOaC7iKbzq0jOFL614R7d9R593HLqAOL0cYoqLdkNrjBSOdmoQI06yigq1TSBXAg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
thenify-all@^1.0.0:
version "1.6.0"
resolved "https://registry.yarnpkg.com/thenify-all/-/thenify-all-1.6.0.tgz#1a1918d402d8fc3f98fbf234db0bcc8cc10e9726"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-GhkY1ALY/D+Y+/I02wvMjMEOlyY=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
thenify ">= 3.1.0 < 4"
"thenify@>= 3.1.0 < 4":
version "3.3.0"
resolved "https://registry.yarnpkg.com/thenify/-/thenify-3.3.0.tgz#e69e38a1babe969b0108207978b9f62b88604839"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-5p44obq+lpsBCCB5eLn2K4hgSDk=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
any-promise "^1.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
throttleit@~0.0.2:
version "0.0.2"
resolved "https://registry.yarnpkg.com/throttleit/-/throttleit-0.0.2.tgz#cfedf88e60c00dd9697b61fdd2a8343a9b680eaf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-z+34jmDADdlpe2H90qg0OptoDq8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
through2@2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/through2/-/through2-2.0.1.tgz#384e75314d49f32de12eebb8136b8eb6b5d59da9"
integrity sha1-OE51MU1J8y3hLuu4E2uOtrXVnak=
dependencies:
readable-stream "~2.0.0"
xtend "~4.0.0"
build: downgrade `gulp-clang-format` to 1.0.23 (#31295) The `gulp format*` tasks have been broken since 5eb742621. These include the `gulp format:enforce` task, which is what runs on CI to enforce consistent code style. Here is what (I believe) happened: - I assume formatting was failing in 5eb742621 (moving `zone.js` into `angular/angular`). The reason must have been that [this glob pattern][1] matches `packages/zone.js/` (which is a directory) and passes it to `clang-format` claiming it is a file. - I further assume that in an attempt to fix the issue, `gulp-clang-format` was updated to the latest version (1.0.27) in 5eb742621. - `gulp format:enforce` stopped complaining, so everyone thought formatting was fine and moved on. - Formatting still wasn't fine, but the task completed successfully nevertheless :scream: - The reason is that angular/gulp-clang-format@55b697c5c (and subsequent commits) changed the way the `done()` callback was called, leaving it to `clang-format` to call it (while previously it was also called when the associated stream ended). - In the old version of `clang-format` that we are using (1.0.41), there is a bug (which has been fixed in angular/clang-format@4cce2c4ee): The callback is not called [unless the process exits with an error][2]. One can also see that the `gulp format:enforce` task is not completed in `gulp lint`. Example output from [build 374722][3]: ``` yarn gulp lint ... Starting 'format:enforce'... Starting 'validate-commit-messages'... ... Finished 'validate-commit-messages' after 833 ms Starting 'tools:build'... Finished 'tools:build' after 1.75 s Starting 'tslint'... Finished 'tslint' after 19 s Done in 21.82s. ``` Notice that all tasks have a corresponding "Finished X` log, except for `format:enforce`. For reference: The problem was originally reported by @ocombe on Slack ([discussion][4]). --- This commit fixes the issue by downgrading `gulp-clang-format` to 1.0.23. The linting failures due to formatting issues will be addressed in subsequent commits. [1]: https://github.com/angular/angular/blob/a8f3b317f/tools/gulp-tasks/format.js#L13 [2]: https://github.com/angular/clang-format/blob/b8c7df0b7/index.js#L95 [3]: https://circleci.com/gh/angular/angular/374722 [4]: https://angular-team.slack.com/archives/C042EU9T5/p1561480241191000 PR Close #31295
2019-06-26 14:09:32 -04:00
through2@^0.6.1, through2@^0.6.3:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.6.5"
resolved "https://registry.yarnpkg.com/through2/-/through2-0.6.5.tgz#41ab9c67b29d57209071410e1d7a7a968cd3ad48"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-QaucZ7KdVyCQcUEOHXp6lozTrUg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
readable-stream ">=1.0.33-1 <1.1.0-0"
xtend ">=4.0.0 <4.1.0-0"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
through2@^2.0.0:
version "2.0.5"
resolved "https://registry.yarnpkg.com/through2/-/through2-2.0.5.tgz#01c1e39eb31d07cb7d03a96a70823260b23132cd"
integrity sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==
dependencies:
readable-stream "~2.3.6"
xtend "~4.0.1"
through2@^2.0.2, through2@^2.0.3:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.0.3"
resolved "https://registry.yarnpkg.com/through2/-/through2-2.0.3.tgz#0004569b37c7c74ba39c43f3ced78d1ad94140be"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-AARWmzfHx0ujnEPzzteNGtlBQL4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
readable-stream "^2.1.5"
xtend "~4.0.1"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
through@2, "through@>=2.2.7 <3", through@^2.3.6, through@~2.3, through@~2.3.1, through@~2.3.8:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.3.8"
resolved "https://registry.yarnpkg.com/through/-/through-2.3.8.tgz#0dd4c9ffaabc357960b1b724115d7e0e86a2e1f5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-DdTJ/6q8NXlgsbckEV1+Doai4fU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
tildify@^1.0.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/tildify/-/tildify-1.2.0.tgz#dcec03f55dca9b7aa3e5b04f21817eb56e63588a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-3OwD9V3Km3qj5bBPIYF+tW5jWIo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
os-homedir "^1.0.0"
time-stamp@^1.0.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/time-stamp/-/time-stamp-1.1.0.tgz#764a5a11af50561921b133f3b44e618687e0f5c3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-dkpaEa9QVhkhsTPztE5hhofg9cM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
timed-out@^4.0.0, timed-out@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/timed-out/-/timed-out-4.0.1.tgz#f32eacac5a175bea25d7fab565ab3ed8741ef56f"
integrity sha1-8y6srFoXW+ol1/q1Zas+2HQe9W8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
timers-browserify@^1.0.1:
version "1.4.2"
resolved "https://registry.yarnpkg.com/timers-browserify/-/timers-browserify-1.4.2.tgz#c9c58b575be8407375cb5e2462dacee74359f41d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ycWLV1voQHN1y14kYtrO50NZ9B0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
process "~0.11.0"
timers-ext@0.1, timers-ext@^0.1.2:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.1.5"
resolved "https://registry.yarnpkg.com/timers-ext/-/timers-ext-0.1.5.tgz#77147dd4e76b660c2abb8785db96574cbbd12922"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-tsEStd7kmACHENhsUPaxb8Jf8/+GZZxyNFQbZD07HQOyooOa6At1rQqjffgvg7n+dxscQa9cjjMdWhJtsP2sxg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
es5-ext "~0.10.14"
next-tick "1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
timers-ext@^0.1.5:
version "0.1.7"
resolved "https://registry.yarnpkg.com/timers-ext/-/timers-ext-0.1.7.tgz#6f57ad8578e07a3fb9f91d9387d65647555e25c6"
integrity sha512-b85NUNzTSdodShTIbky6ZF02e8STtVVfD+fu4aXXShEELpozH+bCpJLYMPZbsABN2wDH7fJpqIoXxJpzbf0NqQ==
dependencies:
es5-ext "~0.10.46"
next-tick "1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
tiny-lr@^0.2.1:
version "0.2.1"
resolved "https://registry.yarnpkg.com/tiny-lr/-/tiny-lr-0.2.1.tgz#b3fdba802e5d56a33c2f6f10794b32e477ac729d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-s/26gC5dVqM8L28QeUsy5Hescp0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
body-parser "~1.14.0"
debug "~2.2.0"
faye-websocket "~0.10.0"
livereload-js "^2.2.0"
parseurl "~1.3.0"
qs "~5.1.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
tmp@0.0.28:
version "0.0.28"
resolved "https://registry.yarnpkg.com/tmp/-/tmp-0.0.28.tgz#172735b7f614ea7af39664fa84cf0de4e515d120"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Fyc1t/YU6nrzlmT6hM8N5OUV0SA=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
os-tmpdir "~1.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
tmp@0.0.30:
version "0.0.30"
resolved "https://registry.yarnpkg.com/tmp/-/tmp-0.0.30.tgz#72419d4a8be7d6ce75148fd8b324e593a711c2ed"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ckGdSovn1s51FI/YsyTlk6cRwu0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
os-tmpdir "~1.0.1"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
tmp@0.0.33, tmp@0.0.x, tmp@^0.0.33:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.0.33"
resolved "https://registry.yarnpkg.com/tmp/-/tmp-0.0.33.tgz#6d34335889768d21b2bcda0aa277ced3b1bfadf9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-jRCJlojKnZ3addtTOjdIqoRuPEKBvNXcGYqzO6zWZX8KfKEpnGY5jfggJQ3EjKuu8D4bJRr0y+cYJFmYbImXGw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
os-tmpdir "~1.0.2"
to-array@0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/to-array/-/to-array-0.1.4.tgz#17e6c11f73dd4f3d74cda7a4ff3238e9ad9bf890"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-F+bBH3PdTz10zaek/zI46a2b+JA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
to-ast@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/to-ast/-/to-ast-1.0.0.tgz#0c4a31c8c98edfde9aaf0192c794b4c8b11ee287"
integrity sha1-DEoxyMmO396arwGSx5S0yLEe4oc=
dependencies:
ast-types "^0.7.2"
esprima "^2.1.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
to-buffer@^1.1.0:
version "1.1.1"
resolved "https://registry.yarnpkg.com/to-buffer/-/to-buffer-1.1.1.tgz#493bd48f62d7c43fcded313a03dcadb2e1213a80"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-lx9B5iv7msuFYE3dytT+KE5tap+rNYw+K4jVkb9R/asAb+pbBSM17jtunHplhBe6RRJdZx3Pn2Jph24O32mOVg==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
to-object-path@^0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/to-object-path/-/to-object-path-0.3.0.tgz#297588b7b0e7e0ac08e04e672f85c1f4999e17af"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-KXWIt7Dn4KwI4E5nL4XB9JmeF68=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
kind-of "^3.0.2"
to-regex-range@^2.1.0:
version "2.1.1"
resolved "https://registry.yarnpkg.com/to-regex-range/-/to-regex-range-2.1.1.tgz#7c80c17b9dfebe599e27367e0d4dd5590141db38"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-fIDBe53+vlmeJzZ+DU3VWQFB2zg=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
is-number "^3.0.0"
repeat-string "^1.6.1"
to-regex@^3.0.1, to-regex@^3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/to-regex/-/to-regex-3.0.2.tgz#13cfdd9b336552f30b51f33a8ae1b42a7a7599ce"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-FWtleNAtZ/Ki2qtqej2CXTOayOH9bHDQF+Q48VpWyDXjbYxA4Yz8iDB31zXOBUlOHHKidDbqGVrTUvQMPmBGBw==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
define-property "^2.0.2"
extend-shallow "^3.0.2"
regex-not "^1.0.2"
safe-regex "^1.1.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
topo@1.x.x:
version "1.1.0"
resolved "https://registry.yarnpkg.com/topo/-/topo-1.1.0.tgz#e9d751615d1bb87dc865db182fa1ca0a5ef536d5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-6ddRYV0buH3IZdsYL6HKCl71NtU=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
hoek "2.x.x"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
touch@0.0.3:
version "0.0.3"
resolved "https://registry.yarnpkg.com/touch/-/touch-0.0.3.tgz#51aef3d449571d4f287a5d87c9c8b49181a0db1d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Ua7z1ElXHU8oel2Hyci0kYGg2x0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
nopt "~1.0.10"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
tough-cookie@~2.3.0, tough-cookie@~2.3.3:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "2.3.4"
resolved "https://registry.yarnpkg.com/tough-cookie/-/tough-cookie-2.3.4.tgz#ec60cee38ac675063ffc97a5c18970578ee83655"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-TZ6TTfI5NtZnuyy/Kecv+CnoROnyXn2DN97LontgQpCwsX2XyLYCC0ENhYkehSOwAp8rTQKc/NUIF7BkQ5rKLA==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
punycode "^1.4.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
tough-cookie@~2.4.3:
version "2.4.3"
resolved "https://registry.yarnpkg.com/tough-cookie/-/tough-cookie-2.4.3.tgz#53f36da3f47783b0925afa06ff9f3b165280f781"
integrity sha512-Q5srk/4vDM54WJsJio3XNn6K2sCG+CQ8G5Wz6bZhRZoAe/+TxjWB/GlFAnYEbkYVlON9FMk/fE3h2RLpPXo4lQ==
dependencies:
psl "^1.1.24"
punycode "^1.4.1"
toxic@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/toxic/-/toxic-1.0.1.tgz#8c2e2528da591100adc3883f2c0e56acfb1c7288"
integrity sha512-WI3rIGdcaKULYg7KVoB0zcjikqvcYYvcuT6D89bFPz2rVR0Rl0PK6x8/X62rtdLtBKIE985NzVf/auTtGegIIg==
dependencies:
lodash "^4.17.10"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
traverse@>=0.2.4:
version "0.6.6"
resolved "https://registry.yarnpkg.com/traverse/-/traverse-0.6.6.tgz#cbdf560fd7b9af632502fed40f918c157ea97137"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-y99WD9e5r2MlAv7UD5GMFX6pcTc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
"traverse@>=0.3.0 <0.4":
version "0.3.9"
resolved "https://registry.yarnpkg.com/traverse/-/traverse-0.3.9.tgz#717b8f220cc0bb7b44e40514c22b2e8bbc70d8b9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-cXuPIgzAu3tE5AUUwisui7xw2Lk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
trim-newlines@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/trim-newlines/-/trim-newlines-1.0.0.tgz#5887966bb582a4503a41eb524f7d35011815a613"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-WIeWa7WCpFA6QetST301ARgVphM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
trim-newlines@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/trim-newlines/-/trim-newlines-2.0.0.tgz#b403d0b91be50c331dfc4b82eeceb22c3de16d20"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-tAPQuRvlDDMd/EuC7s6yLD3hbSA=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
trim-off-newlines@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/trim-off-newlines/-/trim-off-newlines-1.0.1.tgz#9f9ba9d9efa8764c387698bcbfeb2c848f11adb3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-n5up2e+odkw4dpi8v+sshI8RrbM=
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
try-require@^1.0.0:
version "1.2.1"
resolved "https://registry.yarnpkg.com/try-require/-/try-require-1.2.1.tgz#34489a2cac0c09c1cc10ed91ba011594d4333be2"
integrity sha1-NEiaLKwMCcHMEO2RugEVlNQzO+I=
build: TypeScript 3.5 upgrade (#31615) https://github.com/Microsoft/TypeScript/wiki/Breaking-Changes#typescript-35 PR Close #31615
2019-07-17 20:49:16 -04:00
tsickle@0.36.0:
version "0.36.0"
resolved "https://registry.yarnpkg.com/tsickle/-/tsickle-0.36.0.tgz#d6f47cdd14d009f3fea4e8516cd46c1393f3aa02"
integrity sha512-lrEMU5e+efx5DXtrRSGsxgkCOVRw4WeVaOkQ2pMIxCZDY5rISagVyP4yi7t6M396POFSbMHgQMT/vz0HmfxWVA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
minimist "^1.2.0"
mkdirp "^0.5.1"
build: update to tsickle 0.33.1 (#27612) PR Close #27612
2018-12-11 20:02:09 -05:00
source-map "^0.7.3"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
tslib@^1.0.0, tslib@^1.7.1, tslib@^1.8.1, tslib@^1.9.0:
version "1.9.3"
resolved "https://registry.yarnpkg.com/tslib/-/tslib-1.9.3.tgz#d7e4dd79245d85428c4d7e4822a79917954ca286"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-4krF8scpejhaOgqzBEcGM7yDIEfi0/8+8zDRZhNZZ2kjmHJ4hv3zCbQWxoJGz1iw5U0Jl0nma13xzHXcncMavQ==
build: update to latest bazel rules (#22127) PR Close #22127
2018-02-09 13:22:00 -05:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
tslint-eslint-rules@4.1.1:
version "4.1.1"
resolved "https://registry.yarnpkg.com/tslint-eslint-rules/-/tslint-eslint-rules-4.1.1.tgz#7c30e7882f26bc276bff91d2384975c69daf88ba"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-fDDniC8mvCdr/5HSOEl1xp2viLo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
doctrine "^0.7.2"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
tslib "^1.0.0"
tsutils "^1.4.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
refactor: remove toplevel property accesses (#29329) PR Close #29329
2019-05-02 11:44:24 -04:00
tslint-no-toplevel-property-access@0.0.2:
version "0.0.2"
resolved "https://registry.yarnpkg.com/tslint-no-toplevel-property-access/-/tslint-no-toplevel-property-access-0.0.2.tgz#c9b19bbd525ea7b8577e5ada601cc8625b4ed004"
integrity sha512-Oc+UUurlGLBkgeUSGxMoTpRUpaXsjqzQCEAYrYQyuU8330fi5FKlye5n53y87EJ24AlfdoxMPV7DJfFOADapfg==
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
tslint@5.7.0:
version "5.7.0"
resolved "https://registry.yarnpkg.com/tslint/-/tslint-5.7.0.tgz#c25e0d0c92fa1201c2bc30e844e08e682b4f3552"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wl4NDJL6EgHCvDDoROCOaCtPNVI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
babel-code-frame "^6.22.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
colors "^1.1.2"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
commander "^2.9.0"
diff "^3.2.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
glob "^7.1.1"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
minimatch "^3.0.4"
resolve "^1.3.2"
semver "^5.3.0"
tslib "^1.7.1"
tsutils "^2.8.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
tslint@~5.1.0:
version "5.1.0"
resolved "https://registry.yarnpkg.com/tslint/-/tslint-5.1.0.tgz#51a47baeeb58956fcd617bd2cf00e2ef0eea2ed9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-UaR7rutYlW/NYXvSzwDi7w7qLtk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
babel-code-frame "^6.22.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
colors "^1.1.2"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
diff "^3.2.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
findup-sync "~0.3.0"
glob "^7.1.1"
optimist "~0.6.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
resolve "^1.3.2"
semver "^5.3.0"
tsutils "^1.4.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
tsscmp@1.0.5:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.5"
resolved "https://registry.yarnpkg.com/tsscmp/-/tsscmp-1.0.5.tgz#7dc4a33af71581ab4337da91d85ca5427ebd9a97"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-fcSjOvcVgatDN9qR2FylQn69mpc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
tsutils@2.27.2, tsutils@^2.8.1:
version "2.27.2"
resolved "https://registry.yarnpkg.com/tsutils/-/tsutils-2.27.2.tgz#60ba88a23d6f785ec4b89c6e8179cac9b431f1c7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-qf6rmT84TFMuxAKez2pIfR8UCai49iQsfB7YWVjV1bKpy/d0PWT5rEOSM6La9PiHZ0k1RRZQiwVdVJfQ3BPHgg==
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768
2017-12-06 09:56:49 -05:00
dependencies:
build: update to latest bazel rules (#22127) PR Close #22127
2018-02-09 13:22:00 -05:00
tslib "^1.8.1"
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768
2017-12-06 09:56:49 -05:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
tsutils@^1.4.0:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.9.1"
resolved "https://registry.yarnpkg.com/tsutils/-/tsutils-1.9.1.tgz#b9f9ab44e55af9681831d5f28d0aeeaf5c750cb0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ufmrROVa+WgYMdXyjQrur1x1DLA=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
tty-browserify@0.0.0:
version "0.0.0"
resolved "https://registry.yarnpkg.com/tty-browserify/-/tty-browserify-0.0.0.tgz#a157ba402da24e9bf957f9aa69d524eed42901a6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-oVe6QC2iTpv5V/mqadUk7tQpAaY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
tunnel-agent@^0.6.0:
version "0.6.0"
resolved "https://registry.yarnpkg.com/tunnel-agent/-/tunnel-agent-0.6.0.tgz#27a5dea06b36b04a0a9966774b290868f0fc40fd"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-J6XeoGs2sEoKmWZ3SykIaPD8QP0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
safe-buffer "^5.0.1"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
tunnel-agent@~0.4.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.4.3"
resolved "https://registry.yarnpkg.com/tunnel-agent/-/tunnel-agent-0.4.3.tgz#6373db76909fe570e08d73583365ed828a74eeeb"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Y3PbdpCf5XDgjXNYM2Xtgop07us=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
tweetnacl@^0.14.3, tweetnacl@~0.14.0:
version "0.14.5"
resolved "https://registry.yarnpkg.com/tweetnacl/-/tweetnacl-0.14.5.tgz#5ae68177f192d4456269d108afa93ff8743f4f64"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-WuaBd/GS1EViadEIr6k/+HQ/T2Q=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
type-check@~0.3.2:
version "0.3.2"
resolved "https://registry.yarnpkg.com/type-check/-/type-check-0.3.2.tgz#5884cab512cf1d355e3fb784f30804b2b520db72"
integrity sha1-WITKtRLPHTVeP7eE8wgEsrUg23I=
dependencies:
prelude-ls "~1.1.2"
build(bazel): remove @ts-api-guardian_deps yarn_install (#29799) PR Close #29799
2019-04-09 21:08:13 -04:00
type-detect@^4.0.0, type-detect@^4.0.5:
version "4.0.8"
resolved "https://registry.yarnpkg.com/type-detect/-/type-detect-4.0.8.tgz#7646fb5f18871cfbb7749e69bd39a6388eb7450c"
integrity sha512-0fr/mIH1dlO+x7TlcMy+bIDqKPsw/70tVyeHW787goQjhmqaZe10uwLujubK9q9Lg6Fiho1KUKDYz0Z7k7g5/g==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
type-is@~1.6.10, type-is@~1.6.16, type-is@~1.6.6:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.6.16"
resolved "https://registry.yarnpkg.com/type-is/-/type-is-1.6.16.tgz#f89ce341541c672b25ee7ae3c73dee3b2be50194"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-HRkVv/5qY2G6I8iab9cI7v1bOIdhm94dVjQCPFElW9W+3GeDOSHmy2EBYe4VTApuzolPcmgFTN3ftVJRKR2J9Q==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
media-typer "0.3.0"
mime-types "~2.1.18"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
typedarray@^0.0.6:
version "0.0.6"
resolved "https://registry.yarnpkg.com/typedarray/-/typedarray-0.0.6.tgz#867ac74e3864187b1d3d47d996a78ec5c8830777"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-hnrHTjhkGHsdPUfZlqeOxciDB3c=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test: add integration test for side effects (#29329) This new tests keeps track of the known side effects for Angular ES modules. PR Close #29329
2019-03-12 13:03:50 -04:00
typescript@3.2.4:
version "3.2.4"
resolved "https://registry.yarnpkg.com/typescript/-/typescript-3.2.4.tgz#c585cb952912263d915b462726ce244ba510ef3d"
integrity sha512-0RNDbSdEokBeEAkgNbxJ+BLwSManFy9TeXz8uW+48j/xhEXv1ePME60olyzw2XzUqUBNAYFeJadIqAgNqIACwg==
build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) PR Close #29966
2019-04-17 20:13:07 -04:00
typescript@3.4.3:
version "3.4.3"
resolved "https://registry.yarnpkg.com/typescript/-/typescript-3.4.3.tgz#0eb320e4ace9b10eadf5bc6103286b0f8b7c224f"
integrity sha512-FFgHdPt4T/duxx6Ndf7hwgMZZjZpB+U0nMNGVCYPq0rEzWKjEDobm4J6yb3CS7naZ0yURFqdw9Gwc7UOh/P9oQ==
build: update angular cli packages to latest beta (#29720) PR Close #29720
2019-04-05 02:38:16 -04:00
build: TypeScript 3.5 upgrade (#31615) https://github.com/Microsoft/TypeScript/wiki/Breaking-Changes#typescript-35 PR Close #31615
2019-07-17 20:49:16 -04:00
typescript@~3.5.3:
version "3.5.3"
resolved "https://registry.yarnpkg.com/typescript/-/typescript-3.5.3.tgz#c830f657f93f1ea846819e929092f5fe5983e977"
integrity sha512-ACzBtm/PhXBDId6a6sDJfroT2pOWt/oOnk4/dElG5G33ZL776N3Y6/6bKZJBFpd+b05F3Ct9qDjMeJmRWtE2/g==
feat: add TypeScript 3 support (#25275) PR Close #25275
2018-08-05 11:31:27 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
uglify-js@1.2.6, uglify-js@~1.2.5:
version "1.2.6"
resolved "https://registry.yarnpkg.com/uglify-js/-/uglify-js-1.2.6.tgz#d354b2d3c1cf10ebc18fa78c11a28bdd9ce1580d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-01Sy08HPEOvBj6eMEaKL3ZzhWA0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
uglify-js@^1.3.3:
version "1.3.5"
resolved "https://registry.yarnpkg.com/uglify-js/-/uglify-js-1.3.5.tgz#4b5bfff9186effbaa888e4c9e94bd9fc4c94929d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-S1v/+Rhu/7qoiOTJ6UvZ/EyUkp0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: switch from uglify-js to uglify-es (#22669) This enables us to minify ES2015 code. PR Close #22669
2018-03-10 00:01:53 -05:00
uglify-js@^2.6:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "2.8.29"
resolved "https://registry.yarnpkg.com/uglify-js/-/uglify-js-2.8.29.tgz#29c5733148057bb4e1f75df35b7a9cb72e6a59dd"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-KcVzMUgFe7Th913zW3qcty5qWd0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
source-map "~0.5.1"
yargs "~3.10.0"
optionalDependencies:
uglify-to-browserify "~1.0.0"
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
uglify-js@^3.1.4:
version "3.5.3"
resolved "https://registry.yarnpkg.com/uglify-js/-/uglify-js-3.5.3.tgz#d490bb5347f23025f0c1bc0dee901d98e4d6b063"
integrity sha512-rIQPT2UMDnk4jRX+w4WO84/pebU2jiLsjgIyrCktYgSvx28enOE3iYQMr+BD1rHiitWnDmpu0cY/LfIEpKcjcw==
dependencies:
commander "~2.19.0"
source-map "~0.6.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
uglify-js@~2.6.0:
version "2.6.4"
resolved "https://registry.yarnpkg.com/uglify-js/-/uglify-js-2.6.4.tgz#65ea2fb3059c9394692f15fed87c2b36c16b9adf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ZeovswWck5RpLxX+2HwrNsFrmt8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
async "~0.2.6"
source-map "~0.5.1"
uglify-to-browserify "~1.0.0"
yargs "~3.10.0"
uglify-to-browserify@~1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/uglify-to-browserify/-/uglify-to-browserify-1.0.2.tgz#6e0924d6bda6b5afe349e39a6d632850a0f882b7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-bgkk1r2mta/jSeOabWMoUKD4grc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
uid-number@0.0.5:
version "0.0.5"
resolved "https://registry.yarnpkg.com/uid-number/-/uid-number-0.0.5.tgz#5a3db23ef5dbd55b81fce0ec9a2ac6fccdebb81e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Wj2yPvXb1VuB/ODsmirG/M3ruB4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
uid-safe@2.1.4:
version "2.1.4"
resolved "https://registry.yarnpkg.com/uid-safe/-/uid-safe-2.1.4.tgz#3ad6f38368c6d4c8c75ec17623fb79aa1d071d81"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Otbzg2jG1MjHXsF2I/t5qh0HHYE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
random-bytes "~1.0.0"
uid-safe@~2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/uid-safe/-/uid-safe-2.0.0.tgz#a7f3c6ca64a1f6a5d04ec0ef3e4c3d5367317137"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-p/PGymSh9qXQTsDvPkw9U2cxcTc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
base64-url "1.2.1"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
ultron@~1.1.0:
version "1.1.1"
resolved "https://registry.yarnpkg.com/ultron/-/ultron-1.1.1.tgz#9fe1536a10a664a65266a1e3ccf85fd36302bc9c"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-UIEXBNeYmKptWH6z8ZnqTeS8fV74zG0/eRU9VGkpzz+LIJNs8W/zM/L+7ctCkRrgbNnnR0xxw4bKOr0cW0N0Og==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
unc-path-regex@^0.1.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.1.2"
resolved "https://registry.yarnpkg.com/unc-path-regex/-/unc-path-regex-0.1.2.tgz#e73dd3d7b0d7c5ed86fbac6b0ae7d8c6a69d50fa"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-5z3T17DXxe2G+6xrCufYxqadUPo=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
underscore@1.x:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.9.1"
resolved "https://registry.yarnpkg.com/underscore/-/underscore-1.9.1.tgz#06dce34a0e68a7babc29b365b8e74b8925203961"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-5/4etnCkd9c8gwgowi5/om/mYO5ajCaOgdzj/oW+0eQV9WxKBDZw5+ycmKmeaTXjInS/W0BzpGLo2xR2aBwZdg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
unicoderegexp@^0.4.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.4.1"
resolved "https://registry.yarnpkg.com/unicoderegexp/-/unicoderegexp-0.4.1.tgz#afb10e4ef1eeddc711417bbb652bc885da9d4171"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-r7EOTvHu3ccRQXu7ZSvIhdqdQXE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
union-value@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/union-value/-/union-value-1.0.0.tgz#5c71c34cb5bad5dcebe3ea0cd08207ba5aa1aea4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-XHHDTLW61dzr4+oM0IIHulqhrqQ=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
arr-union "^3.1.0"
get-value "^2.0.6"
is-extendable "^0.1.1"
set-value "^0.4.3"
build: update to rules_nodejs 0.38 (#32889) PR Close #32889
2019-09-27 18:49:59 -04:00
union@~0.4.3:
version "0.4.6"
resolved "https://registry.yarnpkg.com/union/-/union-0.4.6.tgz#198fbdaeba254e788b0efcb630bc11f24a2959e0"
integrity sha1-GY+9rrolTniLDvy2MLwR8kopWeA=
dependencies:
qs "~2.3.3"
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
unique-filename@^1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/unique-filename/-/unique-filename-1.1.1.tgz#1d69769369ada0583103a1e6ae87681b56573230"
integrity sha512-Vmp0jIp2ln35UTXuryvjzkjGdRyf9b2lTXuSYUiPmzRcl3FDtYqAwOnTJkAngD9SWhnoJzDbTKwaOrZ+STtxNQ==
dependencies:
unique-slug "^2.0.0"
unique-slug@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/unique-slug/-/unique-slug-2.0.1.tgz#5e9edc6d1ce8fb264db18a507ef9bd8544451ca6"
integrity sha512-n9cU6+gITaVu7VGj1Z8feKMmfAjEAQGhwD9fE3zvpRRa0wEIx8ODYkVGfSc94M2OX00tUFV8wH3zYbm1I8mxFg==
dependencies:
imurmurhash "^0.1.4"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
unique-stream@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/unique-stream/-/unique-stream-1.0.0.tgz#d59a4a75427447d9aa6c91e70263f8d26a4b104b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-1ZpKdUJ0R9mqbJHnAmP40mpLEEs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
unique-string@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/unique-string/-/unique-string-1.0.0.tgz#9e1057cca851abb93398f8b33ae187b99caec11a"
integrity sha1-nhBXzKhRq7kzmPizOuGHuZyuwRo=
dependencies:
crypto-random-string "^1.0.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
universal-analytics@0.4.15:
version "0.4.15"
resolved "https://registry.yarnpkg.com/universal-analytics/-/universal-analytics-0.4.15.tgz#4abc61b159ffe765be144e07b7b739e0ee7b88ab"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-9Dt6WBWsHsmv74G+N/rmEgi6KFZxVvQXkVhr0disegeUryybQAUQwMD1l5EtqaOu+hSOGbhL/hPPQYisZIqPRw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
async "1.2.x"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
request "2.x"
underscore "1.x"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
uuid "^3.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
universal-analytics@^0.4.16, universal-analytics@^0.4.20:
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
version "0.4.20"
resolved "https://registry.yarnpkg.com/universal-analytics/-/universal-analytics-0.4.20.tgz#d6b64e5312bf74f7c368e3024a922135dbf24b03"
integrity sha512-gE91dtMvNkjO+kWsPstHRtSwHXz0l2axqptGYp5ceg4MsuurloM0PU3pdOfpb5zBXUvyjT4PwhWK2m39uczZuw==
dependencies:
debug "^3.0.0"
request "^2.88.0"
uuid "^3.0.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
universalify@^0.1.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.1.2"
resolved "https://registry.yarnpkg.com/universalify/-/universalify-0.1.2.tgz#b646f69be3942dabcecc9d6639c80dc105efaa66"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-rBJeI5CXAlmy1pV+617WB9J63U6XcazHHF2f2dbJix4XzpUF0RS3Zbj0FGIOCAva5P/d/GBOYaACQ1w+0azUkg==
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
unpipe@1.0.0, unpipe@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/unpipe/-/unpipe-1.0.0.tgz#b2bf4ee8514aae6165b4817829d21b2ef49904ec"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-sr9O6FFKrmFltIF4KdIbLvSZBOw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
unset-value@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/unset-value/-/unset-value-1.0.0.tgz#8376873f7d2335179ffb1e6fc3a8ed0dfc8ab559"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-g3aHP30jNRef+x5vw6jtDfyKtVk=
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
has-value "^0.3.1"
isobject "^3.0.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
unzip-response@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/unzip-response/-/unzip-response-2.0.1.tgz#d2f0f737d16b0615e72a6935ed04214572d56f97"
integrity sha1-0vD3N9FrBhXnKmk17QQhRXLVb5c=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
unzip@~0.1.9:
version "0.1.11"
resolved "https://registry.yarnpkg.com/unzip/-/unzip-0.1.11.tgz#89749c63b058d7d90d619f86b98aa1535d3b97f0"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-iXScY7BY19kNYZ+GuYqhU107l/A=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
binary ">= 0.3.0 < 1"
fstream ">= 0.1.30 < 1"
match-stream ">= 0.0.2 < 1"
pullstream ">= 0.4.1 < 1"
readable-stream "~1.0.31"
setimmediate ">= 1.0.1 < 2"
build(compiler-cli): upgrade chokidar to latest version (#28797) Fixes #28771 PR Close #28797
2019-02-18 08:11:03 -05:00
upath@^1.0.5, upath@^1.1.0:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.1.0"
resolved "https://registry.yarnpkg.com/upath/-/upath-1.1.0.tgz#35256597e46a581db4793d0ce47fa9aebfc9fabd"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-bzpH/oBhoS/QI/YtbkqCg6VEiPYjSZtrHQM6/QnJS6OL9pKUFLqb3aFh4Scvwm45+7iAgiMkLhSbaZxUqmrprw==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
update-notifier@^2.5.0:
version "2.5.0"
resolved "https://registry.yarnpkg.com/update-notifier/-/update-notifier-2.5.0.tgz#d0744593e13f161e406acb1d9408b72cad08aff6"
integrity sha512-gwMdhgJHGuj/+wHJJs9e6PcCszpxR1b236igrOkUofGhqJuG+amlIKwApH1IW1WWl7ovZxsX49lMBWLxSdm5Dw==
dependencies:
boxen "^1.2.1"
chalk "^2.0.1"
configstore "^3.0.0"
import-lazy "^2.1.0"
is-ci "^1.0.10"
is-installed-globally "^0.1.0"
is-npm "^1.0.0"
latest-version "^3.0.0"
semver-diff "^2.0.0"
xdg-basedir "^3.0.0"
feat(bazel): Bazel workspace schematics (#26971) This commit creates a schematics for Bazel workspace. PR Close #26971
2018-09-14 10:03:29 -04:00
uri-js@^4.2.2:
version "4.2.2"
resolved "https://registry.yarnpkg.com/uri-js/-/uri-js-4.2.2.tgz#94c540e1ff772956e2299507c010aea6c8838eb0"
integrity sha512-KY9Frmirql91X2Qgjry0Wd4Y+YTdrdZheS8TFwvkbLWf/G5KNJDCh6pKL5OZctEW4+0Baa5idK2ZQuELRwPznQ==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
punycode "^2.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
urix@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/urix/-/urix-0.1.0.tgz#da937f7a62e21fec1fd18d49b35c2935067a6c72"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-2pN/emLiH+wf0Y1Js1wpNQZ6bHI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
url-join@0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/url-join/-/url-join-0.0.1.tgz#1db48ad422d3402469a87f7d97bdebfe4fb1e3c8"
integrity sha1-HbSK1CLTQCRpqH99l73r/k+x48g=
build: update to rules_nodejs 0.38 (#32889) PR Close #32889
2019-09-27 18:49:59 -04:00
url-join@^2.0.5:
version "2.0.5"
resolved "https://registry.yarnpkg.com/url-join/-/url-join-2.0.5.tgz#5af22f18c052a000a48d7b82c5e9c2e2feeda728"
integrity sha1-WvIvGMBSoACkjXuCxenC4v7tpyg=
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
url-parse-lax@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/url-parse-lax/-/url-parse-lax-1.0.0.tgz#7af8f303645e9bd79a272e7a14ac68bc0609da73"
integrity sha1-evjzA2Rem9eaJy56FKxovAYJ2nM=
dependencies:
prepend-http "^1.0.1"
url-parse-lax@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/url-parse-lax/-/url-parse-lax-3.0.0.tgz#16b5cafc07dbe3676c1b1999177823d6503acb0c"
integrity sha1-FrXK/Afb42dsGxmZF3gj1lA6yww=
dependencies:
prepend-http "^2.0.0"
url-to-options@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/url-to-options/-/url-to-options-1.0.1.tgz#1505a03a289a48cbd7a434efbaeec5055f5633a9"
integrity sha1-FQWgOiiaSMvXpDTvuu7FBV9WM6k=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
url@~0.10.1:
version "0.10.3"
resolved "https://registry.yarnpkg.com/url/-/url-0.10.3.tgz#021e4d9c7705f21bbf37d03ceb58767402774c64"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Ah5NnHcF8hu/N9A861h2dAJ3TGQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
punycode "1.3.2"
querystring "0.2.0"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
use@^3.1.0:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "3.1.1"
resolved "https://registry.yarnpkg.com/use/-/use-3.1.1.tgz#d50c8cac79a19fbc20f2911f56eb973f4e10070f"
integrity sha512-cwESVXlO3url9YWlFW/TA9cshCEhtu7IKJ/p5soJ/gGpj7vbvFrAY/eIioQ6Dw23KjZhYgiIo8HOs1nQ2vr/oQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
user-home@^1.1.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.1.1"
resolved "https://registry.yarnpkg.com/user-home/-/user-home-1.1.1.tgz#2b5be23a32b63a7c9deb8d0f28d485724a3df190"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-K1viOjK2Onyd640PKNSFcko98ZA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
user-home@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/user-home/-/user-home-2.0.0.tgz#9c70bfd8169bc1dcbf48604e0f04b8b49cde9e9f"
integrity sha1-nHC/2Babwdy/SGBODwS4tJzenp8=
dependencies:
os-homedir "^1.0.0"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
useragent@2.3.0:
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
version "2.3.0"
resolved "https://registry.yarnpkg.com/useragent/-/useragent-2.3.0.tgz#217f943ad540cb2128658ab23fc960f6a88c9972"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-4AoH4pxuSvHCjqLO04sU6U/uE65BYza8l/KKBS0b0hnUPWi+cQ2BpeTEwejCSx9SPV5/U03nniDTrWx5NrmKdw==
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488
2018-10-04 16:14:14 -04:00
dependencies:
lru-cache "4.1.x"
tmp "0.0.x"
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
util-deprecate@~1.0.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/util-deprecate/-/util-deprecate-1.0.2.tgz#450d4dc9fa70de732762fbd2d4a28981419a0ccf"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-RQ1Nyfpw3nMnYvvS1KKJgUGaDM8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
util@0.10.3:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.10.3"
resolved "https://registry.yarnpkg.com/util/-/util-0.10.3.tgz#7afb1afe50805246489e3db7fe0ed379336ac0f9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-evsa/lCAUkZInj23/g7TeTNqwPk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
inherits "2.0.1"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
util@~0.10.3:
version "0.10.4"
resolved "https://registry.yarnpkg.com/util/-/util-0.10.4.tgz#3aa0125bfe668a4672de58857d3ace27ecb76901"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-0Pm9hTQ3se5ll1XihRic3FDIku70C+iHUdT/W926rSgHV5QgXsYbKZN8MSC3tJtSkhuROzvsQjAaFENRXr+19A==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
dependencies:
inherits "2.0.3"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
utile@0.3.x:
version "0.3.0"
resolved "https://registry.yarnpkg.com/utile/-/utile-0.3.0.tgz#1352c340eb820e4d8ddba039a4fbfaa32ed4ef3a"
integrity sha1-E1LDQOuCDk2N26A5pPv6oy7U7zo=
dependencies:
async "~0.9.0"
deep-equal "~0.2.1"
i "0.3.x"
mkdirp "0.x.x"
ncp "1.0.x"
rimraf "2.x.x"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
utils-merge@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/utils-merge/-/utils-merge-1.0.0.tgz#0294fb922bb9375153541c4f7096231f287c8af8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-ApT7kiu5N1FTVBxPcJYjHyh8ivg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
utils-merge@1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/utils-merge/-/utils-merge-1.0.1.tgz#9f95710f50a267947b2ccc124741c1028427e713"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-n5VxD1CiZ5R7LMwSR0HBAoQn5xM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
uuid@3.2.1:
version "3.2.1"
resolved "https://registry.yarnpkg.com/uuid/-/uuid-3.2.1.tgz#12c528bb9d58d0b9265d9a2f6f0fe8be17ff1f14"
integrity sha512-jZnMwlb9Iku/O3smGWvZhauCf6cvvpKi4BKRiliS3cxnI+Gz9j5MEpTz2UFuXiKPJocb7gnsLHwiS05ige5BEA==
uuid@^2.0.1:
version "2.0.3"
resolved "https://registry.yarnpkg.com/uuid/-/uuid-2.0.3.tgz#67e2e863797215530dff318e5bf9dcebfd47b21a"
integrity sha1-Z+LoY3lyFVMN/zGOW/nc6/1Hsho=
uuid@^3.0.0, uuid@^3.1.0, uuid@^3.3.2:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "3.3.2"
resolved "https://registry.yarnpkg.com/uuid/-/uuid-3.3.2.tgz#1b4af4955eb3077c501c23872fc6513811587131"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-yXJmeNaw3DnnKAOKJE51sL/ZaYfWJRl1pK9dr19YFCu0ObS231AB1/LbqTKRAQ5kw8A90rA6fr4riOUpTZvQZA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
v8-coverage@1.0.9:
version "1.0.9"
resolved "https://registry.yarnpkg.com/v8-coverage/-/v8-coverage-1.0.9.tgz#780889680c0fea0f587adf22e2b5f443b9434745"
integrity sha512-JolsCH1JDI2QULrxkAGZaovJPvg/Q0p20Uj0F5N8fPtYDtz38gNBRPQ/WVXlLLd3d8WHvKN96AfE4XFk4u0g2g==
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
dependencies:
debug "^3.1.0"
foreground-child "^1.5.6"
istanbul-lib-coverage "^1.2.0"
istanbul-lib-report "^1.1.3"
istanbul-reports "^1.3.0"
mkdirp "^0.5.1"
rimraf "^2.6.2"
signal-exit "^3.0.2"
spawn-wrap "^1.4.2"
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
test-exclude "^5.2.2"
uuid "^3.3.2"
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
v8-to-istanbul "1.2.0"
yargs "^11.0.0"
v8-to-istanbul@1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/v8-to-istanbul/-/v8-to-istanbul-1.2.0.tgz#f6a22ffb08b2202aaba8c2be497d1d41fe8fb4b6"
integrity sha512-rVSmjdEfJmOHN8GYCbg+XUhbzXZr7DzdaXIslB9DdcopGZEMsW5x5qIdxr/8DcW7msULHNnvs/xUY1TszvhKRw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
v8flags@^2.0.2:
version "2.1.1"
resolved "https://registry.yarnpkg.com/v8flags/-/v8flags-2.1.1.tgz#aab1a1fa30d45f88dd321148875ac02c0b55e5b4"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-qrGh+jDUX4jdMhFIh1rALAtV5bQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
user-home "^1.1.1"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
valid-url@^1:
version "1.0.9"
resolved "https://registry.yarnpkg.com/valid-url/-/valid-url-1.0.9.tgz#1c14479b40f1397a75782f115e4086447433a200"
integrity sha1-HBRHm0DxOXp1eC8RXkCGRHQzogA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
validate-npm-package-license@^3.0.1:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "3.0.4"
resolved "https://registry.yarnpkg.com/validate-npm-package-license/-/validate-npm-package-license-3.0.4.tgz#fc91f6b9c7ba15c857f4cb2c5defeec39d4f410a"
integrity sha512-DpKm2Ui/xN7/HQKCtpZxoRWBhZ9Z0kqtygG8XCgNQ8ZlDnxuQmWhj566j8fN4Cu3/JmbhsDo7fcAJq4s9h27Ew==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
spdx-correct "^3.0.0"
spdx-expression-parse "^3.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
validate-npm-package-name@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/validate-npm-package-name/-/validate-npm-package-name-3.0.0.tgz#5fa912d81eb7d0c74afc140de7317f0ca7df437e"
integrity sha1-X6kS2B630MdK/BQN5zF/DKffQ34=
dependencies:
builtins "^1.0.3"
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
validator@^8.0.0:
version "8.2.0"
resolved "https://registry.yarnpkg.com/validator/-/validator-8.2.0.tgz#3c1237290e37092355344fef78c231249dab77b9"
integrity sha512-Yw5wW34fSv5spzTXNkokD6S6/Oq92d8q/t14TqsS3fAiA1RYnxSFSIZ+CY3n6PGGRCq5HhJTSepQvFUS2QUDxA==
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
vary@^1, vary@~1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/vary/-/vary-1.1.2.tgz#2299f02c6ded30d4a5961b0b9f74524a18f634fc"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-IpnwLG3tMNSllhsLn3RSShj2NPw=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
vary@~1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/vary/-/vary-1.0.1.tgz#99e4981566a286118dfb2b817357df7993376d10"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-meSYFWaihhGN+yuBc1ffeZM3bRA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
verror@1.10.0:
version "1.10.0"
resolved "https://registry.yarnpkg.com/verror/-/verror-1.10.0.tgz#3a105ca17053af55d6e270c1f8288682e18da400"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-OhBcoXBTr1XW4nDB+CiGguGNpAA=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
assert-plus "^1.0.0"
core-util-is "1.0.2"
extsprintf "^1.2.0"
vhost@~3.0.1:
version "3.0.2"
resolved "https://registry.yarnpkg.com/vhost/-/vhost-3.0.2.tgz#2fb1decd4c466aa88b0f9341af33dc1aff2478d5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-L7HezUxGaqiLD5NBrzPcGv8keNU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
vinyl-fs@^0.3.0:
version "0.3.14"
resolved "https://registry.yarnpkg.com/vinyl-fs/-/vinyl-fs-0.3.14.tgz#9a6851ce1cac1c1cea5fe86c0931d620c2cfa9e6"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-mmhRzhysHBzqX+hsCTHWIMLPqeY=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
defaults "^1.0.0"
glob-stream "^3.1.5"
glob-watcher "^0.0.6"
graceful-fs "^3.0.0"
mkdirp "^0.5.0"
strip-bom "^1.0.0"
through2 "^0.6.1"
vinyl "^0.4.0"
vinyl@^0.4.0:
version "0.4.6"
resolved "https://registry.yarnpkg.com/vinyl/-/vinyl-0.4.6.tgz#2f356c87a550a255461f36bbeb2a5ba8bf784847"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-LzVsh6VQolVGHza76ypbqL94SEc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
clone "^0.2.0"
clone-stats "^0.0.1"
vinyl@^0.5.0:
version "0.5.3"
resolved "https://registry.yarnpkg.com/vinyl/-/vinyl-0.5.3.tgz#b0455b38fc5e0cf30d4325132e461970c2091cde"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-sEVbOPxeDPMNQyUTLkYZcMIJHN4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
clone "^1.0.0"
clone-stats "^0.0.1"
replace-ext "0.0.1"
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
vinyl@^2.0.1:
version "2.2.0"
resolved "https://registry.yarnpkg.com/vinyl/-/vinyl-2.2.0.tgz#d85b07da96e458d25b2ffe19fece9f2caa13ed86"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-MBH+yP0kC/GQ5GwBqrTPTzEfiiLjta7hTtvQtbxBgTeSXsmKQRQecjibMbxIXzVT3Y9KJK+drOz1/k+vsu8Nkg==
style: add gulp task to only format changed files (#24969) Closes #24904 PR Close #24969
2018-07-18 12:09:55 -04:00
dependencies:
clone "^2.1.1"
clone-buffer "^1.0.0"
clone-stats "^1.0.0"
cloneable-readable "^1.0.0"
remove-trailing-separator "^1.0.1"
replace-ext "^1.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
vlq@0.2.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.2.2"
resolved "https://registry.yarnpkg.com/vlq/-/vlq-0.2.2.tgz#e316d5257b40b86bb43cb8d5fea5d7f54d6b0ca1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-4xbVJXtAuGu0PLjV/qXX9U1rDKE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
vm-browserify@0.0.4:
version "0.0.4"
resolved "https://registry.yarnpkg.com/vm-browserify/-/vm-browserify-0.0.4.tgz#5d7ea45bbef9e4a6ff65f95438e0a87c357d5a73"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-XX6kW7755Kb/ZflUOOCofDV9WnM=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
indexof "0.0.1"
void-elements@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/void-elements/-/void-elements-2.0.1.tgz#c066afb582bb1cb4128d60ea92392e94d5e9dbec"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wGavtYK7HLQSjWDqkjkulNXp2+w=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
vrsource-tslint-rules@5.1.1:
version "5.1.1"
resolved "https://registry.yarnpkg.com/vrsource-tslint-rules/-/vrsource-tslint-rules-5.1.1.tgz#9bef7a60bc34f6cdc637d7ba1b8d745b71f6dcbe"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-m+96YLw09s3GN9e6G410W3H23L4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
tslint "~5.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
walkdir@0.0.5:
version "0.0.5"
resolved "https://registry.yarnpkg.com/walkdir/-/walkdir-0.0.5.tgz#8b36be89c4f189249fd2d931cf133ba0c1c6fde8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-iza+icTxiSSf0tkxzxM7oMHG/eg=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
walkdir@^0.0.11:
version "0.0.11"
resolved "https://registry.yarnpkg.com/walkdir/-/walkdir-0.0.11.tgz#a16d025eb931bd03b52f308caed0f40fcebe9532"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-oW0CXrkxvQO1LzCMrtD0D86+lTI=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
watchpack@^0.2.1:
version "0.2.9"
resolved "https://registry.yarnpkg.com/watchpack/-/watchpack-0.2.9.tgz#62eaa4ab5e5ba35fdfc018275626e3c0f5e3fb0b"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Yuqkq15bo1/fwBgnVibjwPXj+ws=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
async "^0.9.0"
chokidar "^1.0.0"
graceful-fs "^4.1.2"
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
webdriver-js-extender@2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/webdriver-js-extender/-/webdriver-js-extender-2.1.0.tgz#57d7a93c00db4cc8d556e4d3db4b5db0a80c3bb7"
integrity sha512-lcUKrjbBfCK6MNsh7xaY2UAUmZwe+/ib03AjVOpFobX4O7+83BUveSrLfU0Qsyb1DaKJdQRbuU+kM9aZ6QUhiQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
ci: move e2e tests from travis to circleci (#27937) PR Close #27937
2019-01-05 08:01:47 -05:00
"@types/selenium-webdriver" "^3.0.0"
selenium-webdriver "^3.0.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
webdriver-manager@^12.0.6:
ci: update nodejs version to v10.16.0 (#31088) Updates the NodeJS version to the latest stable version at the time of writing (v10.16.0). We need to update our image to use a minimum NodeJS version of v10.15.0 because new CLI apps automatically install a non-locked version of selenium-webdriver that now requires NodeJS >= 10.15.0 since the latest release of 17th June 2019 (4.0.0-alpha.3). See CI failures: https://circleci.com/gh/angular/angular/359077 PR Close #31088
2019-06-17 13:17:19 -04:00
version "12.1.5"
resolved "https://registry.yarnpkg.com/webdriver-manager/-/webdriver-manager-12.1.5.tgz#28817b14d4b16b94ede10d5a7ee187aeb7679edf"
integrity sha512-f1apDjMpZ8SHlXtXGzqBxOjV+WQcDRz5PN7pWScgjXS7vhUIFcM3V89Shetf4A04n8DDR2MxiVQq6JproFcRZw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
adm-zip "^0.4.9"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
chalk "^1.1.1"
del "^2.2.0"
glob "^7.0.3"
ini "^1.3.4"
minimist "^1.2.0"
q "^1.4.1"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
request "^2.87.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
rimraf "^2.5.2"
semver "^5.3.0"
xml2js "^0.4.17"
webpack-core@~0.6.0:
version "0.6.9"
resolved "https://registry.yarnpkg.com/webpack-core/-/webpack-core-0.6.9.tgz#fc571588c8558da77be9efb6debdc5a3b172bdc2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-/FcViMhVjad76e+23r3Fo7FyvcI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
source-list-map "~0.1.7"
source-map "~0.4.1"
build: update version of Angular CLI and Build Optimizer used for tests (#28372) PR Close #28372
2019-01-25 11:33:22 -05:00
webpack-sources@1.3.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/webpack-sources/-/webpack-sources-1.3.0.tgz#2a28dcb9f1f45fe960d8f1493252b5ee6530fa85"
integrity sha512-OiVgSrbGu7NEnEvQJJgdSFPl2qWKkWq5lHMhgiToIiN9w34EBnjYzSYs+VbL5KoYiLNtFFa7BZIKxRED3I32pA==
build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) The current build workflow depends on cross workspace dependency by installing angular-cli as a Bazel repository. This is not ideal because it introduces separate node_module directories other than the one installed by Angular through the yarn_install rule (ngdeps). This commit removes angular-cli from the Bazel workspace and installs rollup and @angular-devkit/build-optimizer locally. PR Close #28215
2019-01-17 15:40:11 -05:00
dependencies:
source-list-map "^2.0.0"
source-map "~0.6.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
webpack@1.12.9:
version "1.12.9"
resolved "https://registry.yarnpkg.com/webpack/-/webpack-1.12.9.tgz#2a031d66189839cc5cbf2c68f80566da2e14ff4e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-KgMdZhiYOcxcvyxo+AVm2i4U/04=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
async "^1.3.0"
clone "^1.0.2"
enhanced-resolve "~0.9.0"
esprima "^2.5.0"
interpret "^0.6.4"
loader-utils "^0.2.11"
memory-fs "~0.3.0"
mkdirp "~0.5.0"
node-libs-browser ">= 0.4.0 <=0.6.0"
optimist "~0.6.0"
supports-color "^3.1.0"
tapable "~0.1.8"
uglify-js "~2.6.0"
watchpack "^0.2.1"
webpack-core "~0.6.0"
websocket-driver@>=0.5.1:
version "0.7.0"
resolved "https://registry.yarnpkg.com/websocket-driver/-/websocket-driver-0.7.0.tgz#0caf9d2d755d93aee049d4bdd0d3fe2cca2a24eb"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-DK+dLXVdk67gSdS90NP+LMoqJOs=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
http-parser-js ">=0.4.0"
websocket-extensions ">=0.1.1"
websocket-extensions@>=0.1.1:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "0.1.3"
resolved "https://registry.yarnpkg.com/websocket-extensions/-/websocket-extensions-0.1.3.tgz#5d2ff22977003ec687a4b87073dfbbac146ccf29"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-nqHUnMXmBzT0w570r2JpJxfiSD1IzoI+HGVdd3aZ0yNi3ngvQ4jv1dtHt5VGxfI2yj5yqImPhOK4vmIh2xMbGg==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
when@3.7.2:
version "3.7.2"
resolved "https://registry.yarnpkg.com/when/-/when-3.7.2.tgz#06bed1296df3a0bfd83f7f31c5e1d779bd97eae8"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Br7RKW3zoL/YP38xxeHXeb2X6ug=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
when@3.7.7:
version "3.7.7"
resolved "https://registry.yarnpkg.com/when/-/when-3.7.7.tgz#aba03fc3bb736d6c88b091d013d8a8e590d84718"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-q6A/w7tzbWyIsJHQE9io5ZDYRxg=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 (#28532) PR Close #28532
2019-02-04 18:53:32 -05:00
when@^3.7.2:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "3.7.8"
resolved "https://registry.yarnpkg.com/when/-/when-3.7.8.tgz#c7130b6a7ea04693e842cdc9e7a1f2aa39a39f82"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-xxMLan6gRpPoQs3J56Hyqjmjn4I=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
which-module@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/which-module/-/which-module-2.0.0.tgz#d9ef07dce77b9902b8a3a8fa4b31c3e3f7e6e87a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-2e8H3Od7mQK4o6j6SzHD4/fm6Ho=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
which@1.2.4:
version "1.2.4"
resolved "https://registry.yarnpkg.com/which/-/which-1.2.4.tgz#1557f96080604e5b11b3599eb9f45b50a9efd722"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-FVf5YIBgTlsRs1meufRbUKnv1yI=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
is-absolute "^0.1.7"
isexe "^1.1.1"
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
which@^1.2.1, which@^1.2.14, which@^1.2.9, which@^1.3.0, which@^1.3.1:
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
version "1.3.1"
resolved "https://registry.yarnpkg.com/which/-/which-1.3.1.tgz#a45043d54f5805316da8d62f9f50918d3da70b0a"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-HxJdYWq1MTIQbJ3nw0cqssHoTNU267KlrDuGZ1WYlxDStUtKUhOaJmh112/TZmHxxUfuJqPXSOm7tDyas0OSIQ==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
isexe "^2.0.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
wide-align@^1.1.0:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
version "1.1.3"
resolved "https://registry.yarnpkg.com/wide-align/-/wide-align-1.1.3.tgz#ae074e6bdc0c14a431e804e624549c633b000457"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-QGkOQc8XL6Bt5PwnsExKBPuMKBxnGxWWW3fU55Xt4feHozMUhdUMaBCk290qpm/wG5u/RSKzwdAC4i51YigihA==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
string-width "^1.0.2 || 2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
widest-line@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/widest-line/-/widest-line-2.0.1.tgz#7438764730ec7ef4381ce4df82fb98a53142a3fc"
integrity sha512-Ba5m9/Fa4Xt9eb2ELXt77JxVDV8w7qQrH0zS/TWSJdLyAwQjWoOzpzj5lwVftDz6n/EOu3tNACS84v509qwnJA==
dependencies:
string-width "^2.1.1"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
window-size@0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/window-size/-/window-size-0.1.0.tgz#5438cd2ea93b202efa3a19fe8887aee7c94f9c9d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-VDjNLqk7IC76Ohn+iIeu58lPnJ0=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
winreg@0.0.12:
version "0.0.12"
resolved "https://registry.yarnpkg.com/winreg/-/winreg-0.0.12.tgz#07105554ba1a9d08979251d129475bffae3006b7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-BxBVVLoanQiXklHRKUdb/64wBrc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
winston@2.1.x:
version "2.1.1"
resolved "https://registry.yarnpkg.com/winston/-/winston-2.1.1.tgz#3c9349d196207fd1bdff9d4bc43ef72510e3a12e"
integrity sha1-PJNJ0ZYgf9G9/51LxD73JRDjoS4=
dependencies:
async "~1.0.0"
colors "1.0.x"
cycle "1.0.x"
eyes "0.1.x"
isstream "0.1.x"
pkginfo "0.3.x"
stack-trace "0.0.x"
winston@2.4.0:
version "2.4.0"
resolved "https://registry.yarnpkg.com/winston/-/winston-2.4.0.tgz#808050b93d52661ed9fb6c26b3f0c826708b0aee"
integrity sha1-gIBQuT1SZh7Z+2wms/DIJnCLCu4=
dependencies:
async "~1.0.0"
colors "1.0.x"
cycle "1.0.x"
eyes "0.1.x"
isstream "0.1.x"
stack-trace "0.0.x"
winston@^1.0.1:
version "1.1.2"
resolved "https://registry.yarnpkg.com/winston/-/winston-1.1.2.tgz#68edd769ff79d4f9528cf0e5d80021aade67480c"
integrity sha1-aO3Xaf951PlSjPDl2AAhqt5nSAw=
dependencies:
async "~1.0.0"
colors "1.0.x"
cycle "1.0.x"
eyes "0.1.x"
isstream "0.1.x"
pkginfo "0.3.x"
stack-trace "0.0.x"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
wordwrap@0.0.2:
version "0.0.2"
resolved "https://registry.yarnpkg.com/wordwrap/-/wordwrap-0.0.2.tgz#b79669bb42ecb409f83d583cad52ca17eaa1643f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-t5Zpu0LstAn4PVg8rVLKF+qhZD8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
wordwrap@~0.0.2:
version "0.0.3"
resolved "https://registry.yarnpkg.com/wordwrap/-/wordwrap-0.0.3.tgz#a3d5da6cd5c0bc0008d37234bbaf1bed63059107"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-o9XabNXAvAAI03I0u68b7WMFkQc=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.8 (#29508) * fixes prodmode issue in integration/bazel BREAKING CHANGE: @bazel/typescript is now a peerDependency of @angular/bazel so user's of @angular/bazel must add @bazel/typescript to their package.json PR Close #29508
2019-03-25 14:06:10 -04:00
wordwrap@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/wordwrap/-/wordwrap-1.0.0.tgz#27584810891456a4171c8d0226441ade90cbcaeb"
integrity sha1-J1hIEIkUVqQXHI0CJkQa3pDLyus=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
wrap-ansi@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/wrap-ansi/-/wrap-ansi-2.1.0.tgz#d8fc3d284dd05794fe84973caecdd1cf824fdd85"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-2Pw9KE3QV5T+hJc8rs3Rz4JP3YU=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
string-width "^1.0.1"
strip-ansi "^3.0.1"
wrappy@1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/wrappy/-/wrappy-1.0.2.tgz#b5243d8f3ec1aa35f1364605bc0d1036e30ab69f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-tSQ9jz7BqjXxNkYFvA0QNuMKtp8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
write-file-atomic@^1.1.2:
version "1.3.4"
resolved "https://registry.yarnpkg.com/write-file-atomic/-/write-file-atomic-1.3.4.tgz#f807a4f0b1d9e913ae7a48112e6cc3af1991b45f"
integrity sha1-+Aek8LHZ6ROuekgRLmzDrxmRtF8=
dependencies:
graceful-fs "^4.1.11"
imurmurhash "^0.1.4"
slide "^1.1.5"
write-file-atomic@^2.0.0:
version "2.4.2"
resolved "https://registry.yarnpkg.com/write-file-atomic/-/write-file-atomic-2.4.2.tgz#a7181706dfba17855d221140a9c06e15fcdd87b9"
integrity sha512-s0b6vB3xIVRLWywa6X9TOMA7k9zio0TMOsl9ZnDkliA/cfJlpHXAscj0gbHVJiTdIuAYpIyqS5GW91fqm6gG5g==
dependencies:
graceful-fs "^4.1.11"
imurmurhash "^0.1.4"
signal-exit "^3.0.2"
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
ws@~3.3.1:
version "3.3.3"
resolved "https://registry.yarnpkg.com/ws/-/ws-3.3.3.tgz#f1cf84fe2d5e901ebce94efaece785f187a228f2"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-nnWLa/NwZSt4KQJu51MYlCcSQ5g7INpOrOMt4XV8j4dqTXdmlUmSHQ8/oLC069ckre0fRsgfvsKwbTdtKLCDkA==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
dependencies:
async-limiter "~1.0.0"
safe-buffer "~5.1.0"
ultron "~1.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
xdg-basedir@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/xdg-basedir/-/xdg-basedir-2.0.0.tgz#edbc903cc385fc04523d966a335504b5504d1bd2"
integrity sha1-7byQPMOF/ARSPZZqM1UEtVBNG9I=
dependencies:
os-homedir "^1.0.0"
xdg-basedir@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/xdg-basedir/-/xdg-basedir-3.0.0.tgz#496b2cc109eca8dbacfe2dc72b603c17c5870ad4"
integrity sha1-SWsswQnsqNus/i3HK2A8F8WHCtQ=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
xhr2@0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/xhr2/-/xhr2-0.1.4.tgz#7f87658847716db5026323812f818cadab387a5f"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-f4dliEdxbbUCYyOBL4GMras4el8=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
xml2js@0.4.16:
version "0.4.16"
resolved "https://registry.yarnpkg.com/xml2js/-/xml2js-0.4.16.tgz#f82fccd2f9540d7e0a9b5dac163e7471195c9db3"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-+C/M0vlUDX4Km12sFj50cRlcnbM=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
sax ">=0.6.0"
xmlbuilder "^4.1.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
xml2js@^0.4.17, xml2js@~0.4.4:
version "0.4.19"
resolved "https://registry.yarnpkg.com/xml2js/-/xml2js-0.4.19.tgz#686c20f213209e94abf0d1bcf1efaa291c7827a7"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-esZnJZJOiJR9wWKMyuvSE1y6Dq5LCuJanqhxslH2bxM6duahNZ+HMpCLhBQGZkbX6xRf8x1Y2eJlgt2q3qo49Q==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
sax ">=0.6.0"
xmlbuilder "~9.0.1"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
xmlbuilder@^4.1.0:
version "4.2.1"
resolved "https://registry.yarnpkg.com/xmlbuilder/-/xmlbuilder-4.2.1.tgz#aa58a3041a066f90eaa16c2f5389ff19f3f461a5"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-qlijBBoGb5DqoWwvU4n/GfP0YaU=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
lodash "^4.0.0"
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
xmlbuilder@~9.0.1:
version "9.0.7"
resolved "https://registry.yarnpkg.com/xmlbuilder/-/xmlbuilder-9.0.7.tgz#132ee63d2ec5565c557e20f4c22df9aca686b10d"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-Ey7mPS7FVlxVfiD0wi35rKaGsQ0=
build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) PR Close #24663
2018-06-25 14:22:23 -04:00
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
xmldom@^0.1.27:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "0.1.27"
resolved "https://registry.yarnpkg.com/xmldom/-/xmldom-0.1.27.tgz#d501f97b3bdb403af8ef9ecc20573187aadac0e9"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-1QH5ezvbQDr4757MIFcxh6rawOk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
xmlhttprequest-ssl@~1.5.4:
version "1.5.5"
resolved "https://registry.yarnpkg.com/xmlhttprequest-ssl/-/xmlhttprequest-ssl-1.5.5.tgz#c2876b06168aadc40e57d97e81191ac8f4398b3e"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-wodrBhaKrcQOV9l+gRkayPQ5iz4=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
fix(common): use correct ICU plural for locale mk (#24659) PR Close #24659
2018-06-25 11:17:56 -04:00
xpath@^0.0.27:
version "0.0.27"
resolved "https://registry.yarnpkg.com/xpath/-/xpath-0.0.27.tgz#dd3421fbdcc5646ac32c48531b4d7e9d0c2cfa92"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha512-fg03WRxtkCV6ohClePNAECYsmpKKTv5L8y/X3Dn1hQrec3POx2jHZ/0P2qQ6HvsrU1BmeqXcof3NGGueG6LxwQ==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
"xtend@>=4.0.0 <4.1.0-0", xtend@^4.0.0, xtend@^4.0.1, xtend@~4.0.0, xtend@~4.0.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "4.0.1"
resolved "https://registry.yarnpkg.com/xtend/-/xtend-4.0.1.tgz#a5c6d532be656e23db820efb943a1f04998d63af"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-pcbVMr5lbiPbgg77lDofBJmNY68=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build(bazel): update to nodejs rules 0.27.10 (#29694) PR Close #29694
2019-04-03 19:56:20 -04:00
y18n@^3.2.1:
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
version "3.2.1"
resolved "https://registry.yarnpkg.com/y18n/-/y18n-3.2.1.tgz#6d15fba884c08679c0d77e88e7759e811e07fa41"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-bRX7qITAhnnA136I53WegR4H+kE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
y18n@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/y18n/-/y18n-4.0.0.tgz#95ef94f85ecc81d007c264e190a120f0a3c8566b"
integrity sha512-r9S/ZyXu/Xu9q1tYlpsLIsa3EeLXXk0VwlxqTcFRfg9EhMW+17kbt9G0NrgCmhGb5vT2hyhJZLfDGx+7+5Uj/w==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
yallist@^2.1.2:
version "2.1.2"
resolved "https://registry.yarnpkg.com/yallist/-/yallist-2.1.2.tgz#1c11f9218f076089a47dd512f93c6699a6a81d52"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-HBH5IY8HYImkfdUS+TxmmaaoHVI=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
yallist@^3.0.0, yallist@^3.0.2:
test(bazel): Use local_repository to load Angular (#28061) The current integration test for Bazel schematics downloads a published version of Angular as required by the http_archive rule in the CLI created WORKSPACE. However, this makes the test less useful because it does not actually test any changes to the Angular repo at source. This PR replaces the http_archive method in the WORSPACE with local_repository so that any local changes to the Angular repo are tested accordingly. With Typescript 3.2, the file e2e/src/app.po.ts generated by CLI no longer compiles under Bazel due to missing type annotations. A temporary file is placed in the integration/bazel-schematics directory while the change is pending in CLI repo. https://github.com/angular/angular-cli/pull/13406 PR Close #28061
2019-01-10 19:04:05 -05:00
version "3.0.3"
resolved "https://registry.yarnpkg.com/yallist/-/yallist-3.0.3.tgz#b4b049e314be545e3ce802236d6cd22cd91c3de9"
integrity sha512-S+Zk8DEWE6oKpV+vI3qWkaK+jSbIK86pCwe2IF/xwIpQ8jEuxpw9NyaGjmp9+BoJv5FV2piqCDcoCtStppiq2A==
build: upgrade karma and related dependencies (#19904) PR Close #19904
2018-07-05 14:35:17 -04:00
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
yargs-parser@^13.0.0:
version "13.0.0"
resolved "https://registry.yarnpkg.com/yargs-parser/-/yargs-parser-13.0.0.tgz#3fc44f3e76a8bdb1cc3602e860108602e5ccde8b"
integrity sha512-w2LXjoL8oRdRQN+hOyppuXs+V/fVAYtpcrRxZuF7Kt/Oc+Jr2uAcVntaUTNT6w5ihoWfFDpNY8CPx1QskxZ/pw==
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
camelcase "^5.0.0"
decamelize "^1.2.0"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
yargs-parser@^9.0.2:
version "9.0.2"
resolved "https://registry.yarnpkg.com/yargs-parser/-/yargs-parser-9.0.2.tgz#9ccf6a43460fe4ed40a9bb68f48d43b8a68cc077"
integrity sha1-nM9qQ0YP5O1Aqbto9I1DuKaMwHc=
dependencies:
camelcase "^4.1.0"
yargs@11.0.0:
version "11.0.0"
resolved "https://registry.yarnpkg.com/yargs/-/yargs-11.0.0.tgz#c052931006c5eee74610e5fc0354bedfd08a201b"
integrity sha512-Rjp+lMYQOWtgqojx1dEWorjCofi1YN7AoFvYV7b1gx/7dAAeuI4kN5SZiEvr0ZmsZTOpDRcCqrpI10L31tFkBw==
dependencies:
cliui "^4.0.0"
decamelize "^1.1.1"
find-up "^2.1.0"
get-caller-file "^1.0.1"
os-locale "^2.0.0"
require-directory "^2.1.1"
require-main-filename "^1.0.1"
set-blocking "^2.0.0"
string-width "^2.0.0"
which-module "^2.0.0"
y18n "^3.2.1"
yargs-parser "^9.0.2"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
yargs@13.1.0:
version "13.1.0"
resolved "https://registry.yarnpkg.com/yargs/-/yargs-13.1.0.tgz#b2729ce4bfc0c584939719514099d8a916ad2301"
integrity sha512-1UhJbXfzHiPqkfXNHYhiz79qM/kZqjTE8yGlEjZa85Q+3+OwcV6NRkV7XOV1W2Eom2bzILeUn55pQYffjVOLAg==
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
cliui "^4.0.0"
find-up "^3.0.0"
get-caller-file "^2.0.1"
os-locale "^3.1.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
require-directory "^2.1.1"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
require-main-filename "^2.0.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
set-blocking "^2.0.0"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
string-width "^3.0.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
which-module "^2.0.0"
build: upgrade yargs package to 13.1.0 (#29722) Update yargs, because the old version was transitively (via os-local) depending on a vulnerable version of the mem package: https://app.snyk.io/vuln/npm:mem:20180117 PR Close #29722
2019-04-05 04:44:43 -04:00
y18n "^4.0.0"
yargs-parser "^13.0.0"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
build(bazel): update to nodejs rules 0.27.9 (#29647) PR Close #29647
2019-04-01 19:59:36 -04:00
yargs@^11.0.0:
version "11.1.0"
resolved "https://registry.yarnpkg.com/yargs/-/yargs-11.1.0.tgz#90b869934ed6e871115ea2ff58b03f4724ed2d77"
integrity sha512-NwW69J42EsCSanF8kyn5upxvjp5ds+t3+udGBeTbFnERA+lF541DDpMawzo4z6W/QrzNM18D+BPMiOBibnFV5A==
dependencies:
cliui "^4.0.0"
decamelize "^1.1.1"
find-up "^2.1.0"
get-caller-file "^1.0.1"
os-locale "^2.0.0"
require-directory "^2.1.1"
require-main-filename "^1.0.1"
set-blocking "^2.0.0"
string-width "^2.0.0"
which-module "^2.0.0"
y18n "^3.2.1"
yargs-parser "^9.0.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
yargs@~3.10.0:
version "3.10.0"
resolved "https://registry.yarnpkg.com/yargs/-/yargs-3.10.0.tgz#f7ee7bd857dd7c1d2d38c0e74efbd681d1431fd1"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-9+572FfdfB0tOMDnTvvWgdFDH9E=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
camelcase "^1.0.2"
cliui "^2.1.0"
decamelize "^1.0.0"
window-size "0.1.0"
yeast@0.1.2:
version "0.1.2"
resolved "https://registry.yarnpkg.com/yeast/-/yeast-0.1.2.tgz#008e06d8094320c372dbc2f8ed76a0ca6c8ac419"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-AI4G2AlDIMNy28L47XagymyKxBk=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
feat(bazel): add dts bundler as action to ng_module (#28588) This enabled dts flattening in the final distrubutable package. Notes: - For the time being this is an opt-in feature via the `ng_module` attribute `bundle_dts`, however in the near future this will be turned on by default. - This only supports the legacy compiler `ngc`, as `ngtsc` emits namespaced imports `import * as __` from local modules which is not supported for the time being by API Extractor. See: https://github.com/Microsoft/web-build-tools/issues/1029 Ref: TOOL-611 PR Close #28588
2019-02-07 13:02:07 -05:00
z-schema@~3.18.3:
version "3.18.4"
resolved "https://registry.yarnpkg.com/z-schema/-/z-schema-3.18.4.tgz#ea8132b279533ee60be2485a02f7e3e42541a9a2"
integrity sha512-DUOKC/IhbkdLKKiV89gw9DUauTV8U/8yJl1sjf6MtDmzevLKOF2duNJ495S3MFVjqZarr+qNGCPbkg4mu4PpLw==
dependencies:
lodash.get "^4.0.0"
lodash.isequal "^4.0.0"
validator "^8.0.0"
optionalDependencies:
commander "^2.7.1"
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
zip-dir@1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/zip-dir/-/zip-dir-1.0.2.tgz#253f907aead62a21acd8721d8b88032b2411c051"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-JT+QeurWKiGs2HIdi4gDKyQRwFE=
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
dependencies:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
async "^1.5.2"
build: switch from npm to yarn (#19328) PR Close #19328
2017-09-21 09:39:43 -04:00
jszip "^2.4.0"
ci: do not install firebase-tools without cache (#28615) Currently we install `firebase-tools` manually in the integration tests run script. This is problematic because it means that we cannot cache `firebase-tools` properly and Yarn might time out downloading this dependency. We can safely move this to the top level `package.json` since Bazel now has a `.bazelignore` and since we have a cache that works for PRs (with fallback caching). Note that the `.bazelignore` is relevant here because `firebase-tools` has been mainly moved to the bash script because it broke some Bazel calls. See 4f0cae067656fa4563417542297c67030d911a36. PR Close #28615
2019-02-08 04:25:52 -05:00
zip-stream@^1.0.0, zip-stream@^1.1.0, zip-stream@^1.2.0:
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/zip-stream/-/zip-stream-1.2.0.tgz#a8bc45f4c1b49699c6b90198baacaacdbcd4ba04"
build: restore integrity lines in yarn.lock (#26488) PR Close #26488
2018-10-16 16:52:32 -04:00
integrity sha1-qLxF9MG0lpnGuQGYuqyqzbzUugQ=
build: update npm dependencies (#19328) PR Close #19328
2017-09-22 13:51:03 -04:00
dependencies:
archiver-utils "^1.3.0"
compress-commons "^1.2.0"
lodash "^4.8.0"
readable-stream "^2.0.0"
build(zone.js): update zone.js to 0.10.2 (#31975) Bundle size changed in both zone.js(legacy) and zone-evergreen.js - zone.js(legacy) package increased a little because the following feature and fixes. 1. #31699, handle MSPointer events PR 2. https://github.com/angular/zone.js/pull/1219 to add __zone_symbol__ customization support - zone-evergreen.js package decreased because 1. the MSPointer PR only for legacy 2. the Object.defineProperty patch is moved to legacy #31660 PR Close #31975
2019-08-02 20:58:31 -04:00
zone.js@^0.10.2:
version "0.10.2"
resolved "https://registry.yarnpkg.com/zone.js/-/zone.js-0.10.2.tgz#67ca084b3116fc33fc40435e0d5ea40a207e392e"
integrity sha512-UAYfiuvxLN4oyuqhJwd21Uxb4CNawrq6fPS/05Su5L4G+1TN+HVDJMUHNMobVQDFJRir2cLAODXwluaOKB7HFg==