In Chinese traditional culture
qianmeans heaven and
kunstands for earth, so
qiankunis the universe.
As we know what micro-frontends aims for:
Modularity is very important for large application. By breaking down a large system into individual sub-applications, we can achieve good divide-and-conquer between products and when necessary combination, especially for enterprise applications that usually involve multi-team collaboration. But if you're trying to implement such a micro frontends architecture system by yourself, you're likely to run into some tricky problems:
- In what form do subapplications publish static resources?
- How does the main application integrate individual sub-applications?
- How do you ensure that sub-applications are independent of each other (development independent, deployment independent) and runtime isolated?
- Performance issues? What about public dependencies?
- And so on...
After solving these common problems of micro frontends, we extracted the kernel of our solution after a lot of internal online application testing and polishing, and then named it
Probably the most complete micro-frontends solution you ever met🧐.
$ yarn add qiankun # or npm i qiankun -S
$yarn $yarn install:examples $yarn start
📦Based On single-spa
- 🦾 HTML Entry Access Mode
- 🧳 JS Sandbox
- ⚡ Prefetch Assets
🔌Umi Plugin Integration
- Parcel apps integration (multiple sub apps displayed at the same time, but only one uses router at most)
- Communication development kits between master and sub apps
- Custom side effects hijacker
- Nested Microfrontends