16fe90d6ac
Previously, when compiling the docs examples with `ngcc` (to run them in Ivy mode), we would only consider the `es2015` property. However, some packages (such as `angular-in-memory-web-api`) may not have that property in their `package.json`. They might still be compilable by `ngcc`, if they define other format properties (such as `module` or `main`), but `ngcc` would still fail if it could not find any of the _specified_ properties (here only `es2015`): ``` Error: Unable to process any formats for the following entry-points (tried es2015): - /.../node_modules/angular-in-memory-web-api ``` This commit fixes potential issues by considering all properties that would be considered if `ngcc` was run implicitly by `@angular/cli` and aligns the command with the one that will be generated for new apps: https://github.com/angular/angular/blob/3e14c2d02/packages/core/schematics/migrations/postinstall-ngcc/index.ts#L22 PR Close #33206
Angular
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages.
Quickstart
Changelog
Learn about the latest improvements.
Want to help?
Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues in the hotlist: community-help.