22 Commits

Author SHA1 Message Date
Alan Agius
a78fe96681 test: update ng-packagr tests tsconfig as per CLI default
This seems to be the root cause of the failures in the following PR:
https://github.com/angular/angular-cli/pull/17455
2020-04-13 11:33:53 -07:00
Alan Agius
cecb3de5b7 test: update tslint.json for test application to match latest new projects 2020-03-16 21:41:48 -07:00
Alan Agius
17b28f4c64 revert: "test(@angular-devkit/build-angular): add skipLibCheck to tests workspace tsconfig"
This reverts commit 3ae1eb6e2d80d424aee9fb966787d28843f5c2f4.
2020-01-29 10:20:50 -08:00
Cyrille Tuzi
ee589d9116 fix(@schematics/angular): add compliance with no-any lint rule 2020-01-29 10:19:36 -08:00
Alan Agius
3ae1eb6e2d test(@angular-devkit/build-angular): add skipLibCheck to tests workspace tsconfig
Add skipLibCheck to speed up TypeScript analysis and prevent compilation errors caused by incompatible declaration files which were generated with older/new TS versions
2020-01-16 14:48:23 -08:00
Filipe Silva
86d4385440 build: use TypeScript 3.7 2020-01-09 13:43:49 -08:00
Filipe Silva
fd49f2e2fc test: disable typescript version check 2019-10-16 10:00:49 -07:00
Filipe Silva
60f9b19ecd test: use Ivy by default, opt-in to VE 2019-08-28 22:54:52 +05:30
Alan Agius
ad8acb0d23 build: bump angular dev packages to latest next versions 2019-08-22 09:41:28 -07:00
Alan Agius
96c457d6a5 refactor: add enableIvy: true until FW flips it on by default 2019-08-16 09:31:02 -07:00
Alan
ba8a6ea599 feat(@schematics/angular): remove enableIvy option
With this change we remove the enableIvy option as now we only support generating Ivy application. Users who want to create a VE applications should follow the opt-out guide
2019-08-16 09:31:02 -07:00
Alan
e8e6f8a6df test: update Ivy tests as per new workspace settings 2019-08-16 09:31:02 -07:00
Alan Agius
0111693271 Ivy build_ng_packagr (#15262)
* test: update ng-packagr builder tests to work on Windows

* build: add ng packagr test large for ivy

* test: fix web-worker test in ivy

Previously, we were not testing web workers under Ivy as we were overriding tsconfig.app.json entirely without including enableIvy.

When enabling Ivy we are getting warning of files that are part of the compilation which causing a warning to show and break the test.

* build: update ng-packagr to `^5.4.0`

* test: display ivy mode message once
2019-08-12 10:20:02 -07:00
Charles Lyding
246abb3935 feat(@angular-devkit/build-angular): update to core-js 3
Fixes  #13954
2019-04-04 09:28:02 -07:00
WilliamKoza
d841b3771e fix(@schematics/angular): change entry file name of the library schematic according to the kebab-case convention 2019-03-11 13:40:02 -07:00
Alan Agius
a139243644 refactor: clean up library tsconfig
These properties are already defined in the root tsconfig
2019-02-14 20:58:59 +08:00
Alan Agius
6ae1752891 feat(@schematics/angular): remove annotateForClosureCompiler in libraries tsconfig (#13546)
Users outside of Google don't usually need closure annotations.

We should also follow up with ng-packagr to remove tsickle from peerDependency and afterwards, we be able to remove tsickle from the added dependencies when running this schematic
2019-01-30 11:24:04 -08:00
Filipe Silva
5a847298e5 ci: use puppeteer 2019-01-14 12:57:13 -08:00
Alan Agius
718ee15b9a refactor: remove flatModuleId and flatModuleOutFile from library tsconfig
The autogenerated fiellds are no longer required following this PR https://github.com/dherges/ng-packagr/pull/1024

This has been released in `ng-packagr` `v4.1.0`
2018-08-21 10:16:38 -07:00
Alan Agius
1caf708dca feat(@angular-devkit/build-ng-packagr): update ng-packagr to version 4 2018-07-25 22:54:22 +01:00
Filipe Silva
63b2b1148a test(@angular-devkit/build-angular): use targets instead of architect property 2018-07-25 20:17:33 +01:00
Hans
91e7c3eb96 test: remove unused test directory and remove @ from paths 2018-07-12 09:26:36 -07:00