[{"data":1,"prerenderedAt":898},["ShallowReactive",2],{"content:\u002Fposts\u002F2025\u002Fhow-to-structure-vue-projects":3,"surround:\u002Fposts\u002F2025\u002Fhow-to-structure-vue-projects":889},{"id":4,"title":5,"body":6,"canonical":19,"categories":857,"date":859,"description":860,"draft":861,"extension":862,"image":863,"meta":864,"navigation":868,"path":869,"permalink":870,"readingTime":871,"recommend":870,"references":870,"seo":876,"sitemap":877,"stem":884,"tags":885,"type":870,"updated":887,"__hash__":888},"content\u002Fposts\u002F2025\u002Fhow-to-structure-vue-projects.md","【翻译】如何选择 Vue 项目架构",{"type":7,"value":8,"toc":810},"minimark",[9,23,26,30,33,69,72,79,85,88,95,98,100,104,107,117,121,166,168,172,177,184,187,219,222,228,231,274,299,301,305,312,318,322,325,331,334,366,368,372,375,380,383,426,432,435,471,487,489,493,499,504,507,521,524,560,566,569,574,577,580,583,668,670,673,676,679,682,687,695,699,705,708,711,714,720,723,729,732,735,738,744,747,753,756,759,763,769,773,779,782],[10,11,12],"auths-alex",{},[13,14,15,16],"p",{},"原文地址：",[17,18,22],"a",{"href":19,"rel":20},"https:\u002F\u002Falexop.dev\u002Fposts\u002Fhow-to-structure-vue-projects\u002F",[21],"nofollow","How to Structure Vue Projects",[24,25],"hr",{},[27,28,29],"h2",{"id":29},"快速总结",[13,31,32],{},"这篇文章涵盖了适合不同项目规模的各种 Vue 项目架构：",[34,35,36,44,50,56,63],"ul",{},[37,38,39,40],"li",{},"适用于小型项目的",[41,42,43],"strong",{},"扁平结构",[37,45,46,47],{},"适用于可扩展应用的",[41,48,49],{},"原子设计",[37,51,52,53],{},"适用于大型项目的",[41,54,55],{},"模块化方法",[37,57,58,59,62],{},"适用于复杂应用的",[41,60,61],{},"功能切片设计","(Feature Sliced Design)",[37,64,65,66],{},"企业级解决方案的",[41,67,68],{},"微前端方案",[27,70,71],{"id":71},"介绍",[13,73,74,75,78],{},"在开始一个 Vue 项目时，你要做出的最关键的决定之一就是如何选择架构。正确的架构可以提高团队内部的可扩展性、可维护性和协作性。这种考虑与",[41,76,77],{},"康威定律","一致：",[80,81,82],"blockquote",{},[13,83,84],{},"“设计系统的组织被迫生产出复制这些组织通信结构的设计。” — 梅尔·康威",[13,86,87],{},"从本质上讲，你的 Vue 应用程序的架构将反映你的组织结构，影响你应该如何规划项目的布局。",[13,89,90],{},[91,92],"img",{"alt":93,"src":94},"","https:\u002F\u002Fbitmc.uno\u002Fpicgo\u002F67aeeff3a746b-78.webp",[13,96,97],{},"无论您是构建小型应用程序还是企业级解决方案，本指南都涵盖了适合不同规模和复杂性的各种项目结构。",[24,99],{},[27,101,103],{"id":102},"_1-扁平结构非常适合小型项目","1. 扁平结构：非常适合小型项目",[13,105,106],{},"你是否正在进行一个小规模的 Vue 项目或概念验证？简单、扁平的文件夹结构可能是使事情变得简单并避免不必要的复杂性的最佳选择。",[108,109,114],"pre",{"className":110,"code":112,"language":113,"meta":93},[111],"language-txt","\u002Fsrc\n|-- \u002Fcomponents\n|   |-- BaseButton.vue\n|   |-- BaseCard.vue\n|   |-- PokemonList.vue\n|   |-- PokemonCard.vue\n|-- \u002Fcomposables\n|   |-- usePokemon.js\n|-- \u002Futils\n|   |-- validators.js\n|-- \u002Flayout\n|   |-- DefaultLayout.vue\n|   |-- AdminLayout.vue\n|-- \u002Fplugins\n|   |-- translate.js\n|-- \u002Fviews\n|   |-- Home.vue\n|   |-- PokemonDetail.vue\n|-- \u002Frouter\n|   |-- index.js\n|-- \u002Fstore\n|   |-- index.js\n|-- \u002Fassets\n|   |-- \u002Fimages\n|   |-- \u002Fstyles\n|-- \u002Ftests\n|   |-- ...\n|-- App.vue\n|-- main.js\n","txt",[115,116,112],"code",{"__ignoreMap":93},[118,119,120],"h3",{"id":120},"优点和缺点",[122,123,124,138],"table",{},[125,126,127],"thead",{},[128,129,130,135],"tr",{},[131,132,134],"th",{"align":133},"left","✅ 优点",[131,136,137],{"align":133},"❌ 缺点",[139,140,141,150,158],"tbody",{},[128,142,143,147],{},[144,145,146],"td",{"align":133},"易于实施",[144,148,149],{"align":133},"不可扩展",[128,151,152,155],{},[144,153,154],{"align":133},"最少的设置",[144,156,157],{"align":133},"随着项目的增长而变得杂乱无章",[128,159,160,163],{},[144,161,162],{"align":133},"非常适合小型团队或独立开发人员",[144,164,165],{"align":133},"缺乏明确的关注点分离",[24,167],{},[27,169,171],{"id":170},"_2-原子设计可扩展的组件组织","2. 原子设计：可扩展的组件组织",[13,173,174],{},[91,175],{"alt":93,"src":176},"https:\u002F\u002Fbitmc.uno\u002Fpicgo\u002F67aeee43ba0f2-78.webp",[13,178,179,180,183],{},"对于更大的 Vue 应用程序，",[41,181,182],{},"原子设计(Atomic Design)"," 方法可能是有利的。此方法将组件组织到从最简单到最复杂的层次结构中。",[27,185,186],{"id":186},"原子层次结构",[34,188,189,195,201,207,213],{},[37,190,191,194],{},[41,192,193],{},"原子 Atoms","：基本元素，如按钮和图标。",[37,196,197,200],{},[41,198,199],{},"分子 Molecules","：形成简单组件的原子组（例如，搜索栏）。",[37,202,203,206],{},[41,204,205],{},"生物体 Organisms","：由分子和原子组成的复杂组件（例如导航栏）。",[37,208,209,212],{},[41,210,211],{},"布局 Layout","：构建有机体而没有真实内容的页面布局。",[37,214,215,218],{},[41,216,217],{},"页面 Pages","：模板填充了真实内容以形成实际页面。",[13,220,221],{},"此方法可确保可伸缩性和可维护性，从而促进简单组件和复杂组件之间的平滑过渡。",[108,223,226],{"className":224,"code":225,"language":113,"meta":93},[111],"\u002Fsrc\n|-- \u002Fcomponents\n|   |-- \u002Fatoms\n|   |   |-- AtomButton.vue\n|   |   |-- AtomIcon.vue\n|   |-- \u002Fmolecules\n|   |   |-- MoleculeSearchInput.vue\n|   |   |-- MoleculePokemonThumbnail.vue\n|   |-- \u002Forganisms\n|   |   |-- OrganismPokemonCard.vue\n|   |   |-- OrganismHeader.vue\n|   |-- \u002Ftemplates\n|   |   |-- TemplatePokemonList.vue\n|   |   |-- TemplatePokemonDetail.vue\n|-- \u002Fpages\n|   |-- PageHome.vue\n|   |-- PagePokemonDetail.vue\n|-- \u002Fcomposables\n|   |-- usePokemon.js\n|-- \u002Futils\n|   |-- validators.js\n|-- \u002Flayout\n|   |-- LayoutDefault.vue\n|   |-- LayoutAdmin.vue\n|-- \u002Fplugins\n|   |-- translate.js\n|-- \u002Frouter\n|   |-- index.js\n|-- \u002Fstore\n|   |-- index.js\n|-- \u002Fassets\n|   |-- \u002Fimages\n|   |-- \u002Fstyles\n|-- \u002Ftests\n|   |-- ...\n|-- App.vue\n|-- main.js\n",[115,227,225],{"__ignoreMap":93},[118,229,120],{"id":230},"优点和缺点-1",[122,232,233,241],{},[125,234,235],{},[128,236,237,239],{},[131,238,134],{"align":133},[131,240,137],{"align":133},[139,242,243,251,259,267],{},[128,244,245,248],{},[144,246,247],{"align":133},"高度可扩展",[144,249,250],{"align":133},"可能会在管理层中引入开销",[128,252,253,256],{},[144,254,255],{"align":133},"井然有序的组件层次结构",[144,257,258],{"align":133},"设置的初始复杂性",[128,260,261,264],{},[144,262,263],{"align":133},"可重用组件",[144,265,266],{"align":133},"对于较小的项目来说可能有点矫枉过正",[128,268,269,272],{},[144,270,271],{"align":133},"改善团队之间的协作",[144,273],{"align":133},[275,276,277,283,292],"alert",{},[278,279,280],"template",{"v-slot:title":93},[13,281,282],{},"想了解更多关于 Atomic Design 的信息吗？",[13,284,285,286,291],{},"查看作者关于 ",[17,287,290],{"href":288,"rel":289},"https:\u002F\u002Falexop.dev\u002Fposts\u002Fatomic-design-vue-or-nuxt",[21],"Vue 和 Nuxt 中的 Atomic Design"," 的详细博客文章。或者点击下面的链接查看翻译后的文章。",[293,294],"link-banner",{"banner":295,"description":296,"link":297,"title":298},"https:\u002F\u002Fbitmc.uno\u002Fpicgo\u002F67aef51e90a66-78.webp","清晰的写作需要清晰的思考。对于编码也是有效的。启动个人项目时，将所有组件扔入一个文件夹中可能会起作用。但是随着项目的增长，尤其是在较大的团队中，这种方法会导致问题：","\u002Fposts\u002F2025\u002Fatomic-design-vue-or-nuxt","【翻译】Vue 和 Nuxt 中的 Atomic Design",[24,300],{},[27,302,304],{"id":303},"_3-模块化方法基于功能的组织","3. 模块化方法：基于功能的组织",[13,306,307,308,311],{},"随着项目的扩展，请考虑使用",[41,309,310],{},"模块化整体架构","。此结构封装了每个功能或域，增强了可维护性，并为可能向微服务演变做好准备。",[108,313,316],{"className":314,"code":315,"language":113,"meta":93},[111],"\u002Fsrc\n|-- \u002Fcore\n|   |-- \u002Fcomponents\n|   |   |-- BaseButton.vue\n|   |   |-- BaseIcon.vue\n|   |-- \u002Fmodels\n|   |-- \u002Fstore\n|   |-- \u002Fservices\n|   |-- \u002Fviews\n|   |   |-- DefaultLayout.vue\n|   |   |-- AdminLayout.vue\n|   |-- \u002Futils\n|   |   |-- validators.js\n|-- \u002Fmodules\n|   |-- \u002Fpokemon\n|   |   |-- \u002Fcomponents\n|   |   |   |-- PokemonThumbnail.vue\n|   |   |   |-- PokemonCard.vue\n|   |   |   |-- PokemonListTemplate.vue\n|   |   |   |-- PokemonDetailTemplate.vue\n|   |   |-- \u002Fmodels\n|   |   |-- \u002Fstore\n|   |   |   |-- pokemonStore.js\n|   |   |-- \u002Fservices\n|   |   |-- \u002Fviews\n|   |   |   |-- PokemonDetailPage.vue\n|   |   |-- \u002Ftests\n|   |   |   |-- pokemonTests.spec.js\n|   |-- \u002Fsearch\n|   |   |-- \u002Fcomponents\n|   |   |   |-- SearchInput.vue\n|   |   |-- \u002Fmodels\n|   |   |-- \u002Fstore\n|   |   |   |-- searchStore.js\n|   |   |-- \u002Fservices\n|   |   |-- \u002Fviews\n|   |   |-- \u002Ftests\n|   |   |   |-- searchTests.spec.js\n|-- \u002Fassets\n|   |-- \u002Fimages\n|   |-- \u002Fstyles\n|-- \u002Fscss\n|-- App.vue\n|-- main.ts\n|-- router.ts\n|-- store.ts\n|-- \u002Ftests\n|   |-- ...\n|-- \u002Fplugins\n|   |-- translate.js\n",[115,317,315],{"__ignoreMap":93},[118,319,321],{"id":320},"备选方案简化的扁平化特征结构","备选方案：简化的扁平化特征结构",[13,323,324],{},"大型项目中的一个常见痛点是过多的文件夹嵌套，这会使导航和文件发现更加困难。下面是一个简化的扁平功能结构，它优先考虑 IDE 友好的导航并减少认知负载：",[108,326,329],{"className":327,"code":328,"language":113,"meta":93},[111],"\u002Ffeatures\n|-- \u002Fproject\n|   |-- project.composable.ts\n|   |-- project.data.ts\n|   |-- project.store.ts\n|   |-- project.types.ts\n|   |-- project.utils.ts\n|   |-- project.utils.test.ts\n|   |-- ProjectList.vue\n|   |-- ProjectItem.vue\n",[115,330,328],{"__ignoreMap":93},[13,332,333],{},"这种结构具有以下几个优点：",[34,335,336,342,348,354,360],{},[37,337,338,341],{},[41,339,340],{},"快速导航","：使用“快速打开”（Ctrl\u002FCmd + P） 等 IDE 功能，您可以通过键入“project...”立即找到任何与项目相关的文件。",[37,343,344,347],{},[41,345,346],{},"减少嵌套","：所有与功能相关的文件都位于同一级别，从而消除了较深的文件夹层次结构",[37,349,350,353],{},[41,351,352],{},"清除所有权","：每个文件的用途从其后缀中立即明确",[37,355,356,359],{},[41,357,358],{},"轻松的模式识别","：一致的命名使理解每个文件的作用变得简单",[37,361,362,365],{},[41,363,364],{},"测试共存","：测试位于它们正在测试的代码旁边",[24,367],{},[27,369,371],{"id":370},"_4-功能切片设计适用于复杂的应用","4. 功能切片设计：适用于复杂的应用",[13,373,374],{},"功能切片设计(Feature-Sliced Design) 非常适合大型长期项目。这种方法将应用程序分解为不同的层，每个层都有特定的角色。",[13,376,377],{},[91,378],{"alt":93,"src":379},"https:\u002F\u002Fbitmc.uno\u002Fpicgo\u002F67aeeb6f789d7-78.webp",[118,381,382],{"id":382},"特征切片设计的层次",[34,384,385,391,397,402,408,414,420],{},[37,386,387,390],{},[41,388,389],{},"应用程序 App","：全局设置、样式和提供程序。",[37,392,393,396],{},[41,394,395],{},"过程 Processes","：公用业务流程，如用户身份验证流。",[37,398,399,401],{},[41,400,217],{},"：使用实体、功能和小组件构建的完整页面。",[37,403,404,407],{},[41,405,406],{},"部件 Widgets","：将实体和功能合并到内聚的 UI 块中。",[37,409,410,413],{},[41,411,412],{},"特征 Features","：处理增加价值的用户交互。",[37,415,416,419],{},[41,417,418],{},"实体 Entities","：表示核心业务模型。",[37,421,422,425],{},[41,423,424],{},"共享 Shared","：与特定业务逻辑无关的可重用实用程序和组件。",[108,427,430],{"className":428,"code":429,"language":113,"meta":93},[111],"\u002Fsrc\n|-- \u002Fapp\n|   |-- App.vue\n|   |-- main.js\n|   |-- app.scss\n|-- \u002Fprocesses\n|-- \u002Fpages\n|   |-- Home.vue\n|   |-- PokemonDetailPage.vue\n|-- \u002Fwidgets\n|   |-- UserProfile.vue\n|   |-- PokemonStatsWidget.vue\n|-- \u002Ffeatures\n|   |-- pokemon\n|   |   |-- CatchPokemon.vue\n|   |   |-- PokemonList.vue\n|   |-- user\n|   |   |-- Login.vue\n|   |   |-- Register.vue\n|-- \u002Fentities\n|   |-- user\n|   |   |-- userService.js\n|   |   |-- userModel.js\n|   |-- pokemon\n|   |   |-- pokemonService.js\n|   |   |-- pokemonModel.js\n|-- \u002Fshared\n|   |-- ui\n|   |   |-- BaseButton.vue\n|   |   |-- BaseInput.vue\n|   |   |-- Loader.vue\n|   |-- lib\n|   |   |-- api.js\n|   |   |-- helpers.js\n|-- \u002Fassets\n|   |-- \u002Fimages\n|   |-- \u002Fstyles\n|-- \u002Frouter\n|   |-- index.js\n|-- \u002Fstore\n|   |-- index.js\n|-- \u002Ftests\n|   |-- featureTests.spec.js\n",[115,431,429],{"__ignoreMap":93},[118,433,120],{"id":434},"优点和缺点-2",[122,436,437,445],{},[125,438,439],{},[128,440,441,443],{},[131,442,134],{"align":133},[131,444,137],{"align":133},[139,446,447,455,463],{},[128,448,449,452],{},[144,450,451],{"align":133},"高内聚力和清晰的分离",[144,453,454],{"align":133},"理解层的初始复杂性",[128,456,457,460],{},[144,458,459],{"align":133},"可扩展且可维护",[144,461,462],{"align":133},"需要周密的规划",[128,464,465,468],{},[144,466,467],{"align":133},"促进团队协作",[144,469,470],{"align":133},"需要一致地执行约定",[275,472,473,478],{},[278,474,475],{"v-slot:title":93},[13,476,477],{},"了解有关特征切片设计的更多信息",[13,479,480,481,486],{},"访问",[17,482,485],{"href":483,"rel":484},"https:\u002F\u002Ffeature-sliced.design\u002F",[21],"官方 Feature-Sliced Design 文档","以深入了解。",[24,488],{},[27,490,492],{"id":491},"_5-微前端企业级解决方案","5. 微前端：企业级解决方案",[13,494,495,498],{},[41,496,497],{},"微前端","将微服务的概念带到了前端。不同的团队可以独立处理 Web 应用程序的各个部分，从而实现灵活的开发和部署。",[13,500,501],{},[91,502],{"alt":93,"src":503},"https:\u002F\u002Fbitmc.uno\u002Fpicgo\u002F67aee9ce4f61b-78.webp",[118,505,506],{"id":506},"关键组件",[34,508,509,515],{},[37,510,511,514],{},[41,512,513],{},"应用程序壳","：主控制器处理基本的布局和路由，连接所有微前端。",[37,516,517,520],{},[41,518,519],{},"分解的 UI 和模块","：每个微前端都专注于应用程序的特定部分，并且可以使用不同的技术进行开发。",[118,522,120],{"id":523},"优点和缺点-3",[122,525,526,534],{},[125,527,528],{},[128,529,530,532],{},[131,531,134],{"align":133},[131,533,137],{"align":133},[139,535,536,544,552],{},[128,537,538,541],{},[144,539,540],{"align":133},"独立部署",[144,542,543],{"align":133},"编排中的高复杂性",[128,545,546,549],{},[144,547,548],{"align":133},"大型团队的可扩展性",[144,550,551],{"align":133},"需要强大的基础设施",[128,553,554,557],{},[144,555,556],{"align":133},"与技术无关的方法",[144,558,559],{"align":133},"用户体验中可能存在的不一致",[275,561,563],{"type":562},"warning",[13,564,565],{},"微前端最适合具有多个开发团队的大型复杂项目。这种方法可能会带来很大的复杂性，并且对于中小型应用程序通常不是必需的。",[27,567,568],{"id":568},"结论",[13,570,571],{},[91,572],{"alt":93,"src":573},"https:\u002F\u002Fbitmc.uno\u002Fpicgo\u002F67aee8ae2aa45-78.webp",[13,575,576],{},"选择正确的项目结构取决于项目的大小、复杂性和团队组织。您的团队或项目越复杂，您就越应该致力于促进可扩展性和可维护性的结构。",[13,578,579],{},"您的项目架构应与您的组织一起成长，为未来的发展提供坚实的基础。",[118,581,582],{"id":582},"对比",[122,584,585,601],{},[125,586,587],{},[128,588,589,592,595,598],{},[131,590,591],{"align":133},"方法",[131,593,594],{"align":133},"描述",[131,596,597],{"align":133},"✅优点",[131,599,600],{"align":133},"❌缺点",[139,602,603,615,628,641,655],{},[128,604,605,607,610,612],{},[144,606,43],{"align":133},[144,608,609],{"align":133},"适用于小型项目的简单结构",[144,611,146],{"align":133},[144,613,614],{"align":133},"不可扩展，可能会变得杂乱无章",[128,616,617,619,622,625],{},[144,618,49],{"align":133},[144,620,621],{"align":133},"基于组件的分层结构",[144,623,624],{"align":133},"可扩展、有序、可重用的组件",[144,626,627],{"align":133},"管理层的开销，初始复杂性",[128,629,630,632,635,638],{},[144,631,55],{"align":133},[144,633,634],{"align":133},"基于特征的模块化结构",[144,636,637],{"align":133},"可扩展的封装功能",[144,639,640],{"align":133},"潜在的重复，需要纪律",[128,642,643,646,649,652],{},[144,644,645],{"align":133},"特征切片设计",[144,647,648],{"align":133},"适用于大型项目的功能层和切片",[144,650,651],{"align":133},"高内聚力，分离清晰",[144,653,654],{"align":133},"初始复杂性，需要全面规划",[128,656,657,659,662,665],{},[144,658,497],{"align":133},[144,660,661],{"align":133},"前端组件的独立部署",[144,663,664],{"align":133},"独立部署，可扩展",[144,666,667],{"align":133},"高度复杂，需要团队之间的协调",[24,669],{},[27,671,672],{"id":672},"一般规则和最佳实践",[13,674,675],{},"在结束之前，让我们强调一些可以应用于每种结构的一般规则。这些准则对于保持代码库的一致性和可读性非常重要。",[118,677,678],{"id":678},"基础组件名称",[13,680,681],{},"为您的 UI 组件使用前缀，以将其与其他类型组件区分开来。",[683,684,686],"h4",{"id":685},"bad","Bad",[108,688,693],{"className":689,"code":691,"language":692},[690],"language-text","components\u002F\n|-- MyButton.vue\n|-- VueTable.vue\n|-- Icon.vue\n","text",[115,694,691],{"__ignoreMap":93},[683,696,698],{"id":697},"good","Good",[108,700,703],{"className":701,"code":702,"language":692},[690],"components\u002F\n|-- BaseButton.vue\n|-- BaseTable.vue\n|-- BaseIcon.vue\n",[115,704,702],{"__ignoreMap":93},[118,706,707],{"id":707},"组件名称和功能紧密耦合",[13,709,710],{},"通过和命名紧密耦合的组件，将它们分组在一起。",[683,712,686],{"id":713},"bad-1",[108,715,718],{"className":716,"code":717,"language":692},[690],"components\u002F\n|-- TodoList.vue\n|-- TodoItem.vue\n|-- TodoButton.vue\n",[115,719,717],{"__ignoreMap":93},[683,721,698],{"id":722},"good-1",[108,724,727],{"className":725,"code":726,"language":692},[690],"components\u002F\n|-- TodoList.vue\n|-- TodoListItem.vue\n|-- TodoListItemButton.vue\n",[115,728,726],{"__ignoreMap":93},[118,730,731],{"id":731},"组件名称中的单词顺序",[13,733,734],{},"组件名称应以最高级别的单词开头，并以描述性修饰符结尾。",[683,736,686],{"id":737},"bad-2",[108,739,742],{"className":740,"code":741,"language":692},[690],"components\u002F\n|-- ClearSearchButton.vue\n|-- ExcludeFromSearchInput.vue\n|-- LaunchOnStartupCheckbox.vue\n",[115,743,741],{"__ignoreMap":93},[683,745,698],{"id":746},"good-2",[108,748,751],{"className":749,"code":750,"language":692},[690],"components\u002F\n|-- SearchButtonClear.vue\n|-- SearchInputExclude.vue\n|-- SettingsCheckboxLaunchOnStartup.vue\n",[115,752,750],{"__ignoreMap":93},[118,754,755],{"id":755},"组织测试",[13,757,758],{},"决定是将测试保存在单独的文件夹中，还是与组件一起保存。这两种方法都是有效的，但一致性是关键。",[683,760,762],{"id":761},"方法-1单独的测试文件夹","方法 1：单独的测试文件夹",[108,764,767],{"className":765,"code":766,"language":692},[690],"\u002Fvue-project\n|-- src\n|   |-- components\n|   |   |-- MyComponent.vue\n|   |-- views\n|   |   |-- HomeView.vue\n|-- tests\n|   |-- components\n|   |   |-- MyComponent.spec.js\n|   |-- views\n|   |   |-- HomeView.spec.js\n",[115,768,766],{"__ignoreMap":93},[683,770,772],{"id":771},"方法-2内联测试文件","方法 2：内联测试文件",[108,774,777],{"className":775,"code":776,"language":692},[690],"\u002Fvue-project\n|-- src\n|   |-- components\n|   |   |-- MyComponent.vue\n|   |   |-- MyComponent.spec.js\n|   |-- views\n|   |   |-- HomeView.vue\n|   |   |-- HomeView.spec.js\n",[115,778,776],{"__ignoreMap":93},[27,780,781],{"id":781},"其他资料",[34,783,784,791,798,805],{},[37,785,786],{},[17,787,790],{"href":788,"rel":789},"https:\u002F\u002Fvuejs.org\u002Fstyle-guide\u002F",[21],"官方 Vue.js 风格指南",[37,792,793],{},[17,794,797],{"href":795,"rel":796},"https:\u002F\u002Fmicro-frontends.org\u002F",[21],"微前端 - 将微服务理念扩展到前端开发",[37,799,800],{},[17,801,804],{"href":802,"rel":803},"https:\u002F\u002Fmartinfowler.com\u002Farticles\u002Fmicro-frontends.html",[21],"Martin Fowler 谈 Microfrontends",[37,806,807],{},[17,808,485],{"href":483,"rel":809},[21],{"title":93,"searchDepth":811,"depth":811,"links":812},4,[813,815,816,820,821,824,827,831,835,838,856],{"id":29,"depth":814,"text":29},2,{"id":71,"depth":814,"text":71},{"id":102,"depth":814,"text":103,"children":817},[818],{"id":120,"depth":819,"text":120},3,{"id":170,"depth":814,"text":171},{"id":186,"depth":814,"text":186,"children":822},[823],{"id":230,"depth":819,"text":120},{"id":303,"depth":814,"text":304,"children":825},[826],{"id":320,"depth":819,"text":321},{"id":370,"depth":814,"text":371,"children":828},[829,830],{"id":382,"depth":819,"text":382},{"id":434,"depth":819,"text":120},{"id":491,"depth":814,"text":492,"children":832},[833,834],{"id":506,"depth":819,"text":506},{"id":523,"depth":819,"text":120},{"id":568,"depth":814,"text":568,"children":836},[837],{"id":582,"depth":819,"text":582},{"id":672,"depth":814,"text":672,"children":839},[840,844,848,852],{"id":678,"depth":819,"text":678,"children":841},[842,843],{"id":685,"depth":811,"text":686},{"id":697,"depth":811,"text":698},{"id":707,"depth":819,"text":707,"children":845},[846,847],{"id":713,"depth":811,"text":686},{"id":722,"depth":811,"text":698},{"id":731,"depth":819,"text":731,"children":849},[850,851],{"id":737,"depth":811,"text":686},{"id":746,"depth":811,"text":698},{"id":755,"depth":819,"text":755,"children":853},[854,855],{"id":761,"depth":811,"text":762},{"id":771,"depth":811,"text":772},{"id":781,"depth":814,"text":781},[858],"译","2025-02-14 14:18:31","这篇文章涵盖了适合不同项目规模的各种 Vue 项目结构",false,"md","https:\u002F\u002Fbitmc.uno\u002Fpicgo\u002F67aef11ea579d-78.webp",{"aside":865},[866,867],"toc","auth-alex",true,"\u002Fposts\u002F2025\u002Fhow-to-structure-vue-projects",null,{"text":872,"minutes":873,"time":874,"words":875},"14 min read",13.475,808500,2695,{"title":5,"description":860},{"loc":869,"images":878},[879,880,881,882,883],{"loc":94},{"loc":176},{"loc":379},{"loc":503},{"loc":573},"posts\u002F2025\u002Fhow-to-structure-vue-projects",[886],"Vue","2026-02-07 23:23:50","K7fYsADw8aU6M6fGQlkEafm4b2e32POgJZYigw420Mg",[890,895],{"title":891,"path":892,"stem":893,"date":894,"type":870,"children":-1},"【翻译】构建 Pinia 插件进行跨标签页状态同步","\u002Fposts\u002F2025\u002Fbuilding-a-pinia-plugin-for-cross-tab-state-syncing","posts\u002F2025\u002Fbuilding-a-pinia-plugin-for-cross-tab-state-syncing","2025-02-14 11:32:59",{"title":298,"path":297,"stem":896,"date":897,"type":870,"children":-1},"posts\u002F2025\u002Fatomic-design-vue-or-nuxt","2025-02-14 15:43:50",1789642590173]