Enable javascript in your browser for better experience. Need to know to enable it? Go here.
Last updated : Oct 28, 2020
Not on the current edition
This blip is not on the current edition of the Radar. If it was on one of the last few editions it is likely that it is still relevant. If the blip is older it might no longer be relevant and our assessment might be different today. Unfortunately, we simply don't have the bandwidth to continuously review blips from previous editions of the Radar Understand more
Oct 2020
试验 ? 值得一试。了解为何要构建这一能力是很重要的。企业应当在风险可控的前提下在项目中尝试应用此项技术。

single-spa是个 JavaScript 框架,它把多个微前端集成为一个前端应用。虽然我们告诫提防微前端混乱,借口使用微前端来混合和匹配多个框架,但 single-spa 恰恰干的就是这个。我们明白存在一些正当的场景,比如在有必要集成多个框架时,你需要升级多个微前端中某个框架到新版本。single-spa 一直是我们团队在集成微前端时的默认框架选择,他们发现它可以跟 SystemJS 工作得很好,并且能管理单个依赖的不同版本。

Nov 2017
评估 ? 在了解它将对你的企业产生什么影响的前提下值得探索

single-spa is a JavaScript metaframework that allows us to build micro frontends using different frameworks that can coexist in a single application. In general, we don't recommend using more than one framework for an application, but there are times when we can't avoid doing so. For instance, single-spa can be quite useful when you're working with a legacy application and you want to experiment by developing a new feature, with either a new version of the existing framework or a completely different one. Given the short life span of many JavaScript frameworks, we see a need for a solution that would allow for future framework changes and localized experimentation, without affecting the entire application. single-spa seems to be a good start in that direction.

已发布 : Nov 30, 2017


English | Español | Português | 中文