Paul Gschwendtner 8e12707f88 build: remove dependency on @types/chokidar (#35371) ... We recently updated chokidar to `3.0.0`. The latest version of chokidar provides TypeScript types on its own and makes the extra dependency on the `@types` unnecessary. This seems to have caused the `build-packages-dist` script to fail with an error like: ``` [strictDeps] transitive dependency on external/npm/node_modules/chokidar/types/index.d.ts not allowed. Please add the BUILD target to your rule's deps. ``` It's unclear why that happens, but a reasonable theory would be that the TS compilation accidentally picked up the types from `chokidar` instead of `@types/chokidar`, and the strict deps `@bazel/typescript` check reported this as issue because it's not an explicit target dependency. PR Close #35371		2020-02-19 12:49:52 -08:00
..
integrationtest	feat(ngcc): automatically clean outdated ngcc artifacts (#35079)	2020-01-31 17:02:44 -08:00
ngcc	feat(ngcc): pause async ngcc processing if another process has the lockfile (#35131)	2020-02-18 17:20:41 -08:00
src	feat(ngcc): pause async ngcc processing if another process has the lockfile (#35131)	2020-02-18 17:20:41 -08:00
test	fix(ivy): repeat template guards to narrow types in event handlers (#35193)	2020-02-07 13:06:00 -08:00
BUILD.bazel	build: remove dependency on @types/chokidar (#35371)	2020-02-19 12:49:52 -08:00
index.ts	refactor(compiler-cli): Move diagnostics files to language service (#33809)	2019-11-14 09:29:07 -08:00
package.json	feat(ngcc): automatically clean outdated ngcc artifacts (#35079)	2020-01-31 17:02:44 -08:00
tsconfig-build.json	build: reference zone.js from source directly instead of npm. (#33046)	2019-11-06 00:48:34 +00:00
tsconfig.json	perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525)	2019-07-09 09:40:46 -07:00