honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/integration/hello_world__systemjs_umd/package.json

38 lines
1.6 KiB
JSON
Raw Normal View History

test: add systemjs+umd integration test (#14196) This test ensures the `__esModule` is set on UMD bundles, thus making them compatible with SystemJS@^0.22.3. Followup from https://github.com/frankwallis/plugin-typescript/issues/185. PR Close #14196
2017-01-30 18:28:56 -05:00
{
"name": "angular-integration",
"description": "Ensure SystemJS ^0.22 UMD compatibility via __esModule flag.",
"version": "0.0.0",
"license": "MIT",
"scripts": {
build: upgrade to TypeScript 2.6 (#21144) Fixes #20653 PR Close #21144
2017-12-22 12:36:47 -05:00
"test": "concurrently \"yarn serve\" \"yarn protractor\" --kill-others --success first",
test: add systemjs+umd integration test (#14196) This test ensures the `__esModule` is set on UMD bundles, thus making them compatible with SystemJS@^0.22.3. Followup from https://github.com/frankwallis/plugin-typescript/issues/185. PR Close #14196
2017-01-30 18:28:56 -05:00
"serve": "lite-server -c bs-config.e2e.json",
"preprotractor": "tsc -p e2e",
"protractor": "protractor protractor.config.js"
},
"dependencies": {
"@angular/common": "file:../../dist/packages-dist/common",
"@angular/core": "file:../../dist/packages-dist/core",
"@angular/compiler": "file:../../dist/packages-dist/compiler",
"@angular/platform-browser": "file:../../dist/packages-dist/platform-browser",
"@angular/platform-browser-dynamic": "file:../../dist/packages-dist/platform-browser-dynamic",
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",
build: upgrade to TypeScript 2.6 (#21144) Fixes #20653 PR Close #21144
2017-12-22 12:36:47 -05:00
"plugin-typescript": "8.0.0",
test: add systemjs+umd integration test (#14196) This test ensures the `__esModule` is set on UMD bundles, thus making them compatible with SystemJS@^0.22.3. Followup from https://github.com/frankwallis/plugin-typescript/issues/185. PR Close #14196
2017-01-30 18:28:56 -05:00
"rxjs": "file:../../node_modules/rxjs",
"systemjs": "0.20.2",
refactor: update angular to support TypeScript 2.4 Detailed updates: - rxjs@5.0.x - tsickle@0.24.x - typescript@2.4.x - @bazel/typescript@0.10.0 - protractor@5.1.x - selenium-webdriver@3.0.x BREAKING CHANGE: - the Angular compiler now requires TypeScript 2.4.x.
2017-09-08 21:40:32 -04:00
"typescript": "file:../../node_modules/typescript",
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"
test: add systemjs+umd integration test (#14196) This test ensures the `__esModule` is set on UMD bundles, thus making them compatible with SystemJS@^0.22.3. Followup from https://github.com/frankwallis/plugin-typescript/issues/185. PR Close #14196
2017-01-30 18:28:56 -05:00
},
"devDependencies": {
build: add npm_integration_test && angular_integration_test (#33927) * it's tricky to get out of the runfiles tree with `bazel test` as `BUILD_WORKSPACE_DIRECTORY` is not set but I employed a trick to read the `DO_NOT_BUILD_HERE` file that is one level up from `execroot` and that contains the workspace directory. This is experimental and if `bazel test //:test.debug` fails than `bazel run` is still guaranteed to work as `BUILD_WORKSPACE_DIRECTORY` will be set in that context * test //integration:bazel_test and //integration:bazel-schematics_test exclusively * run "exclusive" and "manual" bazel-in-bazel integration tests in their own CI job as they take 8m+ to execute ``` //integration:bazel-schematics_test PASSED in 317.2s //integration:bazel_test PASSED in 167.8s ``` * Skip all integration tests that are now handled by angular_integration_test except the tests that are tracked for payload size; these are: - cli-hello-world* - hello_world__closure * add & pin @babel deps as newer versions of babel break //packages/localize/src/tools/test:test @babel/core dep had to be pinned to 7.6.4 or else //packages/localize/src/tools/test:test failed. Also //packages/localize uses @babel/generator, @babel/template, @babel/traverse & @babel/types so these deps were added to package.json as they were not being hoisted anymore from @babel/core transitive. NB: integration/hello_world__systemjs_umd test must run with systemjs 0.20.0 NB: systemjs must be at 0.18.10 for legacy saucelabs job to pass NB: With Bazel 2.0, the glob for the files to test `"integration/bazel/**"` is empty if integation/bazel is in .bazelignore. This glob worked under these conditions with 1.1.0. I did not bother testing with 1.2.x as not having integration/bazel in .bazelignore is correct. PR Close #33927
2020-02-04 14:45:40 -05:00
"@types/jasmine": "file:../../node_modules/@types/jasmine",
"@types/jasminewd2": "file:../../node_modules/@types/jasminewd2",
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",
test: add systemjs+umd integration test (#14196) This test ensures the `__esModule` is set on UMD bundles, thus making them compatible with SystemJS@^0.22.3. Followup from https://github.com/frankwallis/plugin-typescript/issues/185. PR Close #14196
2017-01-30 18:28:56 -05:00
"lite-server": "2.2.2",
test: use puppeteer in integration tests and to download correct chromedriver (#35049) This means integration tests no longer need to depend on a $CI_CHROMEDRIVER_VERSION_ARG environment variable to specify which chromedriver version to download to match the locally installed chrome. This was bad DX and not having it specified was not reliable as webdriver-manager would not always download the chromedriver version to work with the locally installed chrome. webdriver-manager update --gecko=false --standalone=false $CI_CHROMEDRIVER_VERSION_ARG is now replaced with node webdriver-manager-update.js in the root package.json, which checks which version of chrome puppeteer has come bundled with & downloads informs webdriver-manager to download the corresponding chrome driver version. Integration tests now use "webdriver-manager": "file:../../node_modules/webdriver-manager" so they don't have to waste time calling webdriver-manager update in postinstall "// resolutions": "Ensure a single version of webdriver-manager which comes from root node_modules that has already run webdriver-manager update", "resolutions": { "**/webdriver-manager": "file:../../node_modules/webdriver-manager" } This should speed up each integration postinstall by a few seconds. Further, integration test package.json files link puppeteer via file:../../node_modules/puppeteer which is the ideal situation as the puppeteer post-install won't download chrome if it is already downloaded. In CI, since node_modules is cached it should not need to download Chrome either unless the node_modules cache is busted. NB: each version of puppeteer comes bundles with a specific version of chrome. Root package.json & yarn.lock currently pull down puppeteer 2.1.0 which comes with chrome 80. See https://github.com/puppeteer/puppeteer#q-which-chromium-version-does-puppeteer-use for more info. Only two references to CI_CHROMEDRIVER_VERSION_ARG left in integration tests at integration/bazel-schematics/test.sh which I'm not entirely sure how to get rid of it Use a lightweight puppeteer=>chrome version mapping instead of launching chrome and calling browser.version() Launching puppeteer headless chrome and calling browser.version() was a heavy-handed approach to determine the Chrome version. A small and easy to update mappings file is a better solution and it means that the `yarn install` step does not require chrome shared libs available on the system for its postinstall step PR Close #35049
2020-01-31 18:50:44 -05:00
"protractor": "file:../../node_modules/protractor",
"puppeteer": "file:../../node_modules/puppeteer"
},
"//resolutions-comment": "Ensure a single version of webdriver-manager which comes from root node_modules that has already run webdriver-manager update",
"resolutions": {
"**/webdriver-manager": "file:../../node_modules/webdriver-manager"
test: add systemjs+umd integration test (#14196) This test ensures the `__esModule` is set on UMD bundles, thus making them compatible with SystemJS@^0.22.3. Followup from https://github.com/frankwallis/plugin-typescript/issues/185. PR Close #14196
2017-01-30 18:28:56 -05:00
}
}