tag/19.2.2/devtools/tsconfig.spec.json

{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "plugins": [
      {
        "name": "@bazel/tsetse",
        "disabledRules": [
          "must-use-promises"
        ]
      }
    ],
    "sourceMap": false,
    "types": ["jasmine", "node"],
  }
}
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			`"extends": "./tsconfig.json",`
Initial commit for Angular DevTools 2020-01-27 13:40:18 -05:00			`"compilerOptions": {`
fix(devtools): issue where backendReady race condition causes Angular not detected error (#54805) Previously, a race condition could cause DevTools to enter a state where it can't detect an application on reload. This was caused by a sequencing issue between the content script connection, the devtools panel connection and an event "backendReady" that lets DevTools know when a particular frame is ready to be inspected. This commit replaces the previously stored backendReady boolean with a promise, so that the devtools panel can eventually run a callback to connect to a content script when that content script emits it's backendReady message. PR Close #54805 2024-03-11 03:06:23 -04:00			`"plugins": [`
			`{`
			`"name": "@bazel/tsetse",`
			`"disabledRules": [`
			`"must-use-promises"`
			`]`
			`}`
			`],`
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			`"sourceMap": false,`
			`"types": ["jasmine", "node"],`
			`}`
			`}`