Hi José Pablo Ramírez Vargas ! No, it's just a normal utility project and was created via create-single-spa --moduleType util-module. But when I try to bundle it with vite, this MFE is not found... In the webpack.config.js, what does the singleSpaDefaults do? Must I follow some kind of pattern in vite, to replace it properly or bundle my project in a single-SPA way?

Hi @ José Pablo Ramírez Vargas ! Does your vite plugin provide the possibility of bundle an utility module? I'm asking, because your type property only provides 'root' and 'mifi'.

Hello José Pablo Ramírez Vargas . During my own journey with single-spa I came across your articles. Thank you for your work and effort to bring vite into single-spa. In connection with the "standalone" version of the "mife", I stumbled upon a problem that I have not yet been able to solve. What would be the approach if you import a utility module in a "mife". The problem I have is that the import maps for the mife type cannot be set in the plugin and I have not yet figured out how to tell the mife to import this external dependency at runtime. If I use Webpack, I can import the module manually afterwards using the button (bottom right by default). Have I overlooked something obvious? I would be very happy if someone would share their thoughts or suggestions with me. If I get this point solved, then I can switch everything to vite. Happy Easter to all