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

52 lines
2.1 KiB
JSON
Raw Normal View History

ci: Add back the CLI integration test with pinning (#21555) The CLI app is now checked in, rather than generated dynamically with `ng new`. This loses some assertion power, but gains hermeticity. It also checks in lock files for all integration tests, avoiding floating version numbers. We'll need another place to integration test between changes in the various repositories - but the angular/angular PR-blocking status is not the right place to do this. PR Close #21555
2018-01-16 10:09:59 -05:00
{
"name": "cli-hello-world",
"version": "0.0.0",
"license": "MIT",
"scripts": {
feat(ivy): expose a series of helpful application inspection tools (#25919) PR Close #25919
2018-09-24 17:51:54 -04:00
"build": "ng build --prod --progress=false",
ci: make `integration_test` job logs less verbose (#26869) The build progress logs accounted for ~80% of the total log size, which makes it harder to get to the interesting lines, such as error messages. Used suggestion from [here][1]. [1]: https://github.com/angular/angular-cli/issues/11412#issuecomment-412021539 PR Close #26869
2018-10-31 07:33:17 -04:00
"e2e": "ng e2e --webdriver-update=false",
ci: Add back the CLI integration test with pinning (#21555) The CLI app is now checked in, rather than generated dynamically with `ng new`. This loses some assertion power, but gains hermeticity. It also checks in lock files for all integration tests, avoiding floating version numbers. We'll need another place to integration test between changes in the various repositories - but the angular/angular PR-blocking status is not the right place to do this. PR Close #21555
2018-01-16 10:09:59 -05:00
"lint": "ng lint",
test: add i18n to cli-hello-world integration test (#23527) PR Close #23527
2018-04-24 14:30:23 -04:00
"ng": "ng",
ci: pin ChromeDriver to a version compatible with docker image's Chrome (#28494) By default, `webdriver-manager update` will download the latest ChromeDriver version, which might not be compatible with the Chrome version included in the [docker image used on CI], causing CI failures. Previously, we used to pin the ChromeDriver version on CI in [ngcontainer's Dockerfile][2]. This was accidentally broken in #26691, while moving from ngcontainer to default CircleCI docker images. This commit fixes the issue by pinning ChromeDriver to a known compatible version. [1]: https://github.com/angular/angular/blob/bfd48d156d5663cc49d1ec40c2d73ff76a2fe62f/.circleci/config.yml#L16 [2]: https://github.com/angular/angular/blob/bfd48d156d5663cc49d1ec40c2d73ff76a2fe62f/tools/ngcontainer/Dockerfile#L63 PR Close #28494
2019-02-01 16:40:33 -05:00
"postinstall": "webdriver-manager update --gecko=false --standalone=false $CI_CHROMEDRIVER_VERSION_ARG",
test: add i18n to cli-hello-world integration test (#23527) PR Close #23527
2018-04-24 14:30:23 -04:00
"start": "ng serve",
test: log cli version in `cli-hello-world[-ivy]` integration projects (#26947) This helps debug issues on CI. PR Close #26947
2019-01-17 14:38:19 -05:00
"pretest": "ng version",
ci: make `integration_test` job logs less verbose (#26869) The build progress logs accounted for ~80% of the total log size, which makes it harder to get to the interesting lines, such as error messages. Used suggestion from [here][1]. [1]: https://github.com/angular/angular-cli/issues/11412#issuecomment-412021539 PR Close #26869
2018-10-31 07:33:17 -04:00
"test": "ng test --progress=false --watch=false && yarn e2e --configuration=ci && yarn e2e --configuration=ci-production"
ci: Add back the CLI integration test with pinning (#21555) The CLI app is now checked in, rather than generated dynamically with `ng new`. This loses some assertion power, but gains hermeticity. It also checks in lock files for all integration tests, avoiding floating version numbers. We'll need another place to integration test between changes in the various repositories - but the angular/angular PR-blocking status is not the right place to do this. PR Close #21555
2018-01-16 10:09:59 -05:00
},
"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",
feat(core): upgrade rxjs to 6.0.0-alpha.4 (#22573) PR Close #22573
2018-02-27 17:06:06 -05:00
"core-js": "file:../../node_modules/core-js",
"rxjs": "file:../../node_modules/rxjs",
build: upgrade `cli-hello-world[-ivy]` integration projects to @angular/cli@7.2.1 (#27697) PR Close #27697
2019-01-09 13:53:18 -05:00
"tslib": "^1.9.3",
feat(core): upgrade rxjs to 6.0.0-alpha.4 (#22573) PR Close #22573
2018-02-27 17:06:06 -05:00
"zone.js": "file:../../node_modules/zone.js"
ci: Add back the CLI integration test with pinning (#21555) The CLI app is now checked in, rather than generated dynamically with `ng new`. This loses some assertion power, but gains hermeticity. It also checks in lock files for all integration tests, avoiding floating version numbers. We'll need another place to integration test between changes in the various repositories - but the angular/angular PR-blocking status is not the right place to do this. PR Close #21555
2018-01-16 10:09:59 -05:00
},
"devDependencies": {
feat(bazel): update the build to use the new architect api (#29720) With this change the builder has been updated to use the latest architect API and make it compatable with the latest CLI Fixes https://github.com/angular/angular-cli/issues/14082 PR Close #29720
2019-04-05 02:39:23 -04:00
"@angular-devkit/build-angular": "^0.800.0-beta.11",
build(bazel): Use @angular/cli from root package.json (#28139) A few integration tests now depend on @angular/cli. This commit changes the affected tests to use the dependency on @angular/cli defined at root package.json. PR Close #28139
2019-01-14 16:12:45 -05:00
"@angular/cli": "file:../../node_modules/@angular/cli",
ci: Add back the CLI integration test with pinning (#21555) The CLI app is now checked in, rather than generated dynamically with `ng new`. This loses some assertion power, but gains hermeticity. It also checks in lock files for all integration tests, avoiding floating version numbers. We'll need another place to integration test between changes in the various repositories - but the angular/angular PR-blocking status is not the right place to do this. PR Close #21555
2018-01-16 10:09:59 -05:00
"@angular/compiler-cli": "file:../../dist/packages-dist/compiler-cli",
"@angular/language-service": "file:../../dist/packages-dist/language-service",
"@types/jasmine": "~2.8.3",
build: upgrade `@types/jasminewd2` to 2.0.4 (#26139) This commit also removes the extra jasminewd2 typings, since the changes have been merged in the official typings with DefinitelyTyped/DefinitelyTyped#28957. PR Close #26139
2018-09-27 10:03:40 -04:00
"@types/jasminewd2": "~2.0.4",
ci: Add back the CLI integration test with pinning (#21555) The CLI app is now checked in, rather than generated dynamically with `ng new`. This loses some assertion power, but gains hermeticity. It also checks in lock files for all integration tests, avoiding floating version numbers. We'll need another place to integration test between changes in the various repositories - but the angular/angular PR-blocking status is not the right place to do this. PR Close #21555
2018-01-16 10:09:59 -05:00
"@types/node": "~6.0.60",
test: add i18n to cli-hello-world integration test (#23527) PR Close #23527
2018-04-24 14:30:23 -04:00
"codelyzer": "^4.3.0",
ci: Add back the CLI integration test with pinning (#21555) The CLI app is now checked in, rather than generated dynamically with `ng new`. This loses some assertion power, but gains hermeticity. It also checks in lock files for all integration tests, avoiding floating version numbers. We'll need another place to integration test between changes in the various repositories - but the angular/angular PR-blocking status is not the right place to do this. PR Close #21555
2018-01-16 10:09:59 -05:00
"jasmine-core": "~2.8.0",
"jasmine-spec-reporter": "~4.2.1",
"karma": "~2.0.0",
"karma-chrome-launcher": "~2.2.0",
"karma-coverage-istanbul-reporter": "^1.2.1",
"karma-jasmine": "~1.1.0",
"karma-jasmine-html-reporter": "^0.2.2",
test: add i18n to cli-hello-world integration test (#23527) PR Close #23527
2018-04-24 14:30:23 -04:00
"protractor": "file:../../node_modules/protractor",
ci: Add back the CLI integration test with pinning (#21555) The CLI app is now checked in, rather than generated dynamically with `ng new`. This loses some assertion power, but gains hermeticity. It also checks in lock files for all integration tests, avoiding floating version numbers. We'll need another place to integration test between changes in the various repositories - but the angular/angular PR-blocking status is not the right place to do this. PR Close #21555
2018-01-16 10:09:59 -05:00
"ts-node": "~4.1.0",
build: update tslint to version ~5.13.0 (#29070) PR Close #29070
2019-03-02 00:54:25 -05:00
"tslint": "~5.13.0",
test: update cli-hello-world to cli@6.0.0-rc.2 (#23234) PR Close #23234
2018-04-07 01:23:51 -04:00
"typescript": "file:../../node_modules/typescript"
ci: Add back the CLI integration test with pinning (#21555) The CLI app is now checked in, rather than generated dynamically with `ng new`. This loses some assertion power, but gains hermeticity. It also checks in lock files for all integration tests, avoiding floating version numbers. We'll need another place to integration test between changes in the various repositories - but the angular/angular PR-blocking status is not the right place to do this. PR Close #21555
2018-01-16 10:09:59 -05:00
}
build: upgrade `@types/jasminewd2` to 2.0.4 (#26139) This commit also removes the extra jasminewd2 typings, since the changes have been merged in the official typings with DefinitelyTyped/DefinitelyTyped#28957. PR Close #26139
2018-09-27 10:03:40 -04:00
}