2020-11-17
2193
#react
Diogo Souza
29027
Nov 17, 2020 â‹… 7 min read

Creating micro-frontend apps with single-spa

Diogo Souza Brazilian dev. Creator of altaluna.com.br

Recent posts:

i tried kiro and here is what i learned

I tried out Kiro: Here’s what I learned

Check out Kiro, AWS’s AI-powered IDE, see what makes it different from other AI coding tools, and explore whether it lives up to the hype.

Elijah Asaolu
Aug 28, 2025 â‹… 5 min read
Go Design Pattern Article Image With Logo

Why Go design patterns still matter

Here’s how three design patterns solved our Go microservices scaling problems without sacrificing simplicity.

Peter Aideloje
Aug 28, 2025 â‹… 2 min read
how to protect your ai agent from prompt injection attacks

How to protect your AI agent from prompt injection attacks

Explore six principled design patterns (with real-world examples) to help you protect your LLM agents from prompt injection attacks.

Rosario De Chiara
Aug 27, 2025 â‹… 5 min read
Don’t Let AI Erase The Next Generation Of Dev Leaders

Don’t let AI erase the next generation of dev leaders

As AI tools take over more routine coding work, some companies are cutting early-career dev roles — a short-sighted move that could quietly erode the next generation of tech leaders if we aren’t careful.

Jack Herrington
Aug 26, 2025 â‹… 6 min read
View all posts

5 Replies to "Creating micro-frontend apps with single-spa"

  1. Hi Diogo,

    thank you for this example, but it is not working anymore if following this guide step by step.

    Here is the error I am getting when running apps and going to localhost:9000: resolve.js:12 Uncaught (in promise) Error: Unable to resolve bare specifier ‘@LogRocket/root-config’ – screenshot https://prnt.sc/x8eiu5

    I made everything same way as in your example, even the names of the apps and org, just to be sure. Here is my example code – https://github.com/igorbuts/single-spa-test

    What I noticed in my example comparing to yours (from comment above) that all the libraries which name is starting with webpack- differ in major version. Maybe the made some breaking changes….
    Because If I clone your example – it is working.

    When I try in my example to downgrade libs to the versions of your example I get some new errors.

  2. Hey Igor, that’s really weird.

    I’ve cloned your repo and tried to analyze every single file, comparing it with mine, but nothing was different and yet the error persists.

    Then, I’ve created another one from scratch following the same steps in the article and, this time, was ok.

    I guess something has bugged within the Webpack or config files. Please, try it out too. In another folder, redo the process and let me know if that works.

    Cheers.

  3. @Team, Its really a great work you did it. Thanks for the article. I am having one issue in this. Application setup is fine and working. But every navigation it is reloading the page. I don’t want page reloading when we navigate between any routes. Can you please help me to fix this. Please find the attached video for your reference

Leave a Reply