History

George Kalpakas 326240eb91 fix(ngcc): allow ngcc configuration to match pre-release versions of packages (#36370 ) Ngcc supports providing a project-level configuration to affect how certain dependencies are processed and also has a built-in fallback configuration for some unmaintained packages. Each entry in these configurations could be scoped to specific versions of a package by providing a version range. If no version range is provided for a package, it defaults to `*` (with the intention of matching any version). Previously, the installed version of a package was tested against the version range using the [semver][1] package's `satisfies()` function with the default options. By default, `satisfies()` does not match pre-releases (see [here][2] for more details on reasoning). While this makes sense when determining what version of a dependency to install (trying to avoid unexpected breaking changes), it is not desired in the case of ngcc. This commit fixes it by explicitly specifying that pre-release versions should be matched normally. [1]: https://www.npmjs.com/package/semver [2]: https://github.com/npm/node-semver#prerelease-tags PR Close #36370		2020-04-01 13:32:32 -07:00
..
src	fix(ngcc): allow ngcc configuration to match pre-release versions of packages (#36370 )	2020-04-01 13:32:32 -07:00
test	fix(ngcc): allow ngcc configuration to match pre-release versions of packages (#36370 )	2020-04-01 13:32:32 -07:00
BUILD.bazel	fix(ngcc): use path-mappings from tsconfig in dependency resolution (#36180 )	2020-03-24 10:16:12 -07:00
README.md	refactor(ivy): move ngcc into a higher level folder (#29092 )	2019-03-20 14:45:54 -04:00
index.ts	refactor(ngcc): expose logging level on the logger (#35861 )	2020-03-05 18:17:15 -05:00
main-ivy-ngcc.ts	fix(ngcc): rename the executable from `ivy-ngcc` to `ngcc` (#33140 )	2019-10-14 16:29:14 +00:00
main-ngcc.ts	fix(ngcc): use path-mappings from tsconfig in dependency resolution (#36180 )	2020-03-24 10:16:12 -07:00

README.md

Angular Compatibility Compiler (ngcc)

This compiler will convert node_modules compiled with ngc, into node_modules which appear to have been compiled with ngtsc.

This conversion will allow such "legacy" packages to be used by the Ivy rendering engine.

Building

The project is built using Bazel:

yarn bazel build //packages/compiler-cli/ngcc

Unit Testing

The unit tests are built and run using Bazel:

yarn bazel test //packages/compiler-cli/ngcc/test

Integration Testing

There are tests that check the behavior of the overall executable:

yarn bazel test //packages/compiler-cli/ngcc/test:integration