-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
fix(misc): shared deps that rely on default configuration are filtered out #16193
Conversation
…d out The issue was introduced by nrwl#15654. It then filters out and omits shared deps that rely on default configuration when return value from `shared` function is `undefined`. closed nrwl#15811
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
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.
Good catch!
Thanks for the contribution! 🎉
…d out (#16193) Co-authored-by: Dmitry Marcautan <[email protected]> (cherry picked from commit 432e074)
Thank you so much for this one! I think this will solve my problem where I haven't been able to update my project beyond |
Just tried out the beta and it seems to solve the issue! Thank you so much! |
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
The issue was introduced by #15654. It then filters out and omits shared deps that rely on default configuration when return value from
shared
function isundefined
.Current Behavior
NPM package dependencies are not made shared in module federation configuration when are not explicitly excluded in user provided
shared
function by returningundefined
valueExpected Behavior
NPM package dependencies should be made shared in module federation configuration unless
shared
function returnsfalse
valueRelated Issue(s)
Fixes #15811