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

32 lines
1.3 KiB
JSON
Raw Normal View History

test(integration): add an env for testing closure builds (#14130) * feat: add an env for testing closure builds * build(npm): add dev dependency on yarn (and remove dev props for readability) * build: refactor integration test runner
2017-01-27 12:17:50 -05:00
{
"name": "angular-integration",
"version": "0.0.0",
"license": "MIT",
"dependencies": {
fix(platform-server): setup NoopAnimationsModule in ServerModule by default (#15131) This is so that server side rendering does not throw an exception when it encounters animations on the server side and does not need the user to explicitly setup NoopAnimationsModule in their app server module. Fixes #15098, #14784. PR Close #15131
2017-03-13 20:31:03 -04:00
"@angular/animations": "file:../../dist/packages-dist/animations",
perf: distrubute smaller bundled code and include es2015 bundle TypeScript compiler will now build to ES2015 code and modules. Babili is used to minify ES2015 code, providing an initial optimization that we couldn't previously get just from Uglify. Uses Babel to convert ES2015 to UMD/ES5 code, and Uglify to minimize the output.
2017-01-27 20:39:48 -05:00
"@angular/common": "file:../../dist/packages-dist/common",
"@angular/compiler": "file:../../dist/packages-dist/compiler",
"@angular/compiler-cli": "file:../../dist/packages-dist/compiler-cli",
"@angular/core": "file:../../dist/packages-dist/core",
"@angular/platform-browser": "file:../../dist/packages-dist/platform-browser",
"@angular/platform-server": "file:../../dist/packages-dist/platform-server",
refactor(tsc-wrapped): move tsc-wrapped to the packages directory (#18160)
2017-07-16 13:47:46 -04:00
"@angular/tsc-wrapped": "file:../../dist/packages-dist/tsc-wrapped",
test: cleanup rxjs custom build The latest rxjs release works with closure compiler out of the box. We no longer need to compile our own. Also put closure options into a file rather than using a shell script.
2017-05-03 13:45:45 -04:00
"google-closure-compiler": "20170409.0.0",
"rxjs": "5.3.1",
refactor(compiler-cli): use the transformer based compiler by default The source map does not currently work with the transformer pipeline. It will be re-enabled after TypeScript 2.4 is made the min version. To revert to the former compiler, use the `disableTransformerPipeline` in tsconfig.json: ``` { "angularCompilerOptions": { "disableTransformerPipeline": true } } ```
2017-08-02 14:20:07 -04:00
"typescript": "~2.3.1",
test: cleanup rxjs custom build The latest rxjs release works with closure compiler out of the box. We no longer need to compile our own. Also put closure options into a file rather than using a shell script.
2017-05-03 13:45:45 -04:00
"zone.js": "0.8.6"
test(integration): add an env for testing closure builds (#14130) * feat: add an env for testing closure builds * build(npm): add dev dependency on yarn (and remove dev props for readability) * build: refactor integration test runner
2017-01-27 12:17:50 -05:00
},
test: protractor test for closure bundle (#14240) PR Close #14240
2017-02-01 23:47:04 -05:00
"devDependencies": {
build: pin versions in integration/*/package.json (#14378) Floating versions can break our CI. This happened with concurrently release last evening. Ideally we should just check in the yarn.lock file but are blocked on https://github.com/yarnpkg/yarn/issues/2256 PR Close #14378
2017-02-09 12:52:35 -05:00
"@types/jasmine": "2.5.41",
build: update `concurrently` to latest version The regression in `concurrently` v3.2.0 (which made us roll back to v3.1.0 in #14378) has been fixed in v3.3.0 (see kimmobrunfeldt/concurrently#89).
2017-02-15 05:12:14 -05:00
"concurrently": "3.4.0",
build: pin versions in integration/*/package.json (#14378) Floating versions can break our CI. This happened with concurrently release last evening. Ideally we should just check in the yarn.lock file but are blocked on https://github.com/yarnpkg/yarn/issues/2256 PR Close #14378
2017-02-09 12:52:35 -05:00
"lite-server": "2.2.2",
test: protractor test for closure bundle (#14240) PR Close #14240
2017-02-01 23:47:04 -05:00
"protractor": "file:../../node_modules/protractor"
},
test(integration): add an env for testing closure builds (#14130) * feat: add an env for testing closure builds * build(npm): add dev dependency on yarn (and remove dev props for readability) * build: refactor integration test runner
2017-01-27 12:17:50 -05:00
"scripts": {
test: cleanup rxjs custom build The latest rxjs release works with closure compiler out of the box. We no longer need to compile our own. Also put closure options into a file rather than using a shell script.
2017-05-03 13:45:45 -04:00
"closure": "java -jar node_modules/google-closure-compiler/compiler.jar --flagfile closure.conf",
"test": "ngc && yarn run closure && concurrently \"yarn run serve\" \"yarn run protractor\" --kill-others --success first",
test: protractor test for closure bundle (#14240) PR Close #14240
2017-02-01 23:47:04 -05:00
"serve": "lite-server -c e2e/browser.config.json",
"preprotractor": "tsc -p e2e",
"protractor": "protractor e2e/protractor.config.js"
test(integration): add an env for testing closure builds (#14130) * feat: add an env for testing closure builds * build(npm): add dev dependency on yarn (and remove dev props for readability) * build: refactor integration test runner
2017-01-27 12:17:50 -05:00
}
test: cleanup rxjs custom build The latest rxjs release works with closure compiler out of the box. We no longer need to compile our own. Also put closure options into a file rather than using a shell script.
2017-05-03 13:45:45 -04:00
}