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-ivy-compat/package.json

55 lines
2.4 KiB
JSON
Raw Normal View History

test(ivy): ngcc - test compiling a CLI generated project (#26403) This integration test was created from a vanilla CLI generated project with the following modifications: * remove `PercentPipe` usage from `app.component.html` - these are not yet supported by ivy * changed `ng test` in `package.json` to only to `ng build` - right now we can only confirm that the app will build * hard-code `ngDevMode` in `index.html` - the CLI does not yet set this correctly PR Close #26403
2018-10-05 11:45:18 -04:00
{
build: rename cli-hello-world-ivy test to cli-hello-world-ivy-compat (#28372) There are two ways to bootstrap an Ivy app: with `platformBrowserDynamic().bootstrapModule` and `renderComponent`. To distinguish between these two approaches we call the `platformBrowserDynamic().bootstrapModule` way `ivy-compat` and the `renderComponent` way just `ivy`. PR Close #28372
2019-01-28 09:54:34 -05:00
"name": "cli-hello-world-ivy-compat",
test(ivy): ngcc - test compiling a CLI generated project (#26403) This integration test was created from a vanilla CLI generated project with the following modifications: * remove `PercentPipe` usage from `app.component.html` - these are not yet supported by ivy * changed `ng test` in `package.json` to only to `ng build` - right now we can only confirm that the app will build * hard-code `ngDevMode` in `index.html` - the CLI does not yet set this correctly PR Close #26403
2018-10-05 11:45:18 -04:00
"version": "0.0.0",
"license": "MIT",
"scripts": {
test(ivy): synchronize cli-hello-world-ivy with cli-hello-world integration suite (#27438) The ci-production e2e test is diabled because Angular fails to be found PR Close #27438
2018-12-03 16:36:47 -05:00
"build": "ng build --prod --progress=false",
"e2e": "ng e2e --webdriver-update=false",
test(ivy): ngcc - test compiling a CLI generated project (#26403) This integration test was created from a vanilla CLI generated project with the following modifications: * remove `PercentPipe` usage from `app.component.html` - these are not yet supported by ivy * changed `ng test` in `package.json` to only to `ng build` - right now we can only confirm that the app will build * hard-code `ngDevMode` in `index.html` - the CLI does not yet set this correctly PR Close #26403
2018-10-05 11:45:18 -04:00
"lint": "ng lint",
"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 && yarn ivy-ngcc",
test(ivy): ngcc - test compiling a CLI generated project (#26403) This integration test was created from a vanilla CLI generated project with the following modifications: * remove `PercentPipe` usage from `app.component.html` - these are not yet supported by ivy * changed `ng test` in `package.json` to only to `ng build` - right now we can only confirm that the app will build * hard-code `ngDevMode` in `index.html` - the CLI does not yet set this correctly PR Close #26403
2018-10-05 11:45:18 -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",
test(ivy): enable running cli-hello-world-ivy integration test suite (#27438) PR Close #27438
2018-12-03 16:37:59 -05:00
"//test1": "TODO FW-813: Re-enable `ci-production`. Currently, it fails after a timeout as Protractor reports Angular cannot be found on the page",
"//test2": "ng test --progress=false --watch=false && yarn e2e --configuration=ci && yarn e2e --configuration=ci-production",
test(ivy): synchronize cli-hello-world-ivy with cli-hello-world integration suite (#27438) The ci-production e2e test is diabled because Angular fails to be found PR Close #27438
2018-12-03 16:36:47 -05:00
"test": "ng test --progress=false --watch=false && yarn e2e --configuration=ci"
test(ivy): ngcc - test compiling a CLI generated project (#26403) This integration test was created from a vanilla CLI generated project with the following modifications: * remove `PercentPipe` usage from `app.component.html` - these are not yet supported by ivy * changed `ng test` in `package.json` to only to `ng build` - right now we can only confirm that the app will build * hard-code `ngDevMode` in `index.html` - the CLI does not yet set this correctly PR Close #26403
2018-10-05 11:45:18 -04: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/http": "file:../../dist/packages-dist/http",
"@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",
"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",
test(ivy): ngcc - test compiling a CLI generated project (#26403) This integration test was created from a vanilla CLI generated project with the following modifications: * remove `PercentPipe` usage from `app.component.html` - these are not yet supported by ivy * changed `ng test` in `package.json` to only to `ng build` - right now we can only confirm that the app will build * hard-code `ngDevMode` in `index.html` - the CLI does not yet set this correctly PR Close #26403
2018-10-05 11:45:18 -04:00
"zone.js": "file:../../node_modules/zone.js"
},
"devDependencies": {
build: update version of Angular CLI and Build Optimizer used for tests (#28372) PR Close #28372
2019-01-25 11:33:22 -05:00
"@angular-devkit/build-angular": "0.13.0-rc.0",
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",
test(ivy): ngcc - test compiling a CLI generated project (#26403) This integration test was created from a vanilla CLI generated project with the following modifications: * remove `PercentPipe` usage from `app.component.html` - these are not yet supported by ivy * changed `ng test` in `package.json` to only to `ng build` - right now we can only confirm that the app will build * hard-code `ngDevMode` in `index.html` - the CLI does not yet set this correctly PR Close #26403
2018-10-05 11:45:18 -04:00
"@angular/compiler-cli": "file:../../dist/packages-dist/compiler-cli",
"@angular/language-service": "file:../../dist/packages-dist/language-service",
test: update cli-hello-world-ivy to cli@7.2.0-rc.0 (#27797) Updates the app itself to reflect the result of using the `experimentalIvy` flag on the CLI. The result is similar to: npx @angular/cli@next new cli-hello-world-ivy --experimental-ivy --defaults But replaces the current (cli `7.2.0-rc.0`) `renderComponent` bootstrap with the usual `platformBrowserDynamic` one. It also keeps what the app did (display a pipe, tests it). PR Close #27797
2018-12-14 08:46:01 -05:00
"@types/jasmine": "~2.8.8",
"@types/jasminewd2": "~2.0.3",
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
"@types/node": "~8.9.4",
test: update cli-hello-world-ivy to cli@7.2.0-rc.0 (#27797) Updates the app itself to reflect the result of using the `experimentalIvy` flag on the CLI. The result is similar to: npx @angular/cli@next new cli-hello-world-ivy --experimental-ivy --defaults But replaces the current (cli `7.2.0-rc.0`) `renderComponent` bootstrap with the usual `platformBrowserDynamic` one. It also keeps what the app did (display a pipe, tests it). PR Close #27797
2018-12-14 08:46:01 -05:00
"codelyzer": "~4.5.0",
"jasmine-core": "~2.99.1",
test(ivy): ngcc - test compiling a CLI generated project (#26403) This integration test was created from a vanilla CLI generated project with the following modifications: * remove `PercentPipe` usage from `app.component.html` - these are not yet supported by ivy * changed `ng test` in `package.json` to only to `ng build` - right now we can only confirm that the app will build * hard-code `ngDevMode` in `index.html` - the CLI does not yet set this correctly PR Close #26403
2018-10-05 11:45:18 -04:00
"jasmine-spec-reporter": "~4.2.1",
test: update cli-hello-world-ivy to cli@7.2.0-rc.0 (#27797) Updates the app itself to reflect the result of using the `experimentalIvy` flag on the CLI. The result is similar to: npx @angular/cli@next new cli-hello-world-ivy --experimental-ivy --defaults But replaces the current (cli `7.2.0-rc.0`) `renderComponent` bootstrap with the usual `platformBrowserDynamic` one. It also keeps what the app did (display a pipe, tests it). PR Close #27797
2018-12-14 08:46:01 -05:00
"karma": "~3.1.1",
test(ivy): ngcc - test compiling a CLI generated project (#26403) This integration test was created from a vanilla CLI generated project with the following modifications: * remove `PercentPipe` usage from `app.component.html` - these are not yet supported by ivy * changed `ng test` in `package.json` to only to `ng build` - right now we can only confirm that the app will build * hard-code `ngDevMode` in `index.html` - the CLI does not yet set this correctly PR Close #26403
2018-10-05 11:45:18 -04:00
"karma-chrome-launcher": "~2.2.0",
test: update cli-hello-world-ivy to cli@7.2.0-rc.0 (#27797) Updates the app itself to reflect the result of using the `experimentalIvy` flag on the CLI. The result is similar to: npx @angular/cli@next new cli-hello-world-ivy --experimental-ivy --defaults But replaces the current (cli `7.2.0-rc.0`) `renderComponent` bootstrap with the usual `platformBrowserDynamic` one. It also keeps what the app did (display a pipe, tests it). PR Close #27797
2018-12-14 08:46:01 -05:00
"karma-coverage-istanbul-reporter": "~2.0.1",
"karma-jasmine": "~1.1.2",
test(ivy): ngcc - test compiling a CLI generated project (#26403) This integration test was created from a vanilla CLI generated project with the following modifications: * remove `PercentPipe` usage from `app.component.html` - these are not yet supported by ivy * changed `ng test` in `package.json` to only to `ng build` - right now we can only confirm that the app will build * hard-code `ngDevMode` in `index.html` - the CLI does not yet set this correctly PR Close #26403
2018-10-05 11:45:18 -04:00
"karma-jasmine-html-reporter": "^0.2.2",
"protractor": "file:../../node_modules/protractor",
test: update cli-hello-world-ivy to cli@7.2.0-rc.0 (#27797) Updates the app itself to reflect the result of using the `experimentalIvy` flag on the CLI. The result is similar to: npx @angular/cli@next new cli-hello-world-ivy --experimental-ivy --defaults But replaces the current (cli `7.2.0-rc.0`) `renderComponent` bootstrap with the usual `platformBrowserDynamic` one. It also keeps what the app did (display a pipe, tests it). PR Close #27797
2018-12-14 08:46:01 -05:00
"ts-node": "~7.0.0",
"tslint": "~5.11.0",
test(ivy): ngcc - test compiling a CLI generated project (#26403) This integration test was created from a vanilla CLI generated project with the following modifications: * remove `PercentPipe` usage from `app.component.html` - these are not yet supported by ivy * changed `ng test` in `package.json` to only to `ng build` - right now we can only confirm that the app will build * hard-code `ngDevMode` in `index.html` - the CLI does not yet set this correctly PR Close #26403
2018-10-05 11:45:18 -04:00
"typescript": "file:../../node_modules/typescript"
}
}