angular/integration/ngcc
Paul Gschwendtner d442764470 refactor(compiler-cli): adjust lock file resolution in ngcc to work with ESM (#43431)
Updates the lock file resolution logic in ngcc to work with ESM output.
The compiler-cli is now shipped in bundles, so the actual module resolution
needs to stay to keep the lock file path consistent regardless of where the
lock file code is bundled into. The ngcc integration test needs to be updated
though since the `ngcc` entry-point will always reside in the `bundles/` directory
now.

It has been considered using the top-level `package.json` of the compiler-cli
package, but that caused problems in tests down the line because the ngcc
tests only have the `@angular/compiler-cli/ngcc/...` targets linked into
the node modules. It's not worth changing this and reworking tests if ngcc
is going away in the future anyway (+ it has been like that before!).

PR Close #43431
2021-10-01 18:28:45 +00: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 build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04:00
ngcc.config.js feat(ngcc): allow async locking timeouts to be configured (#36838) 2020-05-01 09:52:10 -07:00
package.json test: update basic integration tests to work with new package output (#43431) 2021-10-01 18:28:43 +00:00
test.sh refactor(compiler-cli): adjust lock file resolution in ngcc to work with ESM (#43431) 2021-10-01 18:28:45 +00:00
tsconfig-app.json test(ivy): add an integration test for ngcc (#25406) 2018-08-22 19:28:56 -04:00
yarn.lock test: update basic integration tests to work with new package output (#43431) 2021-10-01 18:28:43 +00:00