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

55 lines
2.1 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",
test(zone.js): test zone.js package with tgz (#38649) Zone.js 0.11.0 release an empty bundle, and now the npm_package tests all target bazel rule `npm_package`, but not `npm_package.pack`, and these two rules may generate different results, for example, Zone.js 0.11.0's issue is `package.json` define files array which make the bundle only include the files in the files array. So this PR install the zone.js package from the archive generated from `npm_package.pack` rule. PR Close #38649
2020-08-31 00:48:41 -04:00
"zone.js": "file:../../dist/zone.js-dist/archive/zone.js.tgz"
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",
fix(bazel): update integration test to use rules_nodejs@3.1.0 (#40710) Update the integraiton tests for bazel to the latest rules_nodejs version. PR Close #40710
2021-02-04 17:08:26 -05:00
"@bazel/protractor": "3.1.0",
"@bazel/rollup": "3.1.0",
"@bazel/concatjs": "3.1.0",
"@bazel/terser": "3.1.0",
"@bazel/typescript": "3.1.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",
fix(bazel): update integration test to use rules_nodejs@3.1.0 (#40710) Update the integraiton tests for bazel to the latest rules_nodejs version. PR Close #40710
2021-02-04 17:08:26 -05:00
"@types/node": "^12.11.1",
"jasmine": "^3.5.0",
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: upgrade angular build, integration/bazel and @angular/bazel package to rule_nodejs 2.2.0 (#39182) Updates to rules_nodejs 2.2.0. This is the first major release in 7 months and includes a number of features as well as breaking changes. Release notes: https://github.com/bazelbuild/rules_nodejs/releases/tag/2.0.0 Features of note for angular/angular: * stdout/stderr/exit code capture; this could be potentially be useful * TypeScript (ts_project); a simpler tsc rule that ts_library that can be used in the repo where ts_library is too heavy weight Breaking changes of note for angular/angular: * loading custom rules from npm packages: `ts_library` is no longer loaded from `@npm_bazel_typescript//:index.bzl` (which no longer exists) but is now loaded from `@npm//@bazel/typescript:index.bzl` * with the loading changes above, `load("@npm//:install_bazel_dependencies.bzl", "install_bazel_dependencies")` is no longer needed in the WORKSPACE which also means that yarn_install does not need to run unless building/testing a target that depends on @npm. In angular/angular this is a minor improvement as almost everything depends on @npm. * @angular/bazel package is also updated in this PR to support the new load location; Angular + Bazel users that require it for ng_package (ng_module is no longer needed in OSS with Angular 10) will need to load from `@npm//@angular/bazel:index.bzl`. I investigated if it was possible to maintain backward compatability for the old load location `@npm_angular_bazel` but it is not since the package itself needs to be updated to load from `@npm//@bazel/typescript:index.bzl` instead of `@npm_bazel_typescript//:index.bzl` as it depends on ts_library internals for ng_module. * runfiles.resolve will now throw instead of returning undefined to match behavior of node require Other changes in angular/angular: * integration/bazel has been updated to use both ng_module and ts_libary with use_angular_plugin=true. The latter is the recommended way for rules_nodejs users to compile Angular 10 with Ivy. Bazel + Angular ViewEngine is supported with @angular/bazel <= 9.0.5 and Angular <= 8. There is still Angular ViewEngine example on rules_nodejs https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/angular_view_engine on these older versions but users that want to update to Angular 10 and are on Bazel must switch to Ivy and at that point ts_library with use_angular_plugin=true is more performant that ng_module. Angular example in rules_nodejs is configured this way as well: https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/angular. As an aside, we also have an example of building Angular 10 with architect() rule directly instead of using ts_library with angular plugin: https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/angular_bazel_architect. NB: ng_module is still required for angular/angular repository as it still builds ViewEngine & @angular/bazel also provides the ng_package rule. ng_module can be removed in the future if ViewEngine is no longer needed in angular repo. * JSModuleInfo provider added to ng_module. this is for forward compat for future rules_nodejs versions. PR Close #39182
2020-06-25 04:32:41 -04:00
"typescript": "file:../../node_modules/typescript"
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
}