Multi-app support

[danielroe]

Tasks

Beta Give feedback

1. namespace access to useNuxtApp('app-name') - probably defaulting to buildID
2. move global variables into namespace and add compatibility layer for users not using multi-app (Remove window.__NUXT__ #25336)
3. investigate dev-time multi-app support
4. add module federation demo/fixture to monorepo
5. investigate nitro integration for deployment/orchestration
6. add nuxt 'host' support for coordinating 'child' apps, components, or other code that needs to run in a nuxt context

[jeantil]

As far as I understand this feature is the only hope to have full microfrontend support.

• Layers imply build time dependencies
• vite-federation-plugin can import bits of a nuxt app but the scoped css support is broken making it difficult/impossible to use for larger projects wich are the ones that benefit most of micro-frontend.

The best we could come up with for our migration from pure vue 3 apps to nuxt is to use iframes which has practical limits.

[localusercamp]

I hope this will be a great opportunity to easily scaffold a DDD application.

[BusinessOfTechnology]

Is this app as in the concept of App in Vue, or apps like plugin apps on a CMS?

[OlaAlsaker]

Is this app as in the concept of App in Vue, or apps like plugin apps on a CMS?

As I understand it, the multi-app feature is designed for combining multiple Nuxt apps on a single page. In large applications, different teams often work on different parts of the same app. Instead of each team working on the same Nuxt app, they can work on their own app, and Nuxt can automatically merge these apps together.

It's kind of like microservices, but for the frontend – micro frontends 🚀

[jeantil]

The blog post for 3.11 says 3.11 is the last before nuxt 4. for which a first release is expected 2024-Q1 according to the roadmap.

Does it mean Nuxt 3.x will never have multi application support ?
if 3.x never gets it, is multi-app support something of a goal for nuxt 4 ?

[danielroe]

Features aim to land in minor releases. Breaking changes in major ones. Our feature roadmap + plans isn't really affected by our v4 plans; v4 is just an opportunity to make strategic (and gentle) breaking changes.

[nicolaspayot]

@danielroe I'd like to give a try on the first task: namespace access to useNuxtApp('app-name')

[danielroe]

@nicolaspayot Great! 🎉

[aekovalev]

@danielroe Daniel, hello! Is there any information about the appearance of support for microfrontends in nuxt out of the box? When will this happen? after the release of nuxt v4? And will there be support for server-side microfrontends in ssr: true mode?

[danielroe]

It's in active development. 😊

[odranoelBR]

N-Layers, Best nuxt feature =). Tks for the work!

[cheindl]

That ist really great news to hear! But i wonder which of the following scenarios will multi-app nuxt support?

1. Multiple instances of different nuxt apps included within one page
2. Multiple instances of the same nuxt app within one page (e.g. bundled as custom-element, with different initial app states)

Are both planned to be supported?

[nicolaspayot]

In order to continue on this topic, I'd like to work on this issue #25336 (remove window.__NUXT__). @manniL happy to sync with you on this if needed.

@danielroe should we update the tasks list with it?

[fredimitchel]

I would raise a concern during usage of layers: how to manage versions of shared dependencies and not overcomplicating their management by duplicating versions on each packages (layers/consumers/shared)?
My dependabot suggests new version but breaks every time the project because version deduping versions are made by pnpm. Any solution for today or it's something we could see in future?