Releases: vercel/microfrontends
Releases · vercel/microfrontends
@vercel/microfrontends@2.2.2
Patch Changes
-
5a74aaf: Add environment variable overrides for local development ports, enabling multiple worktrees to run simultaneously:
MFE_APP_PORT: Override the dev server port (e.g., 3331 -> 4000)MFE_LOCAL_PROXY_PORT: Override the local proxy port (e.g., 3024 -> 3025)
Note:
MFE_APP_PORTonly works when a single application is running locally. An error will be thrown if multiple local apps are detected with this variable set.Usage:
MFE_APP_PORT=4000 MFE_LOCAL_PROXY_PORT=3025 pnpm dev
-
e343afa: Remove an error from withMicrofrontends when using Next.js 16 with default Turbopack support.
@vercel/microfrontends@2.2.1
Patch Changes
- d1e7cf7: Improve debug logging when inferring the microfrontends.json configuration when the MFE_DEBUG env var is set.
@vercel/microfrontends@2.2.0
Minor Changes
-
966b2e9: Two improvements to the local development proxy:
- Make routing logging less noisy by default. Logging can be added by setting the
MFE_DEBUGenv var ordebugoption. This information is printed in an info message on dev server startup. - Always route requests to the local proxy when the local development proxy is running through Turborepo. The logic has been simplified. Users who are running the proxy manually can set the
TURBO_TASK_HAS_MFE_PROXYenv var totruewhen running.
In addition, we are deprecating two options in
withMicrofrontendsfor configuring microfrontends:- Deprecate the
configPathoption asVC_MICROFRONTENDS_CONFIG_FILE_NAMEsupersedes it. - Deprecate
isProduction. The application will be treated as non-production if the local turbo proxy is running by detecting theTURBO_TASK_HAS_MFE_PROXYenv var which Turborepo sets totrue.
- Make routing logging less noisy by default. Logging can be added by setting the
@vercel/microfrontends@2.1.3
Patch Changes
- 93506f2: Fix Next.js image optimization locally for any image path
@vercel/microfrontends@2.1.2
Patch Changes
- 0606811: Fix local Next.js Image Optimization
@vercel/microfrontends@2.1.1
Patch Changes
- 96f0ea5:
- Add support for locally overriding to MFE aliases: https://vercel.com/changelog/preview-links-between-microfrontends-projects-now-serve-all-paths
- 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.
@vercel/microfrontends@2.1.0
Minor Changes
- c856a5d:
- Add support for custom
microfrontends.jsonfile names. This enables a single application to be deployed as multiple different vercel projects / microfrontends. - Strip asset prefix from Vercel Firewall rate limit paths. Support Vercel Firewall rate limit requests when they go to a child application.
- Add support for custom
@vercel/microfrontends@2.0.1
Patch Changes
- 8c11bdc:
- Support hyphens and escaped special characters in supported path matching regex https://vercel.com/docs/microfrontends/path-routing#supported-path-expressions
- Improve error message for when local development proxy can't determine the port
- Update local proxy double slash routing behaviour to match the production proxy
@vercel/microfrontends@2.0.0
Check out our Public Beta changelog to learn more about this release.
Major Changes
- This release removes the project name and flag names from being visible to client side code.
- Modify the auto-generated asset prefix to use a hash of the project name instead of the project name itself.
- Allow users to specify a custom asset prefix in
microfrontends.json. - Remove project names and flag names from the Microfrontends client configuration.
Minor Changes
- Use user-provided appName when inferring the location of microfrontends.json.
Patch Changes
- Improve error messages when the name in
package.jsondoes not match the Vercel project name.