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

26 lines
503 B
JSON
Raw Normal View History

build: TypeScript 3.5 upgrade (#31615) https://github.com/Microsoft/TypeScript/wiki/Breaking-Changes#typescript-35 PR Close #31615
2019-07-17 20:49:16 -04:00
{
"compilerOptions": {
test: make all typings integration tests use ts strict mode (#34798) previously they didn't which was a bug/oversight. PR Close #34798
2020-01-15 16:31:43 -05:00
"strict": true,
test: explicitly turn off skipLibCheck for typings tests (#34798) skipLibCheck=false is currently the default (in tsc 3.7.4) but it wouldn't be shocking if the default changed in the future because skipLibCheck=true makes more sense in almost all scenarios. So just to be defensive and explicit, I'm setting the flag to false even though it's the current default. PR Close #34798
2020-01-15 23:40:40 -05:00
"skipLibCheck": false,
build: TypeScript 3.5 upgrade (#31615) https://github.com/Microsoft/TypeScript/wiki/Breaking-Changes#typescript-35 PR Close #31615
2019-07-17 20:49:16 -04:00
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"module": "commonjs",
"moduleResolution": "node",
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
"outDir": "./dist/out-tsc",
build: TypeScript 3.5 upgrade (#31615) https://github.com/Microsoft/TypeScript/wiki/Breaking-Changes#typescript-35 PR Close #31615
2019-07-17 20:49:16 -04:00
"rootDir": ".",
"target": "es5",
"lib": [
"es5",
"dom",
"es2015.collection",
"es2015.iterable",
"es2015.promise"
],
"types": [],
},
"files": [
"include-all.ts",
"node_modules/@types/jasmine/index.d.ts"
]
}