skills/angular__angular
1
0
Fork 0
mirror of https://github.com/angular/angular.git synced 2026-09-14 13:54:52 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
fde329da808647e7ff40a19242f2ffc879d522f0
angular__angular/integration/ngcc/package.json
T

37 lines
1.6 KiB
JSON
Raw Normal View History

test(ivy): add an integration test for ngcc (#25406) This commit adds an integration test for ngcc, which runs ngcc against most @angular packages. It does not yet make any assertions on the result. PR Close #25406
2018-08-09 14:23:56 +01:00
{
"name": "angular-integration",
"version": "0.0.0",
"license": "MIT",
"dependencies": {
test: update basic integration tests to work with new package output (#43431) Basic integration tests are those which do not require significant changes as others. The larger ones will have individual commits. For v13, the NPM package output will always be using partial compilation output. This makes the ngcc integration test fail because the actual Angular framework packages are no longer processable. We fix this, and keep the ngcc test coverage by relying on the v12.x framework packages in the integration test. The terser integration test needs to point to the new Flat ESM module file location. We now output FESM2020 instead of FESM2015. This also requires us to use the latest version of terser. The `side-effects` test currently is not maintained by us and relies on View Engine build output. In the partial compilation output the partial declarations are not marked with `@PURE` and are not removed therefore. We would need to update the side-effect test to use the linker Babel plugin instead. This is currently out-of-scope though so we disable the test for now. PR Close #43431
2021-09-20 22:12:21 +02:00
"@angular/animations": "file:../../node_modules/@angular/animations-12",
test(ngcc): update ngcc integration test dependencies (#34212) This commit updates `@angular/material` and `@angular/cdk` to the latest release candidate. Doing so exposed a bug in ngcc, which is fixed by the preceding commit. Also the layout of these libraries changed, so the checks in the integration test need a bit of tweaking. PR Close #34212
2019-12-03 12:39:16 +00:00
"@angular/cdk": "9.0.0-rc.4",
test: update basic integration tests to work with new package output (#43431) Basic integration tests are those which do not require significant changes as others. The larger ones will have individual commits. For v13, the NPM package output will always be using partial compilation output. This makes the ngcc integration test fail because the actual Angular framework packages are no longer processable. We fix this, and keep the ngcc test coverage by relying on the v12.x framework packages in the integration test. The terser integration test needs to point to the new Flat ESM module file location. We now output FESM2020 instead of FESM2015. This also requires us to use the latest version of terser. The `side-effects` test currently is not maintained by us and relies on View Engine build output. In the partial compilation output the partial declarations are not marked with `@PURE` and are not removed therefore. We would need to update the side-effect test to use the linker Babel plugin instead. This is currently out-of-scope though so we disable the test for now. PR Close #43431
2021-09-20 22:12:21 +02:00
"@angular/common": "file:../../node_modules/@angular/common-12",
test(ivy): add an integration test for ngcc (#25406) This commit adds an integration test for ngcc, which runs ngcc against most @angular packages. It does not yet make any assertions on the result. PR Close #25406
2018-08-09 14:23:56 +01:00
"@angular/compiler": "file:../../dist/packages-dist/compiler",
"@angular/compiler-cli": "file:../../dist/packages-dist/compiler-cli",
test: update basic integration tests to work with new package output (#43431) Basic integration tests are those which do not require significant changes as others. The larger ones will have individual commits. For v13, the NPM package output will always be using partial compilation output. This makes the ngcc integration test fail because the actual Angular framework packages are no longer processable. We fix this, and keep the ngcc test coverage by relying on the v12.x framework packages in the integration test. The terser integration test needs to point to the new Flat ESM module file location. We now output FESM2020 instead of FESM2015. This also requires us to use the latest version of terser. The `side-effects` test currently is not maintained by us and relies on View Engine build output. In the partial compilation output the partial declarations are not marked with `@PURE` and are not removed therefore. We would need to update the side-effect test to use the linker Babel plugin instead. This is currently out-of-scope though so we disable the test for now. PR Close #43431
2021-09-20 22:12:21 +02:00
"@angular/core": "file:../../node_modules/@angular/core-12",
"@angular/forms": "file:../../node_modules/@angular/forms-12",
test(ngcc): update ngcc integration test dependencies (#34212) This commit updates `@angular/material` and `@angular/cdk` to the latest release candidate. Doing so exposed a bug in ngcc, which is fixed by the preceding commit. Also the layout of these libraries changed, so the checks in the integration test need a bit of tweaking. PR Close #34212
2019-12-03 12:39:16 +00:00
"@angular/material": "9.0.0-rc.4",
test: update basic integration tests to work with new package output (#43431) Basic integration tests are those which do not require significant changes as others. The larger ones will have individual commits. For v13, the NPM package output will always be using partial compilation output. This makes the ngcc integration test fail because the actual Angular framework packages are no longer processable. We fix this, and keep the ngcc test coverage by relying on the v12.x framework packages in the integration test. The terser integration test needs to point to the new Flat ESM module file location. We now output FESM2020 instead of FESM2015. This also requires us to use the latest version of terser. The `side-effects` test currently is not maintained by us and relies on View Engine build output. In the partial compilation output the partial declarations are not marked with `@PURE` and are not removed therefore. We would need to update the side-effect test to use the linker Babel plugin instead. This is currently out-of-scope though so we disable the test for now. PR Close #43431
2021-09-20 22:12:21 +02:00
"@angular/platform-browser": "file:../../node_modules/@angular/platform-browser-12",
"@angular/platform-browser-dynamic": "file:../../node_modules/@angular/platform-browser-dynamic-12",
"@angular/platform-server": "file:../../node_modules/@angular/platform-server-12",
"@angular/router": "file:../../node_modules/@angular/router-12",
test: use @types/node compatible with TS 3.6 (#32946) PR Close #32946
2019-10-17 12:18:19 +01:00
"@types/node": "file:../../node_modules/@types/node",
test(ivy): add an integration test for ngcc (#25406) This commit adds an integration test for ngcc, which runs ngcc against most @angular packages. It does not yet make any assertions on the result. PR Close #25406
2018-08-09 14:23:56 +01:00
"rxjs": "file:../../node_modules/rxjs",
"typescript": "file:../../node_modules/typescript",
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 13:48:41 +09:00
"zone.js": "file:../../dist/zone.js-dist/archive/zone.js.tgz"
test(ivy): add an integration test for ngcc (#25406) This commit adds an integration test for ngcc, which runs ngcc against most @angular packages. It does not yet make any assertions on the result. PR Close #25406
2018-08-09 14:23:56 +01:00
},
"devDependencies": {
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 11:45:40 -08:00
"@types/jasmine": "file:../../node_modules/@types/jasmine",
test(ivy): add an integration test for ngcc (#25406) This commit adds an integration test for ngcc, which runs ngcc against most @angular packages. It does not yet make any assertions on the result. PR Close #25406
2018-08-09 14:23:56 +01:00
"concurrently": "3.4.0",
"lite-server": "2.2.2",
"protractor": "file:../../node_modules/protractor"
},
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 16:15:44 +02: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"
},
test(ivy): add an integration test for ngcc (#25406) This commit adds an integration test for ngcc, which runs ngcc against most @angular packages. It does not yet make any assertions on the result. PR Close #25406
2018-08-09 14:23:56 +01:00
"scripts": {
"test": "./test.sh"
}
}
Reference in New Issue Copy Permalink