Packages

@vercel/microfrontends

2.4.2 · 20 Oct 20261.8M / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/microfrontends From 2.3.3 to 2.4.2

6 releases in betweenevery note read

Reading releases, release notes and advisories…

0
changes to make
0
advisories fixed
1
new
7
fixes

Release by release

  1. 2.4.2

    20 Oct 20261 fix
    • Fixed

      Reuse the parsed config and compiled path matchers in runMicrofrontendsMiddleware across requests instead of rebuilding them on every request

  2. 2.4.1

    12 Oct 20262 fixes
    • 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.

  3. 2.4.0

    7 Jul 20261 new
    • New

      Add an optional configured origin to the local development proxy via --origin <origin> or the MFE_LOCAL_PROXY_ORIGIN environment variable (for example https://web.localhost). When set, the proxy forwards that origin to your applications as x-forwarded-proto/x-forwarded-host/x-forwarded-port and 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.

  4. 2.3.6

    4 Jun 20261 fix
    • Fixed

      Prevent the local development proxy from crashing on mid-stream upstream errors

  5. 2.3.5

    2 Jun 20262 fixes
    • 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.

  6. 2.3.4

    26 May 20261 fix
    • Fixed

      Prevent local proxy crashes when upstream errors occur after response headers have already been sent.

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.