-
Notifications
You must be signed in to change notification settings - Fork 47k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unify the way we fork modules #11711
Conversation
Verified the first commit doesn't change a single byte in the bundles. |
❤️ This looks great, Dan |
The second commit adds my custom plugin for replacing forks since I figured more control is nicer anyway since it's a pretty important part. |
This does exactly what we need and doesn't suffer from rollup/rollup-plugin-alias#34.
Should be ready for review. |
Verified the final changes don't change the build either. |
I settled on calling them "forks" since we already have a different concept of "shims".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This unifies the ad hoc way we fork modules so it's easy to see which modules are forked under which conditions, and how to add new forks. This will help us get rid of the existing external dynamic injection that we still rely on in www (after this is merged).