Should i start a mfe using this lib?

[rogersdk]

I’ve been asked to transform a frontend monolith built with Vite, React, and TypeScript into a microfrontend application. As someone new to microfrontend architecture, I’ve spent several days researching alternatives and came across a library that closely matches our current setup.

The monolithic application is currently in production and running well. However, the main module team is struggling to integrate additional modules due to the large codebase and multiple teams contributing changes through substantial merge requests. Given this situation, I started exploring alternatives and decided to take initiative in finding a solution.

I’ve reviewed the single-spa documentation, but it seems to lack proper integration examples or guidance for working with Vite.

Any help, advice, or pointers would be greatly appreciated.

[webJose]

Hello. I created this plug-in to replace an in-house MFE solution in React in order to accommodate Svelte. It works pretty much flawlessly. Through the course of its lifetime, there's barely any issues reported and currently oscillates between 6 and 8.000 weekly downloads. So to answer your question, yes, I would use it, confidently, I might add.

The only downside is the underlying technology: single-spa. Taking my personal problem with the creator aside, you can see that its creator is pretty much fed up with open source. She doesn't want to maintain it anymore for free, and has explicitly advertised her fee of $250/hr (charged by the minute) to address issues and feature requests. On top of this, she's not quick at all in accepting contributions.

However, as it is right now, single-spa is both solid and simple to use, especially if you compare them to other solutions like Piral.

I have been cooking (slowly, unfortunately), a new MFE library inspired by single-spa parcels. The idea is basically have only parcels and no routers. Why no routers? Because it is impossible to please everyone. "Bring your own router" is going to be its motto, hehe.

Having said that, I have already created a Svelte-powered router that is fast (mounted on Svelte v5's reactivity system, which ranks top 10) and slim (about 1100 lines of code) which can be used as a master router, if you are also in the lookout for a router: @wjfe/n-savant.

I am unsure if this helps, as your question is quite open to interpretation.

[rogersdk]

Thanks for the extra context beyond the README, that really helped clear things up. Do you happen to have a working example using the library? I tried this morning with my current projects, and I think I might have done a few things wrong or misconfigured.

[webJose]

Have you read the blog that describes my investigation and the progression of this plug-in? It will probably clear things up for you: Single-SPA & Svelte

[webJose]

As for a working example or repo: I don't think I have one. I'll check it out. Have you checked this repository's dependencies? There should be a public example somewhere that works for you: https://github.com/WJSoftware/vite-plugin-single-spa/network/dependents

As of today, 146 dependants exist.

[rogersdk]

I haven’t had check the blog, but I’ll go through it. Feel free to close the discussion, i’m pretty sure the information provided was more than enough.
Thanks for the help!

[webJose]

NP. Feel free to reopen or create new discussions. I have distanced myself from the single-spa community, but I wouldn't mind answer questions here and there. Worst thing that can happen is that I refuse help, but don't take it personally because it won't be.