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:

how API client automation can save you hours in development

How API client automation can save you hours in development

Learn how OpenAPI can automate API client generation to save time, reduce bugs, and streamline how your frontend app talks to backend APIs.

Lewis Cianci
Jul 1, 2025 â‹… 7 min read
Interface Segregation Principle

SOLID series: Understanding the Interface Segregation Principle (ISP)

Discover how the Interface Segregation Principle (ISP) keeps your code lean, modular, and maintainable using real-world analogies and practical examples.

Oyinkansola Awosan
Jun 30, 2025 â‹… 7 min read
​​How HTML’s Selectedcontent Element Improves Dropdowns

​​How HTML’s <selectedcontent> element improves dropdowns

is an experimental HTML element that gives developers control over how a selected option is displayed, using just HTML and CSS.

Temitope Oyedele
Jun 27, 2025 â‹… 6 min read
advanced caching in Node.js with Valkey

How to get faster data access in Node.js with Valkey

Learn how to implement an advanced caching layer in a Node.js app using Valkey, a high-performance, Redis-compatible in-memory datastore.

Muhammed Ali
Jun 27, 2025 â‹… 7 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