Olivier Combe 91c7b451d5 feat(ivy): support i18n without closure (#28689) ... So far using runtime i18n with ivy meant that you needed to use Closure and `goog.getMsg` (or a polyfill). This PR changes the compiler to output both closure & non-closure code, while the unused option will be tree-shaken by minifiers. This means that if you use the Angular CLI with ivy and load a translations file, you can use i18n and the application will not throw at runtime. For now it will not translate your application, but at least you can try ivy without having to remove all of your i18n code and configuration. PR Close #28689		2019-04-11 08:28:45 -07:00
..
design	refactor(ivy): prefix all generated instructions (#29692)	2019-04-10 12:11:40 -07:00
src	feat(ivy): support i18n without closure (#28689)	2019-04-11 08:28:45 -07:00
test	test(ivy): add tests for component factory projectable node corner cases (#27791)	2019-03-25 13:47:48 -07:00
testing	build: turn off dts bundling for packages that still are not supported (#29128)	2019-03-07 10:47:20 -08:00
BUILD.bazel	style: enforce buildifier lint on CI (#28186)	2019-02-26 16:57:41 -08: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	fix(core): Remove static dependency from @angular/core to @angular/compiler (#26734)	2018-10-31 14:15:06 -04:00
public_api.ts	build: publish tree of files rather than FESMs (#18541)	2017-08-31 15:34:50 -07:00
tsconfig-build.json	build(bazel): Turning on strictPropertyInitialization for Angular. (#24572)	2018-06-25 07:57:13 -07:00