Packages

@vercel/microfrontends

2.4.2 · 20 Oct 20261.8M / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/microfrontends From 1.3.0 to 2.4.2

23 releases in betweennotes for 22

Reading releases, release notes and advisories…

Other targets from 1.3.0Newest 1.x1.5.0
  1. 1.3.0yours
  2. 4 releases
  3. 2.0.0major
  4. 2 releases
  5. 2.1.1security
  6. 14 releases
  7. 2.4.2target
1+
change to make
0
advisories fixed
13+
new
19+
fixes

Counted from 22 of 23 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking2.0.0

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.

    2.1.1

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.

  7. 2.3.3

    19 May 20262 fixes
    • Fixed

      Convert file level JSDoc to a regular block comment in schema types to prevent OpenAPI generators from incorrectly associating it with the Config interface 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.

  8. 2.3.2

    30 Mar 20262 fixes
    • Fixed

      Update local proxy to use VERCEL_AUTOMATION_BYPASS_SECRET for bypassing deployment protection on fallback deployments. This is the preferred approach now that multiple automation bypasses are supported. The per-app AUTOMATION_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 Config interface declaration.

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.