@vercel/microfrontends
2.4.2 · 20 Oct 20261.8M / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/microfrontends From 2.2.1 to 2.4.2
11 releases in betweenevery note read
Reading releases, release notes and advisories…
Release by release
- Fixed
Reuse the parsed config and compiled path matchers in
runMicrofrontendsMiddlewareacross requests instead of rebuilding them on every request
- Fixed
- Fixed
Print the configured local proxy origin in the startup URL while keeping the localhost proxy target visible.
- Fixed
Avoid Node.js
url.parse()deprecation warnings when routing requests through the local proxy.
- Fixed
- New
Add 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.
- New
- Fixed
Prevent the local development proxy from crashing on mid-stream upstream errors
- Fixed
- Fixed
Preserve absolute URLs in query parameters when the local proxy normalizes request URLs and rewrites redirect Location headers.
- Fixed
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.
- Fixed
- Fixed
Prevent local proxy crashes when upstream errors occur after response headers have already been sent.
- Fixed
- Fixed
Convert file level JSDoc to a regular block comment in schema types to prevent OpenAPI generators from incorrectly associating it with the
Configinterface declaration. - Fixed
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.
- Fixed
- Fixed
Update 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. - Fixed
Convert file-level JSDoc to a regular block comment in schema types to prevent OpenAPI generators from incorrectly associating it with the
Configinterface declaration.
- Fixed
1 internal line (docs, tests, tooling) left out.
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.