devtools/tsconfig.json

{
  "compilerOptions": {
    "sourceMap": true,
    "inlineSources": true,
    "declaration": true,
    "noImplicitReturns": true,
    "noPropertyAccessFromIndexSignature": true,
    "downlevelIteration": true,
    "experimentalDecorators": true,
    "allowSyntheticDefaultImports": true,
    "module": "esnext",
    "moduleResolution": "bundler",
    "esModuleInterop": true,
    "importHelpers": true,
    "target": "es2022",
    "lib": ["es2022", "dom", "dom.iterable"],
    "types": ["chrome"],
    // TODO: Have an IDE specific tsconfig file
    "paths": {
      "@angular/*": ["../packages/*/index"]
    }
  },
  "angularCompilerOptions": {
    "strictInjectionParameters": true,
    "extendedDiagnostics": {
      "checks": {
        "unusedStandaloneImports": "error"
      }
    }
  }
}
Initial commit for Angular DevTools 2020-01-27 13:40:18 -05:00			`{`
build(devtools): revert solution-style tsconfig to align with cli 2020-08-11 21:24:33 +03:00			`"compilerOptions": {`
			`"sourceMap": true,`
build(devtools): fix ng-devtools source maps (#62042) Inline the sources contents in the `js.map` files. This fixes the source maps for the dev app. PR Close #62042 2025-06-13 12:08:14 +03:00			`"inlineSources": 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 18:57:52 -05:00			`"declaration": 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 13:21:09 +02:00			`"noImplicitReturns": true,`
			`"noPropertyAccessFromIndexSignature": true,`
build(devtools): revert solution-style tsconfig to align with cli 2020-08-11 21:24:33 +03:00			`"downlevelIteration": true,`
			`"experimentalDecorators": true,`
			`"allowSyntheticDefaultImports": true,`
			`"module": "esnext",`
build: adopt `moduleResolution: "bundler"` (#64125) This commit updates the TypeScript configuration across the project to use `moduleResolution: "bundler"`. This modernizes our module resolution strategy to align with current TypeScript best practices and bundler behaviors. The following changes are included: - Updated `tsconfig.json` files to set `moduleResolution` to `"bundler"`. - Updated the `rules_angular` bazel dependency to a version compatible with these changes. - Adjusted related test files and golden files to reflect the new module resolution strategy. PR Close #64125 2025-09-29 14:32:10 +00:00			`"moduleResolution": "bundler",`
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 02:00:43 -05:00			`"esModuleInterop": true,`
build(devtools): revert solution-style tsconfig to align with cli 2020-08-11 21:24:33 +03:00			`"importHelpers": true,`
refactor(devtools): use WeakRef in idToInjector map for injector cleanup Replace the manual injectorsSeen cleanup mechanism with WeakRef and FinalizationRegistry. The old approach worked but coupled cleanup to the UI change detection and required tracking seen injectors across traversal. WeakRef lets the browser handle this naturally, removing the injectorsSeen set and the manual cleanup loop. 2026-03-29 22:18:28 -04:00			`"target": "es2022",`
			`"lib": ["es2022", "dom", "dom.iterable"],`
build: migrate devtools to use ng-project (#61317) Migrate devtools to use ng-project PR Close #61317 2025-05-13 19:59:40 +00:00			`"types": ["chrome"],`
build: set paths for devtools & adev (#62574) This allows the IDE to find the right imports PR Close #62574 2025-07-10 16:34:04 +02:00			`// TODO: Have an IDE specific tsconfig file`
refactor(devtools): use signal inputs for split component (#62550) This also introduced a local direction signal so it can be written from the outside PR Close #62550 2025-07-09 18:15:52 +02:00			`"paths": {`
			`"@angular/": ["../packages//index"]`
			`}`
build(devtools): revert solution-style tsconfig to align with cli 2020-08-11 21:24:33 +03:00			`},`
			`"angularCompilerOptions": {`
refactor(devtools): remove unused imports. (#58057) Thanks to the new extended diagnostic. PR Close #58057 2024-10-03 02:41:52 +02:00			`"strictInjectionParameters": true,`
build: remove explicit strict options Those options are enabled by default, they don't need to be explicit. 2026-08-06 00:26:40 +02:00			`"extendedDiagnostics": {`
			`"checks": {`
			`"unusedStandaloneImports": "error"`
			`}`
			`}`
build(devtools): revert solution-style tsconfig to align with cli 2020-08-11 21:24:33 +03: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			`}`