Independent adapter for vite

[wojtask9]

Curently I'm exploring NF with other frameworks than angular.

After recent changes It looks like this coluld be framework agnistic.

I have already working version with vue (bit hacky but its works).

Can you give me some advice what I need to support NF in vite (vite8 + rolldown)

[Aukevanoost]

For sure!

We've actually been working on an ESbuild adapter, what you can do is take that one as example. Remove the ESBuild adapter and change it for your Vite-specific settings: https://github.com/native-federation/esbuild-adapter.

Here are some things to keep in mind:

• We are trying to keep the folder structure 'the same' everywhere so that it is easy to switch between repo's
• Imho, you don't need NX for this, it can be handy but might not always help.
• The new "adapter" architecture supports rebuilds. Therefore, make sure your "build" implementation is idempotent and do setup in the "setup" function. [1]
• We are distinguishing the builds into 2 types: "mapping-and-exposed" (the source code) and "node-modules". You can see the difference using the property "isMappingOrExposed" [2]
• As said before, the new adapter now consists of 3 steps: setup, build and dispose. That means that you also need to build a small map of the active builds (node-modules could have multiple, there is only one exposed-or-mappings). We keep track of them for rebuilds [3]. So don't forget to implement a disposal method in the adapter!

Here are some ideas for rebuilds

• We haven't got the time to do this yet, but Angular is using "watch-pack" to watch filechanges [4], if vite doesnt support this out of the box it might be worth to build this feature in NF for HMR.
• We built an rebuildqueue and are wrapping the rebuild logic in a track function [5] which might help you with sequential rebuilds without the issue of race conditions. This might be a bit advanced for now but could help.

If you have any further questions or need me to look at something, let me know!