Packages

@vercel/microfrontends

2.4.2 · 20 Oct 20261.8M / weekRepositoryHomepagenpmAtom feed

Your version

1.2.0

9 Apr 2025Where it was published

1.5.0 is the newest release of 1.x.

In short

1 new

Release note

The section about @vercel/microfrontends of a note shared by several packages.

Minor Changes

  • Improved 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. The fromApp parameter to your call to runMicrofrontendsMiddleware (in your middleware.ts file) is gone! Please delete the parameter.

    • Your code will fail to compile until you delete the parameter.

    1. The development.localPort field in each application in your microfrontends.json file is renamed to development.local. All you need to do is delete Port from the field name and it will continue working exactly as before!

    • The new field has improved support where you can add a full protocol/host/port if you need (for example, https://my.localhost.me:8080), but works the same as before if you just specify a port.

    1. If the application name in your microfrontends.json matches the Vercel project name, the projectId field is no longer required, please remove it! We would like to deprecate the projectId field in the future. If you have any concerns, please reach out.

    • projectId is annoying to set up so we hope this simplifies things!

    • The Vercel project name should ideally match the application's package.json name. If this is not the case, you will need to set the packageName field to the name from the package.json file. This is needed for the local development proxy to work.

    • Visit vercel.com/docs/microfrontends/troubleshooting for test utilities to validate the microfrontends setup for your application.
      If you have any issues with these changes, please reach out! We are here to help.

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.