Igor Minar 63c9c2d2be fix: work around 'noImplicityAny' incompatibility due to ts3.7 update (#34798) ... Typescript 3.7 now emits d.ts files for getters differently than prior versions, and there seems to be a bug in how it strips private types without replacing them with explicit 'any' type. This then leads to compilation failures in projects compiled against our packages that don't have skipLibCheck turned on but do have strict or noImplicitAny check on. I'm working around this by marking the affected getters as @internal and adding a test to prevent future regressions. I believe this is a TypeScript bug, and I filed a bug report: https://github.com/microsoft/TypeScript/issues/36216 PR Close #34798		2020-01-16 12:06:57 -05:00
..
src	fix: work around 'noImplicityAny' incompatibility due to ts3.7 update (#34798)	2020-01-16 12:06:57 -05:00
BUILD.bazel	build: reference zone.js from source directly instead of npm. (#33046)	2019-11-06 00:48:34 +00:00
PACKAGE.md	docs: add api doc to sub-packages (#33801)	2019-11-20 14:48:50 -08:00
index.ts	build: publish tree of files rather than FESMs (#18541)	2017-08-31 15:34:50 -07:00
package.json	fix: correct several esm2015 entry-points in package.jsons (#22892)	2018-03-20 13:30:08 -07:00
public_api.ts	build: refactor ambient node & jasmine types so they are only included where needed (#25491)	2018-08-16 13:46:43 -07:00