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:

Exploring Advanced Support For Vite 5 In Storybook 8

Exploring advanced support for Vite 5 in Storybook 8

Explore the latest updates in Storybook 8, focusing on its improved support for Vite 5 as a build tool.

Will Soares
Jun 20, 2024 ⋅ 5 min read
Exploring Angular 18's Redirectcommand Class And Let Block

Exploring Angular 18’s RedirectCommand class and @let block

Angular’s latest update brings greater control over redirects and the ability to define and assign variables within the template.

Lewis Cianci
Jun 19, 2024 ⋅ 6 min read
Showing Progress For Page Transitions In Next Js

Showing progress for page transitions in Next.js

Progress bars help create a smooth UX during page transitions in your Next.js app, informing users that their request is processing.

Elijah Agbonze
Jun 19, 2024 ⋅ 9 min read
Qwik Adoption Guide Overview Examples And Alternatives

Qwik adoption guide: Overview, examples, and alternatives

Qwik’s focus on performance, innovative features, and commitment to DX make it a fantastic choice for building high-performance web apps.

Fimber Elemuwa
Jun 18, 2024 ⋅ 10 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