-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[babel 8] Reland "Use NodePath#hub
as part of the paths cache key"
#15759
Conversation
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/54888/ |
The angular error is caused by the caching changes, and not by the changes in |
Ohh :/ The problem is caused by using an old version of @alan-agius4 regardless of this bug on our side, what is the reason for pinning |
This should fix the compat problem, tested locally. Let's see if it fixes the angular-cli integration test. The fix/check is very bad, but it's self-contained and designed to run as less as possible (it only runs when calling into |
In general we pin all of our direct dependencies to have a more stable releases. By pinning all of our dependencies we reduce compatibility issues, bugs and other breaky behaviour as some packages don’t follow semver. Over the years this did prove to make the Angular CLI more stable especially for LTS versions. However, in this case though pinning did cause a problem. |
9694cbd
to
804f8e0
Compare
This is ready for review, but the code is incredibly ugly. Performance wise it's ok: the The angular-cli (breaking) test is failing because the workaround only applies to Babel 7, but it will start passing once |
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.
🤦
Could we possibly make it only land in babel8? |
804f8e0
to
d13e404
Compare
NodePath#hub
as part of the paths cache key"NodePath#hub
as part of the paths cache key"
I updated the PR to only land the breaking change in Babel 8. |
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.
Thanks!
This is just a revert of the revert of #15725, it's not fixed yet.