piral

I thought this one might be about microfrontends. It was not... We are currently working on a solution for this problem (scalable SPA where multiple teams can develop and deploy independently). Its been used by some of our clients for quite a bit now. Their dev teams seem to like it so far. If anyone is interested our GitHub repo is at https://github.com/smapiot/piral - thanks!

As your average developer who's heard architects mention these micro-frontends, I would have liked the article to start off by listing the use cases and trade-offs instead of jumping right on the hype train at full speed. Since the article mentions Piral, I thought I would peruse that project's documentation (0), but am none the wiser on basic questions like: how do components get assembled into the main application, is network traffic overhead is going to be a problem, etc. Delving further into the Piral docs, I came across a link to a sample micro-frontend (1) that seems to be importing every micro-frontend into the index, so network traffic overhead seems like it could be an issue. Does anyone here have experience with these in a production environment and know how to avoid (in my mind) basic pitfalls like these? As it stands, this art

We use Parcel in our Microfrontend Framework Piral (https://github.com/smapiot/piral), too. Overall, this was an awesome decision. In the past we used Webpack a lot, but it just does not feel right any more. I've also written a small article comparing different options: https://blog.bitsrc.io/choosing-the-right-javascript-bundler...

I think there are multiple solutions out there. Our solution is called Piral, https://github.com/smapiot/piral, however, we do not believe that mixing technologies should be a solution - it's rather a workaround (which we also support). The real deal from our point of view is in independent development, deployment, and modular, decoupled thinking.

I appreciate the trend to break the frontend monolith - I think its one of the next steps for grand scale web apps. However, that noted this is certainly not for everyone and it has some downsides (e.g., complexity) that need to be tackled. Right now there is also some lack on tooling and framework / library side. Nevertheless, there are some approaches already. A project currently in the making is Piral (https://piral.io). It is not production ready at this point, but I think it may hit some sweep spot depending on your requirements (see https://github.com/smapiot/piral/blob/master/docs/features.m... for features and comparison to other / similar frameworks for micro frontends). Disclaimer: I'm one of the authors.