@vercel/microfrontends
2.4.2 · 20 Oct 20261.8M / weekRepositoryHomepagenpmAtom feed
55 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 2.x · latest line
2.4.2
20 Oct 2026Reuse the parsed config and compiled path matchers in
runMicrofrontendsMiddlewareacross requests instead of rebuilding them on every request
2.4.1
12 Oct 2026Print the configured local proxy origin in the startup URL while keeping the localhost proxy target visible.
Avoid Node.js
url.parse()deprecation warnings when routing requests through the local proxy.
2.4.0
7 Jul 2026Add an optional configured origin to the local development proxy via
--origin <origin>or theMFE_LOCAL_PROXY_ORIGINenvironment variable (for examplehttps://web.localhost). When set, the proxy forwards that origin to your applications asx-forwarded-proto/x-forwarded-host/x-forwarded-portand rewrites fallback redirects onto it, so apps served behind a custom local hostname or a TLS terminator see the URL the browser actually used. When no origin is configured, inbound forwarded headers pass through unchanged.
2.3.6
4 Jun 2026Prevent the local development proxy from crashing on mid-stream upstream errors
The HTTPS fallback path piped the upstream (production) response to the client without attaching an error handler. When that upstream connection reset mid-stream — common when many requests fan out to a production fallback — the unhandled
errorevent surfaced as an uncaught exception and crashed the proxy process. The upstream response and client request/response streams now have error handlers that tear down the affected request instead of throwing.
2.3.5
2 Jun 2026Preserve absolute URLs in query parameters when the local proxy normalizes request URLs and rewrites redirect Location headers.
Route Vercel Toolbar well-known requests through the local proxy to the locally running application that served the page. This supports
@vercel/toolbar@0.2.6+, which uses/.well-known/vercel-toolbar/*for local dev server access.
2.3.4
26 May 2026Prevent local proxy crashes when upstream errors occur after response headers have already been sent.
2.3.3
19 May 2026Convert file level JSDoc to a regular block comment in schema types to prevent OpenAPI generators from incorrectly associating it with the
Configinterface declaration.Disable prerender speculation rules on Chromium 147 to avoid a browser crash triggered during cross-zone navigation. Prefetch rules are unaffected. The guard auto-resolves on Chrome 148+, which ships the upstream fix.
2.3.2
30 Mar 2026Update local proxy to use
VERCEL_AUTOMATION_BYPASS_SECRETfor bypassing deployment protection on fallback deployments. This is the preferred approach now that multiple automation bypasses are supported. The per-appAUTOMATION_BYPASS_<NAME>secret is still supported.Convert file-level JSDoc to a regular block comment in schema types to prevent OpenAPI generators from incorrectly associating it with the
Configinterface declaration.
2.3.1
18 Feb 2026Expose generateDefaultAssetPrefixFromName
2.3.0
26 Jan 2026Only updates a dependency:path-to-regexp 6.3.0
2.2.2
14 Jan 2026Add environment variable overrides for local development ports, enabling multiple worktrees to run simultaneously:
Note:
MFE_APP_PORTonly works when a single application is running locally. An error will be thrown if multiple local apps are detected with this variable set.Usage:
MFE_APP_PORT=4000 MFE_LOCAL_PROXY_PORT=3025 pnpm dev
Remove an error from withMicrofrontends when using Next.js 16 with default Turbopack support.
2.2.1
3 Dec 2025Improve debug logging when inferring the microfrontends.json configuration when the MFE_DEBUG env var is set.
2.2.0
7 Nov 2025Two improvements to the local development proxy:
In addition, we are deprecating two options in
withMicrofrontendsfor configuring microfrontends:
2.1.3
30 Oct 2025Fix Next.js image optimization locally for any image path
2.1.2
28 Oct 2025Fix local Next.js Image Optimization
2.1.1
28 Oct 2025- Security
96f0ea5: Fix local Next.js image optimization. Next.js released a security fix which removes headers from being passed on image optimization requests. The microfrontends local proxy previously relied on the headers being passed.
96f0ea5: Add support for locally overriding to MFE aliases: vercel.com/changelog/preview-links-between-micr…
2.1.0
24 Oct 2025c856a5d: Add support for custom
microfrontends.jsonfile names. This enables a single application to be deployed as multiple different vercel projects / microfrontends.c856a5d: Strip asset prefix from Vercel Firewall rate limit paths. Support Vercel Firewall rate limit requests when they go to a child application.
2.0.1
15 Oct 20258c11bdc: Support hyphens and escaped special characters in supported path matching regex vercel.com/docs/microfrontends/path-routing
8c11bdc: Improve error message for when local development proxy can't determine the port
8c11bdc: Update local proxy double slash routing behaviour to match the production proxy
2.0.0
6 Aug 2025- Breaking
This release removes the project name and flag names from being visible to client side code.
Use user-provided appName when inferring the location of microfrontends.json.
Improve error messages when the name in
package.jsondoes not match the Vercel project name.
- 1.x
1.5.0
18 Jul 2025Automatically add asset prefix to Next.js images using
images.pathinnext.config.js.
1.4.2
8 Jul 20251.4.1
3 Jul 2025Route next/image requests to the correct microfrontends application in the local development proxy.
1.4.0
25 Jun 2025Improve
PrefetchCrossZoneLinksProviderperformance.
1.3.0
22 May 2025Replace 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.
1.2.0
9 Apr 2025Improved local development proxy, simplified config, Vite support, more detailed error messages, testing, and more!
This release has some minor breaking changes. We try not do this, but at this stage of the project (where we have a relatively small amount of users, each who we're working closely with), we are leaning more towards breaking things and providing clear upgrade instructions so we can move a little quicker. Please let us know if you have concerns with this approach!
1.1.0
13 Mar 2025844006a: Add experimental support for SvelteKit.
844006a: Add experimental support for Vite and React Router.
844006a: Improved inference for NX monorepos.
Minor Changes
844006a: Add experimental support for SvelteKit.
844006a: Add experimental support for Vite and React Router.
844006a: Improved inference for NX monorepos.
844006a: Support additional path syntax,
/:path(a|b|c),/:path((?!a|b|c).\*), and/some-:hash.js844006a: Fix the next/server import to avoid potential import issues for peer dependencies.
844006a: Disallow deprecated fields in microfrontends config by default.
844006a: Improvements/fixes to local development proxy.
844006a: Add
supportPagesRouteroption that corrects/\_next/datarequests to the correct child for Next.js Pages Router.
1.0.0
14 Feb 2025- Breaking
Initial public release
Add back Vercel specific rewrites in local package for preview and local development without the proxy
Add back next config rewrites to deployed apps
- 0.20.x
0.20.0
13 Feb 2025- 0.19.x
- 0.18.x
0.18.0
5 Feb 2025- 0.17.x
- 0.16.x
0.16.0
24 Jan 2025- 0.15.x
0.15.0
22 Jan 2025- 0.14.x
0.14.0
17 Jan 2025- 0.13.x
0.13.0
18 Dec 2024- 0.12.x
0.12.1
17 Dec 2024
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.