single-spa

The router for easy microfrontends (by single-spa)

Single-spa Alternatives

Similar projects and alternatives to single-spa

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better single-spa alternative or higher similarity.

single-spa reviews and mentions

Posts with mentions or reviews of single-spa. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-03-13.
  • Micro frontend frameworks in 2024
    6 projects | dev.to | 13 Mar 2024
    Single-SPA Framework - One of the most popular choices. It has a large community behind it and offers robust routing and lifecycle management for microapps. Ref - https://single-spa.js.org/
  • ⏰ It’s time to talk about Import Map, Micro Frontend, and Nx Monorepo
    9 projects | dev.to | 11 Mar 2024
    Joel Denning is the visionary behind single-spa, boasting profound insights into the true mechanics of the web and is, in my view, a pioneer in micro frontend architecture. I highly recommend checking the single-spa website and his YouTube channel. While the videos might appear dated at first glance, rest assured, Joel is ahead of his time, and the content remains incredibly relevant today.
  • Single-SPA and Svelte advices.
    1 project | /r/sveltejs | 10 Dec 2023
    You got me curious and I found that single spa is something new to me - if I read https://github.com/single-spa/single-spa then I reckon you can use Svelte(Kit) in such framework - like you can use angular etc
  • Speed Run de MicroFrontends com Single-SPA (any%)
    3 projects | dev.to | 24 Nov 2023
  • Use web components for what they’re good at
    8 projects | news.ycombinator.com | 23 Aug 2023
    I’ve actually done that “web components as the interoperability layer”!

    It was this old angular 1.8 app with new features being written in angular-hybrid-ized angular 8. Ripping out angular-hybrid and separating the angular 1.8 routes from the modern angular routes was difficult, but now they were totally separate.

    The only thing linking them together was an object with some RXJS streams in it for state, and a little in-house wrapper “app” who just loaded one component or another depending on the URL and a hash of routes for config. (I’d probably use SingleSPA [1] now. Same thing really.)

    We could deploy them separately since the build just ends up being another JS file somewhere that just gets included with a script tag at runtime. No version bumping! No big mega build!

    We started replacing the remaining “old” routes 1 by 1 with a “new” counter part. That was the easiest part, and went at a pace devs were comfortable with (fast enough) and business folk could tolerate. (modular enough to not HAVE to be done all at once)

    Last I checked, the angular 1.8 stuff is gone years ago. :)

    [1] https://single-spa.js.org/

  • Micro-frontend with Module Federations [Part 1] - Vite
    2 projects | dev.to | 14 Jun 2023
    Module Federation is not the unique solution, for example single-spa
  • Vue 2 EOL
    1 project | /r/vuejs | 30 May 2023
    You may want to look into using single-spa to run Vue 2 and Vue 3 side by side while you're migrating. Once your app is fully converted, you can stop using single-spa
  • Angular et micro front-end : conseils et à la recherche d'un bon tuto
    3 projects | /r/programmation | 25 May 2023
  • Building a Large Scale Micro-frontend Application.
    2 projects | dev.to | 3 Apr 2023
    Single-SPA and module federation are potent tools for building scalable micro-frontends. Single-spa provides a framework for building a modular front-end application. It allows lazy loading of micro-frontends, which helps improve the application's performance. In contrast, module federation enables communication and dependency sharing between different micro-frontends. It reduces code duplication, which can help with scaling an application.
  • How to split an Angular app into micro-frontend apps
    5 projects | dev.to | 27 Mar 2023
    Since micro-frontend allows us to develop applications individually, this also means you can use different frameworks and libraries together to develop each section of this application. Of course, this will have some advantages and disadvantages. If you are using different technologies to serve different parts of the application, it won't be so easy to move developers within teams. However, the door is open, and if you want to do something like that, you could use something like Single SPA, or some other, to help you organize and connect the different technologies into a larger application.
  • A note from our sponsor - SurveyJS
    surveyjs.io | 24 Apr 2024
    With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js. Learn more →

Stats

Basic single-spa repo stats
48
13,017
6.3
7 days ago

single-spa/single-spa is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.

The primary programming language of single-spa is JavaScript.


Sponsored
The modern identity platform for B2B SaaS
The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
workos.com