86e1e6c082
feat: typescript 3.6 support ( #32946 )
...
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6
Fixes #32380
PR Close #32946
2019-10-18 13:15:16 -04:00
df1c456347
fix(bazel): ng_package(data) should support non-text files ( #32721 )
...
PR Close #32721
2019-09-17 15:58:42 -07:00
c198a27a3c
test: update golden files ( #32069 )
...
PR Close #32069
2019-08-09 14:15:25 -07:00
6ece7db37a
build: TypeScript 3.5 upgrade ( #31615 )
...
https://github.com/Microsoft/TypeScript/wiki/Breaking-Changes#typescript-35
PR Close #31615
2019-07-25 17:05:23 -07:00
75748d6044
feat: add support for TypeScript 3.3 (and drop older versions) ( #29004 )
...
https://blogs.msdn.microsoft.com/typescript/2019/01/31/announcing-typescript-3-3/
BREAKING CHANGE: TypeScript 3.1 and 3.2 are no longer supported.
Please update your TypeScript version to 3.3
PR Close #29004
2019-03-13 10:38:37 -07:00
3bb3d6d3e6
test: update ng_package tests to use bundle_dts ( #28588 )
...
PR Close #28588
2019-02-13 19:16:29 -08:00
a100472b5d
build: bump year ( #27880 )
...
PR Close #27880
2019-01-11 11:15:59 -08:00
b78351cc7e
build(bazel): Bump @bazel/typescript & @bazel/karma to 0.22.1 ( #28031 )
...
PR Close #28031
2019-01-10 16:49:56 -08:00
ac5f5ed0a6
test(bazel): re-enable ng_package golden testing on ci ( #27829 )
...
* Enables the ng_package golden testing on the CI
* Fixes the ng_package golden testing for Windows
PR Close #27829
2019-01-07 14:46:47 -08:00
8122970f63
test(bazel): fix all ng_package tests not working on windows ( #27829 )
...
PR Close #27829
2019-01-07 14:46:47 -08:00
da58a55ece
fix(bazel): don't produce ngfactory files for ng_packages ( #23237 )
...
PR Close #23237
2018-04-06 16:26:31 -07:00
ae8a0092bd
build(bazel): use ng_package entry_point_name for umd bundles ( #23132 )
...
This change also requires updating the package gold test to work with
multiple test packages.
PR Close #23132
2018-04-05 14:51:31 -07:00
481b22ecb0
fix(bazel): downlevel decorators in fesm5 files ( #23078 )
...
Needed so that our bundles appear side-effect-free to tools like webpack
PR Close #23078
2018-03-29 18:53:49 -07:00
45e090b614
fix(bazel): pass --global option to rollup ( #23073 )
...
This fixes the UMD bundles which otherwise don't contain the right global symbols
PR Close #23073
2018-03-29 17:44:43 -07:00
2aabbc51fa
fix(bazel): ng_package packages attr not forwarded to npm_package ( #22967 )
...
PR Close #22967
2018-03-26 22:32:09 -04:00
d9a0a8ff3e
build(bazel): add `data` attr to ng_package ( #22919 )
...
PR Close #22919
2018-03-23 13:16:07 -04:00
64efcf103c
build: add the FESM files back to ng_package ( #22889 )
...
PR Close #22889
2018-03-21 13:19:19 -07:00
689f351092
build: expose flatModuleOutFile option on ng_module ( #22814 )
...
This lets projects like Material change ng_package "bundle index" files to non-conflicting paths
Currently packages like @angular/core ship with the generated metadata
in a path like 'core.js' which overwrites one of the inputs.
Angular material puts the generated file in a path like 'index.js'
Either way these files generated by ng_module rules have the potential
to collide with inputs given by the user, which results in an error.
Instead, give users the freedom to choose a different non-conflicting name.
Also this refactors the ng_package rule, removing the redundant
secondary_entry_points attribute.
Instead, we assume that any ng_module in the deps with a module_name
attribute is a secondary entry point.
PR Close #22814
2018-03-20 13:28:57 -07:00
Igor Minar
Jason Bedard
Alan
Adam Plumer
Keen Yee Liau
Paul Gschwendtner
Jeremy Elbourn
Alex Eagle