Do we have any idea by how much such apps is heavier than a monolith one?
One "benefit" of a monolith is its weight: you have one version of each library, of framework, stylings, scripts, etc.
Thank you! One of the things that's possible to do with single-spa is to use shared versions of the libraries. So in the article you'll note that I'm using a shared version of react, react-dom, and single-spa. You can find this in the import map in the "Creating an Import Map for Production" section of the article.
So yes, it's absolutely possible to not have a bloated app! Because you're right, you wouldn't want 5 copies of the React library being downloaded. You can have just one, just like you would in a monolith.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Really nice and complete article! Nice work! :D
Do we have any idea by how much such apps is heavier than a monolith one?
One "benefit" of a monolith is its weight: you have one version of each library, of framework, stylings, scripts, etc.
I will definitely try this soon :)
According to the documentation, there should be no significant performance penalty:
single-spa.js.org/docs/faq/#what-i...
Yep! Exactly right.
Thank you! One of the things that's possible to do with single-spa is to use shared versions of the libraries. So in the article you'll note that I'm using a shared version of
react,react-dom, andsingle-spa. You can find this in the import map in the "Creating an Import Map for Production" section of the article.So yes, it's absolutely possible to not have a bloated app! Because you're right, you wouldn't want 5 copies of the React library being downloaded. You can have just one, just like you would in a monolith.