angular-cn/packages/bazel/test/ng_package
Paul Gschwendtner 9bde1be5a4 test: disable ng_package tests in ivy test jobs (#36944)
Since we no longer hardcode the `package.json` for
entry-points, a bug has appeared for `ng_package` in Ivy.

The `package.json` files are populated incorrectly with Ivy
as the flat module bundle name is not propagated from `ng_module`
to the `ng_package` rule. The rule then guesses the index file
to `index.js` and does not respect the flat module bundle shim.

PR Close #36944
2020-05-06 13:54:27 -07:00
..
example test: add entry-point with generated imports to ng_package test (#35841) 2020-03-06 17:31:10 -05:00
example-with-ts-library build: update to rules_nodejs 1.2.0 (#34961) 2020-01-31 13:14:05 -08:00
BUILD.bazel test: disable ng_package tests in ivy test jobs (#36944) 2020-05-06 13:54:27 -07:00
common_package.spec.ts feat(bazel): simplify ng_package by dropping esm5 and fesm5 (#36944) 2020-05-06 13:54:26 -07:00
core_package.spec.ts feat(bazel): simplify ng_package by dropping esm5 and fesm5 (#36944) 2020-05-06 13:54:26 -07:00
example-custom-entry-point-name.golden build(bazel): use ng_package entry_point_name for umd bundles (#23132) 2018-04-05 14:51:31 -07:00
example_package.golden feat(bazel): simplify ng_package by dropping esm5 and fesm5 (#36944) 2020-05-06 13:54:26 -07:00
example_package.spec.ts fix(bazel): ng_package(data) should support non-text files (#32721) 2019-09-17 15:58:42 -07:00
example_with_ts_library_package.golden feat(bazel): simplify ng_package by dropping esm5 and fesm5 (#36944) 2020-05-06 13:54:26 -07:00