Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
angular/devtools/tsconfig.json

52 lines
1.3 KiB
JSON
Raw Normal View History

Initial commit for Angular DevTools
2020-01-27 18:40:18 +00:00
{
build(devtools): revert solution-style tsconfig to align with cli
2020-08-11 18:24:33 +00:00
"compileOnSave": false,
"compilerOptions": {
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"baseUrl": "../",
build(devtools): port over bazel tooling from angular/components Previously the ts_library bazel rule was used to build angular devtools. This commit migrates to ts project and brings in some bazel tooling from angular/components to run bundle spec files for karma tests.
2021-11-07 23:57:52 +00:00
"outDir": "bazel-out/darwin-fastbuild/bin",
build(devtools): revert solution-style tsconfig to align with cli
2020-08-11 18:24:33 +00:00
"sourceMap": true,
build(devtools): port over bazel tooling from angular/components Previously the ts_library bazel rule was used to build angular devtools. This commit migrates to ts project and brings in some bazel tooling from angular/components to run bundle spec files for karma tests.
2021-11-07 23:57:52 +00:00
"declaration": true,
refactor(devtools): enables typescript strict option (#53340) Enabling `strict` is part of an effort to improve the quality of the devtools code base. One of the direct side effect is to enable `noImplicitAny`, `strictPropertyInitialization` and `strictBindCallApply`. This commit also replaces `fullTemplateTypeCheck` with `stringTemplates`. PR Close #53340
2023-12-04 19:44:53 +00:00
"strict": true,
build: align with internal tsconfig options (#51728) Currently internally Angular has some customized tsconfig files, because we don't align with the tsconfig of the rest of g3. These changes enable `noImplicitReturns` and `noPropertyAccessFromIndexSignature` to align better with the internal config. PR Close #51728
2023-09-11 11:21:09 +00:00
"noImplicitReturns": true,
"noPropertyAccessFromIndexSignature": true,
build(devtools): revert solution-style tsconfig to align with cli
2020-08-11 18:24:33 +00:00
"downlevelIteration": true,
"experimentalDecorators": true,
"allowSyntheticDefaultImports": true,
"module": "esnext",
"moduleResolution": "node",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"esModuleInterop": true,
build(devtools): revert solution-style tsconfig to align with cli
2020-08-11 18:24:33 +00:00
"importHelpers": true,
build(devtools): port over bazel tooling from angular/components Previously the ts_library bazel rule was used to build angular devtools. This commit migrates to ts project and brings in some bazel tooling from angular/components to run bundle spec files for karma tests.
2021-11-07 23:57:52 +00:00
"target": "es2020",
refactor(devtools): Add hydration informations (#53910) This commit adds hydration informations to the devtools. * List of hydrated/hydrated components * Shows hydration overlays * Shows hydration errors for NG0500, 501 & 502 PR Close #53910
2024-01-19 19:29:24 +00:00
"lib": ["es2020", "dom", "dom.iterable"],
build(devtools): port over bazel tooling from angular/components Previously the ts_library bazel rule was used to build angular devtools. This commit migrates to ts project and brings in some bazel tooling from angular/components to run bundle spec files for karma tests.
2021-11-07 23:57:52 +00:00
"typeRoots": [
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"./devtools/node_modules/@types",
build(devtools): port over bazel tooling from angular/components Previously the ts_library bazel rule was used to build angular devtools. This commit migrates to ts project and brings in some bazel tooling from angular/components to run bundle spec files for karma tests.
2021-11-07 23:57:52 +00:00
],
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"types": [
"angular",
"jasmine",
"node"
build(devtools): port over bazel tooling from angular/components Previously the ts_library bazel rule was used to build angular devtools. This commit migrates to ts project and brings in some bazel tooling from angular/components to run bundle spec files for karma tests.
2021-11-07 23:57:52 +00:00
],
build(devtools): revert solution-style tsconfig to align with cli
2020-08-11 18:24:33 +00:00
"paths": {
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"@angular/*": [
"./packages/*",
"./dist/bin/packages/*"
],
build(devtools): port over bazel tooling from angular/components Previously the ts_library bazel rule was used to build angular devtools. This commit migrates to ts project and brings in some bazel tooling from angular/components to run bundle spec files for karma tests.
2021-11-07 23:57:52 +00:00
"ng-devtools": [
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"./devtools/projects/ng-devtools/src/public-api.ts",
build(devtools): port over bazel tooling from angular/components Previously the ts_library bazel rule was used to build angular devtools. This commit migrates to ts project and brings in some bazel tooling from angular/components to run bundle spec files for karma tests.
2021-11-07 23:57:52 +00:00
],
"ng-devtools-backend": [
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"./devtools/projects/ng-devtools-backend/src/public-api.ts",
build(devtools): port over bazel tooling from angular/components Previously the ts_library bazel rule was used to build angular devtools. This commit migrates to ts project and brings in some bazel tooling from angular/components to run bundle spec files for karma tests.
2021-11-07 23:57:52 +00:00
],
"protocol": [
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"./devtools/projects/protocol/src/public-api.ts",
build(devtools): port over bazel tooling from angular/components Previously the ts_library bazel rule was used to build angular devtools. This commit migrates to ts project and brings in some bazel tooling from angular/components to run bundle spec files for karma tests.
2021-11-07 23:57:52 +00:00
],
"shared-utils": [
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"./devtools/projects/shared-utils/src/public-api.ts",
build(devtools): port over bazel tooling from angular/components Previously the ts_library bazel rule was used to build angular devtools. This commit migrates to ts project and brings in some bazel tooling from angular/components to run bundle spec files for karma tests.
2021-11-07 23:57:52 +00:00
]
},
build(devtools): revert solution-style tsconfig to align with cli
2020-08-11 18:24:33 +00:00
},
"angularCompilerOptions": {
refactor(devtools): enables typescript strict option (#53340) Enabling `strict` is part of an effort to improve the quality of the devtools code base. One of the direct side effect is to enable `noImplicitAny`, `strictPropertyInitialization` and `strictBindCallApply`. This commit also replaces `fullTemplateTypeCheck` with `stringTemplates`. PR Close #53340
2023-12-04 19:44:53 +00:00
"strictTemplates": true,
refactor(compiler-cli): remove `enableIvy` options (#47346) This option has no longer any effect as Ivy is the only rendering engine. BREAKING CHANGE: Angular compiler option `enableIvy` has been removed as Ivy is the only rendering engine. PR Close #47346
2022-09-05 09:52:20 +00:00
"strictInjectionParameters": true
build(devtools): revert solution-style tsconfig to align with cli
2020-08-11 18:24:33 +00:00
}
refactor(compiler-cli): remove `enableIvy` options (#47346) This option has no longer any effect as Ivy is the only rendering engine. BREAKING CHANGE: Angular compiler option `enableIvy` has been removed as Ivy is the only rendering engine. PR Close #47346
2022-09-05 09:52:20 +00:00
}
Reference in a new issue Copy permalink