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

51 lines
2.1 KiB
JSON
Raw Normal View History

build: create integration test for ng-update migrations (#32349) Creates anew integratin test for `ng-update` migrations. The integration test uses an Angular CLI project that will be updated using the latest package output symlinked from then `./dist/packages-dist`. This allows us to ensure that migrations work in real CLI projects. Another big benefit is that the Angular version is updated to the latest. This is something we couldn't replicate in unit tests but is extremely important. It's important because compilation could break with newer Angular versions (note that migrations are always executed after the new angular version has been installed). PR Close #32349
2019-08-27 11:37:10 -04:00
{
"name": "ng-update-migrations",
"version": "0.0.0",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"test": "node ./test.js",
"lint": "ng lint",
"e2e": "ng e2e"
},
"private": true,
"dependencies": {
"@angular/animations": "file:../../dist/packages-dist/animations",
"@angular/common": "file:../../dist/packages-dist/common",
"@angular/compiler": "file:../../dist/packages-dist/compiler",
"@angular/core": "file:../../dist/packages-dist/core",
"@angular/forms": "file:../../dist/packages-dist/forms",
"@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",
"rxjs": "file:../../node_modules/rxjs",
"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: create integration test for ng-update migrations (#32349) Creates anew integratin test for `ng-update` migrations. The integration test uses an Angular CLI project that will be updated using the latest package output symlinked from then `./dist/packages-dist`. This allows us to ensure that migrations work in real CLI projects. Another big benefit is that the Angular version is updated to the latest. This is something we couldn't replicate in unit tests but is extremely important. It's important because compilation could break with newer Angular versions (note that migrations are always executed after the new angular version has been installed). PR Close #32349
2019-08-27 11:37:10 -04:00
},
"devDependencies": {
build: consolidate @angular-devkit/build-angular to the root package.json (#34002) This allows us to update the version of the package in a single place for all tests. Notable exemption of this is aio which currently doesn't depend on anything installed in the root. PR Close #34002
2019-11-22 19:31:40 -05:00
"@angular-devkit/build-angular": "file:../../node_modules/@angular-devkit/build-angular",
test: update Angular CLI deps for integration tests (#32957) PR Close #32957
2019-10-02 07:28:23 -04:00
"@angular/cli": "file:../../node_modules/@angular/cli",
build: create integration test for ng-update migrations (#32349) Creates anew integratin test for `ng-update` migrations. The integration test uses an Angular CLI project that will be updated using the latest package output symlinked from then `./dist/packages-dist`. This allows us to ensure that migrations work in real CLI projects. Another big benefit is that the Angular version is updated to the latest. This is something we couldn't replicate in unit tests but is extremely important. It's important because compilation could break with newer Angular versions (note that migrations are always executed after the new angular version has been installed). PR Close #32349
2019-08-27 11:37:10 -04:00
"@angular/compiler-cli": "file:../../dist/packages-dist/compiler-cli",
"@angular/language-service": "file:../../dist/packages-dist/language-service",
build: add npm_integration_test && angular_integration_test (#33927) * it's tricky to get out of the runfiles tree with `bazel test` as `BUILD_WORKSPACE_DIRECTORY` is not set but I employed a trick to read the `DO_NOT_BUILD_HERE` file that is one level up from `execroot` and that contains the workspace directory. This is experimental and if `bazel test //:test.debug` fails than `bazel run` is still guaranteed to work as `BUILD_WORKSPACE_DIRECTORY` will be set in that context * test //integration:bazel_test and //integration:bazel-schematics_test exclusively * run "exclusive" and "manual" bazel-in-bazel integration tests in their own CI job as they take 8m+ to execute ``` //integration:bazel-schematics_test PASSED in 317.2s //integration:bazel_test PASSED in 167.8s ``` * Skip all integration tests that are now handled by angular_integration_test except the tests that are tracked for payload size; these are: - cli-hello-world* - hello_world__closure * add & pin @babel deps as newer versions of babel break //packages/localize/src/tools/test:test @babel/core dep had to be pinned to 7.6.4 or else //packages/localize/src/tools/test:test failed. Also //packages/localize uses @babel/generator, @babel/template, @babel/traverse & @babel/types so these deps were added to package.json as they were not being hoisted anymore from @babel/core transitive. NB: integration/hello_world__systemjs_umd test must run with systemjs 0.20.0 NB: systemjs must be at 0.18.10 for legacy saucelabs job to pass NB: With Bazel 2.0, the glob for the files to test `"integration/bazel/**"` is empty if integation/bazel is in .bazelignore. This glob worked under these conditions with 1.1.0. I did not bother testing with 1.2.x as not having integration/bazel in .bazelignore is correct. PR Close #33927
2020-02-04 14:45:40 -05:00
"@types/jasmine": "file:../../node_modules/@types/jasmine",
"@types/jasminewd2": "file:../../node_modules/@types/jasminewd2",
test: use @types/node compatible with TS 3.6 (#32946) PR Close #32946
2019-10-17 07:18:19 -04:00
"@types/node": "file:../../node_modules/@types/node",
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
"chalk": "2.4.2",
"diff": "4.0.1",
"glob": "7.1.4",
"jasmine-core": "3.4.0",
"jasmine-spec-reporter": "4.2.1",
build: upgrade karma to version 4.4.0 (#39180) Upgrade the karma dependency to version 4.4.0 in the root package.json and in integration tests. Compared to version 4.3.0, which most of the packages were previously depending on, it has the following changes: Bug Fixes - runner: remove explicit error on all tests failed Features - client: Add trusted types support - Preprocessor can return Promise - config: add failOnSkippedTests option. - config: clientDisplayNone sets client elements display none. - deps: Remove core-js dependency. The motivation for upgrading the package is the Trusted Types support that it adds, which is necessary to enable Trusted Types in Angular's unit tests. PR Close #39180
2020-10-08 09:08:43 -04:00
"karma": "4.4.0",
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
"karma-chrome-launcher": "2.2.0",
"karma-jasmine": "2.0.1",
"karma-jasmine-html-reporter": "1.4.2",
build: create integration test for ng-update migrations (#32349) Creates anew integratin test for `ng-update` migrations. The integration test uses an Angular CLI project that will be updated using the latest package output symlinked from then `./dist/packages-dist`. This allows us to ensure that migrations work in real CLI projects. Another big benefit is that the Angular version is updated to the latest. This is something we couldn't replicate in unit tests but is extremely important. It's important because compilation could break with newer Angular versions (note that migrations are always executed after the new angular version has been installed). PR Close #32349
2019-08-27 11:37:10 -04:00
"protractor": "file:../../node_modules/protractor",
"typescript": "file:../../node_modules/typescript"
build: ensure integration projects use root `webdriver-manager` (#40756) Ensure that all integration projects use `webdriver-manager` from the root `node_modules/`. See acfd0edd38d955a8559aeec3d97c0f9a23525079 for more details. PR Close #40756
2021-02-17 09:15:44 -05:00
},
"//resolutions-comment": "Ensure a single version of webdriver-manager which comes from root node_modules that has already run webdriver-manager update",
"resolutions": {
"**/webdriver-manager": "file:../../node_modules/webdriver-manager"
build: create integration test for ng-update migrations (#32349) Creates anew integratin test for `ng-update` migrations. The integration test uses an Angular CLI project that will be updated using the latest package output symlinked from then `./dist/packages-dist`. This allows us to ensure that migrations work in real CLI projects. Another big benefit is that the Angular version is updated to the latest. This is something we couldn't replicate in unit tests but is extremely important. It's important because compilation could break with newer Angular versions (note that migrations are always executed after the new angular version has been installed). PR Close #32349
2019-08-27 11:37:10 -04:00
}
}