Vite plugin for Module Federation
Reason why 🤔
Microservices nowadays is a well-known concept and maybe you are using it in your current company.
Do you know that now you can apply similar ideas on the Frontend?
With Module Federation you can load separately compiled and deployed code into a unique application.
This plugin makes Module Federation work together with Vite.
Working implementations
Getting started 🚀
https://module-federation.io/guide/basic/webpack.html
import { defineConfig } from 'vite';
import vue from '@vitejs/plugin-vue';
import { federation } from 'module-federation-vite';
import topLevelAwait from 'vite-plugin-top-level-await';
export default defineConfig({
plugins: [
federation({
name: 'bbc',
remotes: {
mfapp01: 'mfapp01@https://unpkg.com/mf-app-01@1.0.9/dist/remoteEntry.js',
remote2: 'mfapp02@https://unpkg.com/mf-app-02/dist/remoteEntry.js',
remote3:
'remote1@https://unpkg.com/react-manifest-example_remote1@1.0.6/dist/mf-manifest.json',
},
exposes: {
App: './src/App.vue',
},
filename: 'dd/remoteEntry.js',
shared: {
vue: {},
react: {
requiredVersion: '18',
},
},
}),
],
server: {
port: 5173,
origin: "http://localhost:5173"
},
build: {
target: 'chrome89',
},
});
roadmap
- feat: generate mf-manifest.json
- feat: support chrome plugin
- ✅
feat: support runtime plugins
- feat: download remote d.ts
- feat: generate d.ts
- feat: support @vitejs/plugin-legacy
- feat: Another plugin, when only some remote modules are started, automatically completes HMR(#54)
So far so good 🎉
Now you are ready to use Module Federation in Vite!