@vercel/microfrontends
2.4.2 · 20 Oct 20261.8M / weekRepositoryHomepagenpmAtom feed
Where each line stands
Plan an upgradeLatest releases
All 55 releases- 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.
Dependency tracking
Know when your own dependencies move
@vercel/microfrontends published 12 releases in the last 12 months. inlinr folds the routine ones into a line and keeps the few that need you.
Advisories reach you
An email when a critical or high advisory affects a project, before the next install.
Upgrades checked first
Peer ranges, Node, ESM-only and types changes read before you bump.
Only what matters
Majors and breaking notes stay; patches and sibling bumps fold into one line.
Reading releases, release notes and advisories…
Registry facts last checked 20 Nov 2026. Releases and advisories last read 20 Nov 2026.
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.