35450c78f7
This commit changes the reference emitters in the Ivy compiler to prefer non-aliased exports if they exist. This avoids selecting "private exports" that may not be stable, e.g. the reexports that have been added by the View Engine compiler. Such reexports are not stable and are therefore not suitable to be emitted into partial compilations, as the output of partial compilations should only reference stable symbols from upstream libraries. An alternative solution has been considered where ViewEngine-generated exports would gain a certain prefix, such that the Ivy compiler could just exclude those exports (see #41443). However, that solution would be insufficient in case a library is built using partial compilation and while depending itself on a VE-compiled library from earlier versions of Angular, where the magic prefix would be missing. For such libraries, ngcc would have generated reexports using the declared name if not already present so this change does result in choosing the correct export. Because ngcc always generates reexports using the declared name even if an aliased export is present, this change causes those ngcc-generated exports to be chosen in downstream libraries using partial compilation. This is unfortunate as it means that the declared names become effectively public even if the library author was intentionally exporting it using an alias. This commit does not address this problem; it is expected that this should not result in widespread issues across the library ecosystem. Fixes #41277 PR Close #41866 |
||
|---|---|---|
| .circleci | ||
| .devcontainer | ||
| .github | ||
| .husky | ||
| .ng-dev | ||
| .vscode | ||
| .yarn | ||
| aio | ||
| dev-infra | ||
| docs | ||
| goldens | ||
| integration | ||
| modules | ||
| packages | ||
| scripts | ||
| third_party | ||
| tools | ||
| .bazelignore | ||
| .bazelrc | ||
| .bazelversion | ||
| .clang-format | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmessage | ||
| .mailmap | ||
| .npmrc | ||
| .nvmrc | ||
| .pullapprove.yml | ||
| .yarnrc | ||
| BUILD.bazel | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| WORKSPACE | ||
| browser-providers.conf.js | ||
| gulpfile.js | ||
| karma-js.conf.js | ||
| package.json | ||
| renovate.json | ||
| test-events.js | ||
| test-main.js | ||
| tslint.json | ||
| yarn.lock | ||
| yarn.lock.readme.md | ||
README.md
Angular - One framework. Mobile & desktop.
Angular is a development platform for building mobile and desktop web applications
using Typescript/JavaScript and other languages.
Contributing Guidelines
·
Submit an Issue
·
Blog
Documentation
Get started with Angular, learn the fundamentals and explore advanced topics on our documentation website.
Advanced
Development Setup
Prerequisites
- Install Node.js which includes Node Package Manager
Setting Up a Project
Install the Angular CLI globally:
npm install -g @angular/cli
Create workspace:
ng new [PROJECT NAME]
Run the application:
cd [PROJECT NAME]
ng serve
Angular is cross-platform, fast, scalable, has incredible tooling, and is loved by millions.
Quickstart
Ecosystem
Changelog
Learn about the latest improvements.
Upgrading
Check out our upgrade guide to find out the best way to upgrade your project.
Contributing
Contributing Guidelines
Read through our contributing guidelines to learn about our submission process, coding rules and more.
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 labeled as help wanted or good first issue.
Code of Conduct
Help us keep Angular open and inclusive. Please read and follow our Code of Conduct.
Community
Join the conversation and help the community.
Love Angular? Give our repo a star ⭐ ⬆️.