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",
"zone.js": "file:../../node_modules/zone.js"
},
"devDependencies": {
test: update angular cli version for ng_update_migrations integration test (#33223) Updates the Angular CLI version in the `ng_update_migrations` integration test. Since refactorings are made to the `ng update` command implementation, we want to make sure that everything works as expected for the migrations in version 9. PR Close #33223
2019-10-17 06:22:17 -04:00
"@angular-devkit/build-angular": "^0.900.0-next.11",
"@angular/cli": "^9.0.0-next.9",
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",
"@types/jasmine": "~3.3.8",
"@types/jasminewd2": "~2.0.3",
"@types/node": "~8.9.4",
"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.0",
"protractor": "file:../../node_modules/protractor",
"typescript": "file:../../node_modules/typescript"
}
}