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
..
design	docs(compiler): fix typos and spelling (#34008)	2019-12-03 16:05:32 -08:00
src	fix: work around 'noImplicityAny' incompatibility due to ts3.7 update (#34798)	2020-01-16 12:06:57 -05:00
test	build: derive ts_library dep from jasmine_node_test boostrap label if it ends in `_es5` (#34736)	2020-01-15 14:58:07 -05:00
testing	build: remove unreferenced tsconfig-build.json files (#30858)	2019-06-05 09:03:36 -07:00
BUILD.bazel	build: convert entry_point to label (#30627)	2019-06-11 00:03:11 +00:00
compiler.ts	build: roll up to named .js files rather than 'index.js' (#19190)	2017-09-19 16:59:18 -07:00
index.ts	build: roll up to named .js files rather than 'index.js' (#19190)	2017-09-19 16:59:18 -07:00
package.json	build: set up all packages to publish via wombot proxy (#33747)	2019-11-13 11:34:33 -08:00
public_api.ts	build: publish tree of files rather than FESMs (#18541)	2017-08-31 15:34:50 -07:00