Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
angular/integration/ngcc/package.json

27 lines
1.2 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 13:23:56 +00: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 20:12:21 +00: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 20:12:21 +00: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 13:23:56 +00: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 20:12:21 +00: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 20:12:21 +00: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 11:18:19 +00: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 13:23:56 +00: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 04:48:41 +00: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 13:23:56 +00:00
},
"scripts": {
test: switch integration tests from puppeteer/webdriver-manager to Bazel-managed chromium (#44238) Switches the integration tests form Puppeteer/webdriver-manager to the Bazel-managed Chromium/Chromedriver. This is now possible with the new integration test rule for which we can consult the `dev-infra/bazel/browsers` toolchain and setup environment variables. This has been configured already in a previous commit. This commit also includes some additional small cleanups necessary for the new integration test rule: * The `test.sh` scripts have been renamed as they would conflict with the `test.sh` scripts generated by the integration test rule. Previously this was not an issue because tests were declared at a higher-level. As mentioned though this has other downsides and it is trivial to rename the file. * Related to the point above, since tests are now declared witin the actual test folder (for perf e.g.), `package.json` files setting `"type": "module"` will accidentally cause the `nodejs_test`-generated files to be considered ESM. This is not correct and likely needs to be fixed upstream in `rules_nodejs` where explicit `.cjs` extensions should be used. This is only happening **once** in the `injectable-def` test so it is acceptable doing that for now. PR Close #44238
2021-11-20 16:23:07 +00:00
"test": "./run_test.sh"
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 13:23:56 +00:00
}
}
Reference in a new issue Copy permalink