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

47 lines
1.7 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(ngcc): build `zone.js` from source in `scripts/build-packages-dist.sh` (#33733) In #33046, internal uses of `zone.js` were switched to reference it directly from source (built with Bazel) instead of npm. As a result, the necessary scripts were updated to build `zone.js` as necessary. However, some `integration/**/debug-test.sh` scripts were missed (apparently because they are not used on CI, but only locally as helpers for debugging the integration projects). This commit updates the `scripts/build-packages-dist.sh` script to also build `zone.js`, so that other scripts (such as the various `debug-test.sh` scripts) can use it. PR Close #33733
2019-11-11 10:11:34 -05:00
"zone.js": "file:../../dist/zone.js-dist/zone.js"
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: 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
"@angular-devkit/build-angular": "0.900.0-rc.3",
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: 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
"@types/jasmine": "3.3.16",
"@types/jasminewd2": "2.0.6",
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",
"karma": "4.0.1",
"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"
}
}