-
-
Notifications
You must be signed in to change notification settings - Fork 301
fix(nextjs-mf): fix broken loading of non nextjs remotes #3323
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(nextjs-mf): fix broken loading of non nextjs remotes #3323
Conversation
🦋 Changeset detectedLatest commit: 6c8f932 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for module-federation-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
the change to consume mf 2.0 manifests broke loading of non nextjs remotes because it was hard coded to assume next remotes.
0a6bf5a
to
7890299
Compare
@ScriptedAlchemy I know you aren't trying to pick up new nextjs-mf features but can you please look at this? It's blocking us atm as it breaks any non nextjs loading which I'm trying to migrate to. |
Will merge |
@h3adache please run |
Description
The change to consume mf 2.0 manifests broke loading of non nextjs remotes because it was hard coded to assume next remotes.
This change fixes loading of remotes while preserving the ability to load nextjs mf-manifests
Other minor changes are just to fix broken lint when running
Related Issue
Types of changes
Checklist