7 Commits

Author	SHA1	Message	Date
Alex Rickabaugh	ec4381dd40	feat: make the Ivy compiler the default for ngc (#32219) ... This commit switches the default value of the enableIvy flag to true. Applications that run ngc will now by default receive an Ivy build! This does not affect the way Bazel builds in the Angular repo work, since those are still switched based on the value of the --define=compile flag. Additionally, projects using @angular/bazel still use View Engine builds by default. Since most of the Angular repo tests are still written against View Engine (particularly because we still publish VE packages to NPM), this switch also requires lots of `enableIvy: false` flags in tsconfigs throughout the repo. Congrats to the team for reaching this milestone! PR Close #32219	2019-08-20 16:41:08 -07:00
Tobias Bosch	ed73d4f3ac	refactor(compiler): don’t always compile `.ngfactory.ts` files by default ... This puts the behavior introduced in 573b8611bc behind the new flag `alwaysCompileGeneratedCode` to not break users that might have relied on this behavior.	2017-06-12 15:27:02 -07:00
Tobias Bosch	573b8611bc	fix(compiler): compile `.ngfactory.ts` files even if nobody references them. (#16899) ... This is especially important for library authors, as they will not reference the .ngfactory.ts files. Fixes #16741	2017-05-25 11:00:26 -06:00
Igor Minar	b800a0c824	fix: prevent strictNullChecks support until #15432 is fixed (#15434)	2017-03-23 14:54:19 -07:00
Alex Eagle	03e855ae8f	build: allow users to specify --strictNullChecks (#14382) ... PR Close #14382	2017-02-10 14:10:03 -06:00
Alex Eagle	e9a89c0693	test: protractor test for closure bundle (#14240) ... PR Close #14240	2017-02-07 12:45:14 -06:00
Alex Eagle	4d5a4d89cd	test(integration): add an env for testing closure builds (#14130) ... * feat: add an env for testing closure builds * build(npm): add dev dependency on yarn (and remove dev props for readability) * build: refactor integration test runner	2017-01-27 09:17:50 -08:00