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

22 lines
856 B
JSON
Raw Normal View History

test(language-service): test `@angular/language-service` can be loaded by tsserver.js (#14721)
2017-03-01 16:22:46 -05:00
{
"name": "language_service_plugin",
"version": "0.0.0",
"license": "MIT",
style: typos fixed - https://github.com/vlajos/misspell-fixer (#22975) PR Close #22975
2018-03-10 12:14:58 -05:00
"description": "Angular Language Service plugin integration test",
test(language-service): test `@angular/language-service` can be loaded by tsserver.js (#14721)
2017-03-01 16:22:46 -05:00
"dependencies": {
"@angular/core": "file:../../dist/packages-dist/core",
"@angular/language-service": "file:../../dist/packages-dist/language-service",
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",
test(language-service): Improve integration test (#28168) The current integration test for language service involves piping the results of one process to another using Unix pipes. This makes the test hard to debug, and hard to configure. This commit refactors the integration test to use regular Jasmine scaffolding. More importantly, it tests the way the language service will actually be installed by end users. Users would not have to add `@angular/language-service` to the plugins section in tsconfig.json Instead, all they need to do is install the *extension* from the VS Code Marketplace and Angular Language Service will be loaded as a global plugin. PR Close #28168
2018-12-18 02:44:26 -05:00
"@types/node": "file:../../node_modules/@types/node",
"jasmine": "file:../../node_modules/jasmine",
"typescript": "file:../../node_modules/typescript"
test(language-service): test `@angular/language-service` can be loaded by tsserver.js (#14721)
2017-03-01 16:22:46 -05:00
},
"scripts": {
test(language-service): Improve integration test (#28168) The current integration test for language service involves piping the results of one process to another using Unix pipes. This makes the test hard to debug, and hard to configure. This commit refactors the integration test to use regular Jasmine scaffolding. More importantly, it tests the way the language service will actually be installed by end users. Users would not have to add `@angular/language-service` to the plugins section in tsconfig.json Instead, all they need to do is install the *extension* from the VS Code Marketplace and Angular Language Service will be loaded as a global plugin. PR Close #28168
2018-12-18 02:44:26 -05:00
"build": "tsc -p tsconfig.json",
build: move build scripts to dedicated directory (#35780) This commit moves the build-related scripts (`build-ivy-npm-packages.js`, `build-packages-dist.js` and `package-builder.js`) to a dedicated directory to keep the `scripts/` directory cleaner. It also moves the logic for building the `zone.js` package to a separate script, `zone-js-builder.js`, to make it re-usable. A subsequent commit will use it to build the `zone.js` package when building the Ivy Angular packages as well. PR Close #35780
2020-02-29 15:25:49 -05:00
"build-dist": "node ../../scripts/build/build-packages-dist.js && yarn install --check-files",
test(language-service): Improve integration test (#28168) The current integration test for language service involves piping the results of one process to another using Unix pipes. This makes the test hard to debug, and hard to configure. This commit refactors the integration test to use regular Jasmine scaffolding. More importantly, it tests the way the language service will actually be installed by end users. Users would not have to add `@angular/language-service` to the plugins section in tsconfig.json Instead, all they need to do is install the *extension* from the VS Code Marketplace and Angular Language Service will be loaded as a global plugin. PR Close #28168
2018-12-18 02:44:26 -05:00
"cleanup": "rm -rf ti-*.log tsserver.log",
test(language-service): Add tests for quickinfo and definition (#29990) `quickinfo` is used for hover tooltip. `definition` is used for "Go to definition". PR Close #29990
2019-04-19 11:53:19 -04:00
"golden": "yarn build && node generate.js",
test(language-service): Improve integration test (#28168) The current integration test for language service involves piping the results of one process to another using Unix pipes. This makes the test hard to debug, and hard to configure. This commit refactors the integration test to use regular Jasmine scaffolding. More importantly, it tests the way the language service will actually be installed by end users. Users would not have to add `@angular/language-service` to the plugins section in tsconfig.json Instead, all they need to do is install the *extension* from the VS Code Marketplace and Angular Language Service will be loaded as a global plugin. PR Close #28168
2018-12-18 02:44:26 -05:00
"test": "yarn cleanup && yarn build && jasmine test.js"
test(language-service): test `@angular/language-service` can be loaded by tsserver.js (#14721)
2017-03-01 16:22:46 -05:00
}
}