Paul Gschwendtner c98a4d6ddd feat(ngcc): support for new APF where module points to esm2015 output (#36944) ...

As of version 10, libraries following the APF will no longer contain
ESM5 output. Hence, tests in ngcc need to be updated as they currently
rely on the release output of `@angular/core`.

Additionally, we'd need to support in ngcc that the `module`
property of entry-points no longer necessarily refers to
`esm5` output, but instead can also target `esm2015`.

We currently achieve this by checking the path the `module`
property points to. We can do this because as per APF, the
folder name is known for the esm2015 output. Long-term for
more coverage, we want to sniff the format by looking for
known ES2015 constructs in the file `module` refers to.

PR Close #36944

2020-05-06 13:54:26 -07:00

..

src

test(ivy): ngcc - test compiling the Angular Material library (#26403)

2018-11-01 14:13:26 -07:00

debug-test.sh

build: move build scripts to dedicated directory (#35780)

2020-03-04 08:35:26 -08:00

mock-ngcc-version-marker.js

fix(ngcc): correctly invalidate cache when moving/removing files/directories (#35106)

2020-02-03 14:25:47 -08:00

ngcc.config.js

feat(ngcc): allow async locking timeouts to be configured (#36838)

2020-05-01 09:52:10 -07:00

package.json

build: add npm_integration_test && angular_integration_test (#33927)

2020-02-24 08:59:18 -08:00

test.sh

feat(ngcc): support for new APF where module points to esm2015 output (#36944)

2020-05-06 13:54:26 -07:00

tsconfig-app.json

test(ivy): add an integration test for ngcc (#25406)

2018-08-22 19:28:56 -04:00

yarn.lock

build: update dependencies to use typescript 3.8 and angular 9.1 (#36329)

2020-05-05 16:52:43 -07:00