@vercel/microfrontends
2.4.2 · 20 Oct 20261.8M / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/microfrontends From 1.1.0 to 1.5.0
10 releases in betweennotes for 5
Reading releases, release notes and advisories…
- 1+
- change to make
- 0
- advisories fixed
- 4+
- new
- 1+
- fix
Counted from 5 of 10 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking1.2.0
Release by release
- New
Automatically add asset prefix to Next.js images using
images.pathinnext.config.js.
- New
1.4.2no release note
- Fixed
Route next/image requests to the correct microfrontends application in the local development proxy.
- Fixed
- New
Improve
PrefetchCrossZoneLinksProviderperformance.
- New
- New
Replace the need to add a
.well-knownendpoint for flagged paths. Instead, just add/.well-known/vercel/microfrontends/client-configto your middleware matcher. Note that the middleware is only required if you have flagged paths.
- New
1.2.1 – 1.2.44 releases, no release note
- Breaking
This release has some minor breaking changes.
- New
Improved local development proxy, simplified config, Vite support, more detailed error messages, testing, and more!
- Breaking
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.