Deploying to gh-pages from @ 7c090a4 🚀

assets/404.html-W3ROBeu3.js → assets/404.html-nQDSHalp.js

@@ -1 +1 @@
-import{_ as e,o as c,c as t}from"./app-Js4EkCke.js";const _={};function o(r,n){return c(),t("div")}const a=e(_,[["render",o],["__file","404.html.vue"]]);export{a as default};
+import{_ as e,o as c,c as t}from"./app-eF4imkDp.js";const _={};function o(r,n){return c(),t("div")}const a=e(_,[["render",o],["__file","404.html.vue"]]);export{a as default};

assets/SearchBox-n8n3yupc.js → assets/SearchBox-H-obxIh1.js

@@ -1,4 +1,4 @@
-import{g as w,j as y,k as O,f as M,t as N,l as L,m as S,_ as I,o as m,c as d,p as z,v as T,d as f,n as _,q as x,F as C,s as k,x as R,y as b,z as F}from"./app-Js4EkCke.js";const B=[{path:"/",title:"",pathLocale:"/",contents:[]},{path:"/zh/",title:"",pathLocale:"/",contents:[{header:"微前端",slug:"微前端",content:`微前端的概念是由ThoughtWorks在2016年提出的，它借鉴了微服务的架构理念，核心在于将一个庞大的前端应用拆分成多个独立灵活的小型应用，每个应用都可以独立开发、独立运行、独立部署，再将这些小型应用融合为一个完整的应用，或者将原本运行已久、没有关联的几个应用融合为一个应用。微前端既可以将多个项目融合为一，又可以减少项目之间的耦合，提升项目扩展性，相比一整块的前端仓库，微前端架构下的前端仓库倾向于更小更灵活。
+import{g as w,j as y,k as O,f as M,t as N,l as L,m as S,_ as I,o as m,c as d,p as z,v as T,d as f,n as _,q as x,F as C,s as k,x as R,y as b,z as F}from"./app-eF4imkDp.js";const B=[{path:"/",title:"",pathLocale:"/",contents:[]},{path:"/zh/",title:"",pathLocale:"/",contents:[{header:"微前端",slug:"微前端",content:`微前端的概念是由ThoughtWorks在2016年提出的，它借鉴了微服务的架构理念，核心在于将一个庞大的前端应用拆分成多个独立灵活的小型应用，每个应用都可以独立开发、独立运行、独立部署，再将这些小型应用融合为一个完整的应用，或者将原本运行已久、没有关联的几个应用融合为一个应用。微前端既可以将多个项目融合为一，又可以减少项目之间的耦合，提升项目扩展性，相比一整块的前端仓库，微前端架构下的前端仓库倾向于更小更灵活。
 它主要解决了两个问题： 1、随着项目迭代应用越来越庞大，难以维护。
 2、跨团队或跨部门协作开发项目导致效率低下的问题。`},{header:"关于micro-app",slug:"关于micro-app",content:`在micro-app之前，业内已经有一些开源的微前端框架，比较流行的有2个：single-spa和qiankun。
 single-spa是通过监听 url change 事件，在路由变化时匹配到渲染的子应用并进行渲染，这个思路也是目前实现微前端的主流方式。同时single-spa要求子应用修改渲染逻辑并暴露出三个方法：bootstrap、mount、unmount，分别对应初始化、渲染和卸载，这也导致子应用需要对入口文件进行修改。因为qiankun是基于single-spa进行封装，所以这些特点也被qiankun继承下来，并且需要对webpack配置进行一些修改。