tools/tsconfig.json

{
  // This tsconfig is only used by IDEs, no actual builds.
  "compilerOptions": {
    "baseUrl": ".",
    "declaration": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "module": "commonjs",
    "esModuleInterop": true,
    "moduleResolution": "node",
    "outDir": "../dist/tools/",
    "noImplicitAny": true,
    "noFallthroughCasesInSwitch": true,
    "paths": {
      "@angular/*": ["../packages/*"]
    },
    "rootDirs": [".", ".."],
    "sourceMap": true,
    "inlineSources": true,
    "lib": [
      "es6",
      "dom"
    ],
    "target": "es5",
    "skipLibCheck": true,
    "types": [
      "node"
    ]
  },
  "exclude": [
    "testing",
    "node_modules",
    "typings-test",
    "public_api_guard",
    "docs"
  ],
  "bazelOptions": {
    "suppressTsconfigOverrideWarnings": true
  }
}
chore(typescript 1.6 upgrade): fix build.tools 2015-09-22 12:03:39 -07:00			`{`
build: add rules for generating block/element API data (#52480) Adds build rules for "artificially" generating `DocEntry` collections for block and element APIs. The two rules are very similar, but _just_ different enough that it's worth having two separate implementations. PR Close #52480 2023-10-31 18:02:22 -07:00			`// This tsconfig is only used by IDEs, no actual builds.`
repackaging: all the repackaging changes squashed 2016-04-28 17:50:03 -07:00			`"compilerOptions": {`
			`"baseUrl": ".",`
			`"declaration": true,`
			`"emitDecoratorMetadata": true,`
			`"experimentalDecorators": true,`
			`"module": "commonjs",`
build: enable `esModuleInterop` in TypeScript compilations (#43431) Enables the `esModuleInterop` for all TypeScript compilations in the project. This allows us to emit proper ESM-compatible code. e.g. consider the following import: ```ts import * as ts from 'typescript'; ``` This import currently will break at runtime in NodeJS because the `typescript` package is not shipping ESM. It's still a CommonJS module. ES modules are able to import from `typescript` though, using an import statement as above, but everything in `module.exports` is being exposed as the `default` named export. TypeScript at runtime does not have any other named exports, so for actual ESM compatibility, all of our imports need to be switched to: ``` import ts from 'typescript'; ``` The `esModuleInterop` option allows this to work even though the `d.ts` file of TS currently suggests that there are _only_ named exports. The TypeScript language service will now suggest the correct import form as shown above. It doesn't enforce that unfortunately, but this commit also adds a lint rule that enforces certain patterns so that we emit imports that are compatible with both ESM and CJS output (CJS still needed here since tests run with CJS devmode output still; this is a future project to switch that over to ESM!) PR Close #43431 2021-09-25 14:58:32 +02:00			`"esModuleInterop": true,`
repackaging: all the repackaging changes squashed 2016-04-28 17:50:03 -07:00			`"moduleResolution": "node",`
			`"outDir": "../dist/tools/",`
chore(typing): enforce --noImplicitAny for tools directory. Exposed a couple of bugs. Closes #6645 2016-01-22 10:51:16 -08:00			`"noImplicitAny": true,`
chore(typescript): Enabled noFallthroughCasesInSwitch Turned on the noFallthroughCasesInSwitch flag in tsconfig and fixed a few cases where there were fallthroughs. 2016-06-22 15:57:24 -07:00			`"noFallthroughCasesInSwitch": true,`
build: add rules for generating block/element API data (#52480) Adds build rules for "artificially" generating `DocEntry` collections for block and element APIs. The two rules are very similar, but _just_ different enough that it's worth having two separate implementations. PR Close #52480 2023-10-31 18:02:22 -07:00			`"paths": {`
			`"@angular/": ["../packages/"]`
			`},`
			`"rootDirs": [".", ".."],`
repackaging: all the repackaging changes squashed 2016-04-28 17:50:03 -07:00			`"sourceMap": true,`
			`"inlineSources": true,`
build: Bazel builds ngfactories for packages/core (#18289) PR Close #18289 2017-07-21 14:20:34 -07:00			`"lib": [`
			`"es6",`
			`"dom"`
			`],`
fix(packages): use ES modules for primary build (#11120) 2016-08-30 18:07:40 -07:00			`"target": "es5",`
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488 2018-10-04 13:14:14 -07:00			`"skipLibCheck": true,`
			`"types": [`
			`"node"`
			`]`
repackaging: all the repackaging changes squashed 2016-04-28 17:50:03 -07:00			`},`
			`"exclude": [`
build: add istruction for running and debugging tests to `BAZEL.md` (#21053) PR Close #21053 2017-12-18 16:14:23 -08:00			`"testing",`
fix: add typescript test for our typings (#9096) * Revert "fix(d.ts): enable angular2 compilation with TS flag --strictNullChecks (#8902)" This reverts commit 7e352a27f7172a80cfc5aefa6296ebbaca8df450. * test: add typescript test for our typings 2016-06-08 16:06:23 -07:00			`"node_modules",`
test: upgrade ts-api-guardian to v0.1.2 2016-06-22 11:28:40 -07:00			`"typings-test",`
build(aio): move doc-gen stuff from angular.io (#14097) 2017-01-26 14:03:53 +00:00			`"public_api_guard",`
			`"docs"`
build: ts-api-guardian tsconfig warning with bazel (#27583) * Suppresses the warning from the Bazel TypeScript rules about overwritten options from the `tools/tsconfig.json` file. This is the only remaining warning that makes our Bazel build on Angular Material "dirty" PR Close #27583 2018-12-10 20:25:49 +01:00			`],`
			`"bazelOptions": {`
			`"suppressTsconfigOverrideWarnings": true`
			`}`
			`}`