-
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
feat(webpack): move module federation utils to webpack #18996
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
730ceec
to
ab0601c
Compare
ab0601c
to
4b35184
Compare
4b35184
to
e8a226e
Compare
e8a226e
to
2a096f2
Compare
2a096f2
to
515d431
Compare
515d431
to
2d09112
Compare
2d09112
to
d69a911
Compare
d69a911
to
b1f3506
Compare
b1f3506
to
4c536af
Compare
|
||
let { readJsonFile, joinPathFragments, workspaceRoot, readModulePackageJson } = | ||
requireNx(); | ||
let { readModulePackageJson } = requireNx(); |
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.
You changed other imports other than this. Can you change this too in a followup please?
This should come from nx directly.
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. |
Current Behavior
Our Module Federation utilities currently live in
@nx/devkit
. They were placed here for convenience during the previous effort on MF.Expected Behavior
Our Module Federation utilities will live in
@nx/webpack
which makes more sense as we currently, and for the foreseeable future, only support Webpack Module Federation.This will also remove them from the
@nx/devkit
Public API, usage of which has been deprecated already.Related Issue(s)
Fixes #