iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/integration/bazel/package.json

53 lines
1.9 KiB
JSON
Raw Normal View History

build: add bazel integration test (#18733) It includes sass compilation, and building the bazel package distribution. PR Close #18733
2017-08-21 11:23:47 -04:00
{
"name": "angular-bazel",
"description": "example and integration test for building Angular apps with Bazel",
"version": "0.0.0",
"license": "MIT",
"dependencies": {
build(bazel): update to nodejs rules 0.30.1 & bazel 0.26.0 (#30627) nodejs rules 0.30.1 has new feature to symlink node_modules with yarn_install and bazel 0.26.0 includes new managed_directories feature which enables this PR Close #30627
2019-05-22 20:28:42 -04:00
"@angular/animations": "file:../../dist/packages-dist/animations",
fix(bazel): exclude all angular schematics folders from metadata build (#31237) Fixes #31235 PR Close #31237
2019-06-24 10:43:26 -04:00
"@angular/cdk": "8.0.1",
build(bazel): update to nodejs rules 0.30.1 & bazel 0.26.0 (#30627) nodejs rules 0.30.1 has new feature to symlink node_modules with yarn_install and bazel 0.26.0 includes new managed_directories feature which enables this PR Close #30627
2019-05-22 20:28:42 -04:00
"@angular/common": "file:../../dist/packages-dist/common",
"@angular/core": "file:../../dist/packages-dist/core",
fix(bazel): exclude all angular schematics folders from metadata build (#31237) Fixes #31235 PR Close #31237
2019-06-24 10:43:26 -04:00
"@angular/forms": "file:../../dist/packages-dist/forms",
"@angular/material": "8.0.1",
build(bazel): update to nodejs rules 0.30.1 & bazel 0.26.0 (#30627) nodejs rules 0.30.1 has new feature to symlink node_modules with yarn_install and bazel 0.26.0 includes new managed_directories feature which enables this PR Close #30627
2019-05-22 20:28:42 -04:00
"@angular/platform-browser": "file:../../dist/packages-dist/platform-browser",
"@angular/platform-browser-dynamic": "file:../../dist/packages-dist/platform-browser-dynamic",
"@angular/router": "file:../../dist/packages-dist/router",
"reflect-metadata": "0.1.12",
test: update Angular CLI deps for integration tests (#32957) PR Close #32957
2019-10-02 07:28:23 -04:00
"rxjs": "file:../../node_modules/rxjs",
feat: typescript 3.6 support (#32946) BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6 Fixes #32380 PR Close #32946
2019-10-01 19:44:50 -04:00
"tslib": "file:../../node_modules/tslib",
build(zone.js): update zone.js version to 0.10.3 (#36214) PR Close #36214
2020-03-23 21:22:41 -04:00
"zone.js": "0.10.3"
build: add bazel integration test (#18733) It includes sass compilation, and building the bazel package distribution. PR Close #18733
2017-08-21 11:23:47 -04:00
},
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
"devDependencies": {
build(bazel): update to nodejs rules 0.30.1 & bazel 0.26.0 (#30627) nodejs rules 0.30.1 has new feature to symlink node_modules with yarn_install and bazel 0.26.0 includes new managed_directories feature which enables this PR Close #30627
2019-05-22 20:28:42 -04:00
"@angular/bazel": "file:../../dist/packages-dist/bazel",
"@angular/compiler": "file:../../dist/packages-dist/compiler",
"@angular/compiler-cli": "file:../../dist/packages-dist/compiler-cli",
build: depend on bazelisk rather than directly on Bazel (#36078) This has a couple benefits: - we now use a .bazelversion file rather than package.json to pin the version of bazel we want. This means even if you install bazel on your computer rather than via yarn, you'll still get a warning if your bazel version is wrong. - you no longer end up downloading three copies of bazel due to bugs in both npm and yarn where they download all tarballs before checking the metadata to see which are usable on the local platform. - bazelisk correctly handles the tools/bazel trick for wrapping functionality, which we want to use to instrument developer build latencies PR Close #36078
2020-02-04 19:14:21 -05:00
"@bazel/bazelisk": "file:../../node_modules/@bazel/bazelisk",
build: update to rules_nodejs 1.6.0 (#36580) Lots of bug fixes and stability fixes. Last 1.x release for rules_nodejs. PR Close #36580
2020-04-11 12:15:16 -04:00
"@bazel/karma": "1.6.0",
"@bazel/protractor": "1.6.0",
"@bazel/rollup": "1.6.0",
"@bazel/terser": "1.6.0",
"@bazel/typescript": "1.6.0",
build(bazel): update to nodejs rules 0.30.1 & bazel 0.26.0 (#30627) nodejs rules 0.30.1 has new feature to symlink node_modules with yarn_install and bazel 0.26.0 includes new managed_directories feature which enables this PR Close #30627
2019-05-22 20:28:42 -04:00
"@types/jasmine": "2.8.8",
build: update integration/bazel & @angular/bazel schematics to rules_nodejs 1.0.0 (#34736) For the purposes of the integration test the zone.js script & bundle script tags can just go into the source index.html itself. The purpose of the integration test is is to test @angular/bazel & ng_module & ng_package so there is no need to exercise html_insert_assets in integration/bazel. PR Close #34736
2019-11-27 17:12:10 -05:00
"http-server": "0.12.0",
"karma": "4.4.1",
"karma-chrome-launcher": "3.1.0",
"karma-firefox-launcher": "1.2.0",
"karma-jasmine": "2.0.1",
"karma-requirejs": "1.1.0",
"karma-sourcemap-loader": "0.3.7",
"protractor": "5.4.2",
"requirejs": "2.3.6",
"rollup": "1.27.5",
build: use exact versions for integration project dependencies (#33968) Since we cannot run `yarn install` with the `--frozen-lockfile` option (because we want to be able to install the locally built Angular packages), integration project lockfiles are susceptible to getting out-of-sync with the corresponding `package.json`. When this happens, yarn will install the latest available version that satisfies the version range specified in `package.json`. This commit adds another line of defense, by specifying exact versions for the dependencies in `package.json` files (i.e. `1.33.7` instead of `^1.33.0`). While transitive dependencies will be unpinned, this still ensures that the same version of direct dependencies will be installed in case of an out-of-sync lockfile, thus reducing the probability of random failures. PR Close #33968
2019-11-23 16:52:34 -05:00
"rollup-plugin-commonjs": "10.1.0",
"rollup-plugin-node-resolve": "5.2.0",
"rollup-plugin-sourcemaps": "0.4.2",
build: update integration/bazel & @angular/bazel schematics to rules_nodejs 1.0.0 (#34736) For the purposes of the integration test the zone.js script & bundle script tags can just go into the source index.html itself. The purpose of the integration test is is to test @angular/bazel & ng_module & ng_package so there is no need to exercise html_insert_assets in integration/bazel. PR Close #34736
2019-11-27 17:12:10 -05:00
"terser": "4.4.0",
build: update dependencies to use typescript 3.8 and angular 9.1 (#36329) Update the typescript version to 3.8 as well as the Angular version to 9.1, which is the one which added TS 3.8 support. PR Close #36329
2020-05-05 15:12:54 -04:00
"typescript": "3.8.3"
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
},
build: add bazel integration test (#18733) It includes sass compilation, and building the bazel package distribution. PR Close #18733
2017-08-21 11:23:47 -04:00
"scripts": {
build: depend on bazelisk rather than directly on Bazel (#36078) This has a couple benefits: - we now use a .bazelversion file rather than package.json to pin the version of bazel we want. This means even if you install bazel on your computer rather than via yarn, you'll still get a warning if your bazel version is wrong. - you no longer end up downloading three copies of bazel due to bugs in both npm and yarn where they download all tarballs before checking the metadata to see which are usable on the local platform. - bazelisk correctly handles the tools/bazel trick for wrapping functionality, which we want to use to instrument developer build latencies PR Close #36078
2020-02-04 19:14:21 -05:00
"test": "bazelisk build ... --noshow_progress && bazelisk test ...",
build: update integration/bazel to Ivy and new rollup_bundle (#33434) The legacy rollup_bundle will be removed for the rules_nodejs 1.0 release PR Close #33434
2019-10-25 14:52:37 -04:00
"postinstall": "ngcc"
build: add bazel integration test (#18733) It includes sass compilation, and building the bazel package distribution. PR Close #18733
2017-08-21 11:23:47 -04:00
}
build(bazel): update to nodejs rules 0.30.1 & bazel 0.26.0 (#30627) nodejs rules 0.30.1 has new feature to symlink node_modules with yarn_install and bazel 0.26.0 includes new managed_directories feature which enables this PR Close #30627
2019-05-22 20:28:42 -04:00
}