[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"similar-teambit--bit":3,"tool-teambit--bit":62},[4,18,26,36,46,54],{"id":5,"name":6,"github_repo":7,"description_zh":8,"stars":9,"difficulty_score":10,"last_commit_at":11,"category_tags":12,"status":17},4358,"openclaw","openclaw\u002Fopenclaw","OpenClaw 是一款专为个人打造的本地化 AI 助手，旨在让你在自己的设备上拥有完全可控的智能伙伴。它打破了传统 AI 助手局限于特定网页或应用的束缚，能够直接接入你日常使用的各类通讯渠道，包括微信、WhatsApp、Telegram、Discord、iMessage 等数十种平台。无论你在哪个聊天软件中发送消息，OpenClaw 都能即时响应，甚至支持在 macOS、iOS 和 Android 设备上进行语音交互，并提供实时的画布渲染功能供你操控。\n\n这款工具主要解决了用户对数据隐私、响应速度以及“始终在线”体验的需求。通过将 AI 部署在本地，用户无需依赖云端服务即可享受快速、私密的智能辅助，真正实现了“你的数据，你做主”。其独特的技术亮点在于强大的网关架构，将控制平面与核心助手分离，确保跨平台通信的流畅性与扩展性。\n\nOpenClaw 非常适合希望构建个性化工作流的技术爱好者、开发者，以及注重隐私保护且不愿被单一生态绑定的普通用户。只要具备基础的终端操作能力（支持 macOS、Linux 及 Windows WSL2），即可通过简单的命令行引导完成部署。如果你渴望拥有一个懂你",349277,3,"2026-04-06T06:32:30",[13,14,15,16],"Agent","开发框架","图像","数据工具","ready",{"id":19,"name":20,"github_repo":21,"description_zh":22,"stars":23,"difficulty_score":10,"last_commit_at":24,"category_tags":25,"status":17},3808,"stable-diffusion-webui","AUTOMATIC1111\u002Fstable-diffusion-webui","stable-diffusion-webui 是一个基于 Gradio 构建的网页版操作界面，旨在让用户能够轻松地在本地运行和使用强大的 Stable Diffusion 图像生成模型。它解决了原始模型依赖命令行、操作门槛高且功能分散的痛点，将复杂的 AI 绘图流程整合进一个直观易用的图形化平台。\n\n无论是希望快速上手的普通创作者、需要精细控制画面细节的设计师，还是想要深入探索模型潜力的开发者与研究人员，都能从中获益。其核心亮点在于极高的功能丰富度：不仅支持文生图、图生图、局部重绘（Inpainting）和外绘（Outpainting）等基础模式，还独创了注意力机制调整、提示词矩阵、负向提示词以及“高清修复”等高级功能。此外，它内置了 GFPGAN 和 CodeFormer 等人脸修复工具，支持多种神经网络放大算法，并允许用户通过插件系统无限扩展能力。即使是显存有限的设备，stable-diffusion-webui 也提供了相应的优化选项，让高质量的 AI 艺术创作变得触手可及。",162132,"2026-04-05T11:01:52",[14,15,13],{"id":27,"name":28,"github_repo":29,"description_zh":30,"stars":31,"difficulty_score":32,"last_commit_at":33,"category_tags":34,"status":17},1381,"everything-claude-code","affaan-m\u002Feverything-claude-code","everything-claude-code 是一套专为 AI 编程助手（如 Claude Code、Codex、Cursor 等）打造的高性能优化系统。它不仅仅是一组配置文件，而是一个经过长期实战打磨的完整框架，旨在解决 AI 代理在实际开发中面临的效率低下、记忆丢失、安全隐患及缺乏持续学习能力等核心痛点。\n\n通过引入技能模块化、直觉增强、记忆持久化机制以及内置的安全扫描功能，everything-claude-code 能显著提升 AI 在复杂任务中的表现，帮助开发者构建更稳定、更智能的生产级 AI 代理。其独特的“研究优先”开发理念和针对 Token 消耗的优化策略，使得模型响应更快、成本更低，同时有效防御潜在的攻击向量。\n\n这套工具特别适合软件开发者、AI 研究人员以及希望深度定制 AI 工作流的技术团队使用。无论您是在构建大型代码库，还是需要 AI 协助进行安全审计与自动化测试，everything-claude-code 都能提供强大的底层支持。作为一个曾荣获 Anthropic 黑客大奖的开源项目，它融合了多语言支持与丰富的实战钩子（hooks），让 AI 真正成长为懂上",159267,2,"2026-04-17T11:29:14",[14,13,35],"语言模型",{"id":37,"name":38,"github_repo":39,"description_zh":40,"stars":41,"difficulty_score":42,"last_commit_at":43,"category_tags":44,"status":17},8272,"opencode","anomalyco\u002Fopencode","OpenCode 是一款开源的 AI 编程助手（Coding Agent），旨在像一位智能搭档一样融入您的开发流程。它不仅仅是一个代码补全插件，而是一个能够理解项目上下文、自主规划任务并执行复杂编码操作的智能体。无论是生成全新功能、重构现有代码，还是排查难以定位的 Bug，OpenCode 都能通过自然语言交互高效完成，显著减少开发者在重复性劳动和上下文切换上的时间消耗。\n\n这款工具专为软件开发者、工程师及技术研究人员设计，特别适合希望利用大模型能力来提升编码效率、加速原型开发或处理遗留代码维护的专业人群。其核心亮点在于完全开源的架构，这意味着用户可以审查代码逻辑、自定义行为策略，甚至私有化部署以保障数据安全，彻底打破了传统闭源 AI 助手的“黑盒”限制。\n\n在技术体验上，OpenCode 提供了灵活的终端界面（Terminal UI）和正在测试中的桌面应用程序，支持 macOS、Windows 及 Linux 全平台。它兼容多种包管理工具，安装便捷，并能无缝集成到现有的开发环境中。无论您是追求极致控制权的资深极客，还是渴望提升产出的独立开发者，OpenCode 都提供了一个透明、可信",144296,1,"2026-04-16T14:50:03",[13,45],"插件",{"id":47,"name":48,"github_repo":49,"description_zh":50,"stars":51,"difficulty_score":32,"last_commit_at":52,"category_tags":53,"status":17},2271,"ComfyUI","Comfy-Org\u002FComfyUI","ComfyUI 是一款功能强大且高度模块化的视觉 AI 引擎，专为设计和执行复杂的 Stable Diffusion 图像生成流程而打造。它摒弃了传统的代码编写模式，采用直观的节点式流程图界面，让用户通过连接不同的功能模块即可构建个性化的生成管线。\n\n这一设计巧妙解决了高级 AI 绘图工作流配置复杂、灵活性不足的痛点。用户无需具备编程背景，也能自由组合模型、调整参数并实时预览效果，轻松实现从基础文生图到多步骤高清修复等各类复杂任务。ComfyUI 拥有极佳的兼容性，不仅支持 Windows、macOS 和 Linux 全平台，还广泛适配 NVIDIA、AMD、Intel 及苹果 Silicon 等多种硬件架构，并率先支持 SDXL、Flux、SD3 等前沿模型。\n\n无论是希望深入探索算法潜力的研究人员和开发者，还是追求极致创作自由度的设计师与资深 AI 绘画爱好者，ComfyUI 都能提供强大的支持。其独特的模块化架构允许社区不断扩展新功能，使其成为当前最灵活、生态最丰富的开源扩散模型工具之一，帮助用户将创意高效转化为现实。",108322,"2026-04-10T11:39:34",[14,15,13],{"id":55,"name":56,"github_repo":57,"description_zh":58,"stars":59,"difficulty_score":32,"last_commit_at":60,"category_tags":61,"status":17},6121,"gemini-cli","google-gemini\u002Fgemini-cli","gemini-cli 是一款由谷歌推出的开源 AI 命令行工具，它将强大的 Gemini 大模型能力直接集成到用户的终端环境中。对于习惯在命令行工作的开发者而言，它提供了一条从输入提示词到获取模型响应的最短路径，无需切换窗口即可享受智能辅助。\n\n这款工具主要解决了开发过程中频繁上下文切换的痛点，让用户能在熟悉的终端界面内直接完成代码理解、生成、调试以及自动化运维任务。无论是查询大型代码库、根据草图生成应用，还是执行复杂的 Git 操作，gemini-cli 都能通过自然语言指令高效处理。\n\n它特别适合广大软件工程师、DevOps 人员及技术研究人员使用。其核心亮点包括支持高达 100 万 token 的超长上下文窗口，具备出色的逻辑推理能力；内置 Google 搜索、文件操作及 Shell 命令执行等实用工具；更独特的是，它支持 MCP（模型上下文协议），允许用户灵活扩展自定义集成，连接如图像生成等外部能力。此外，个人谷歌账号即可享受免费的额度支持，且项目基于 Apache 2.0 协议完全开源，是提升终端工作效率的理想助手。",100752,"2026-04-10T01:20:03",[45,13,15,14],{"id":63,"github_repo":64,"name":65,"description_en":66,"description_zh":67,"ai_summary_zh":67,"readme_en":68,"readme_zh":69,"quickstart_zh":70,"use_case_zh":71,"hero_image_url":72,"owner_login":73,"owner_name":74,"owner_avatar_url":75,"owner_bio":76,"owner_company":77,"owner_location":77,"owner_email":78,"owner_twitter":77,"owner_website":79,"owner_url":80,"languages":81,"stars":117,"forks":118,"last_commit_at":119,"license":120,"difficulty_score":32,"env_os":121,"env_gpu":121,"env_ram":121,"env_deps":122,"category_tags":132,"github_topics":133,"view_count":32,"oss_zip_url":77,"oss_zip_packed_at":77,"status":17,"created_at":153,"updated_at":154,"faqs":155,"releases":156},8651,"teambit\u002Fbit","bit","AI-powered development workspaces with reusable components, architectural clarity and zero overhead.","Bit 是一款专为 AI 时代打造的智能开发工作区工具，旨在通过组件化架构提升软件构建的效率与质量。它将源代码组织为可复用的独立组件，帮助开发者从编码到持续集成（CI）的全流程中，构建可靠、可扩展且一致的应用程序。\n\nBit 主要解决了传统开发中代码重复率高、架构混乱以及协作成本大的痛点。通过定义标准化的构建模块，它不仅让人类开发者能轻松共享 UI 组件和功能模块，更支持 AI 代理利用模型上下文协议（MCP）智能地创建和复用组件，从而大幅加速开发进程并减少冗余。\n\n这款工具非常适合前端与全栈开发者、技术团队以及希望引入 AI 辅助编程的组织使用。无论你的项目是单体仓库、多仓库还是无仓库结构，Bit 都能灵活适配。\n\n其独特亮点在于“原子化安全部署”与“壳应用（Shell Applications）”概念，允许将独立组件像搭积木一样组合成完整应用，并确保测试与生产环境的部署简单且优化。Bit 原生支持 TypeScript 和 ESM，无缝兼容 React、Vue、Angular、Next.js 等主流 JavaScript 生态框架，让开发者能够立即上手，专注于创造核心价值。","\u003Cp align=\"center\">\n  \u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fteambit_bit_readme_0ac9bff9178c.png\"\u002F>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fbit.dev\u002F\">Website\u003C\u002Fa> |\n  \u003Ca href=\"https:\u002F\u002Fbit.dev\u002Fdocs\u002F\">Docs\u003C\u002Fa> |\n  \u003Ca href=\"https:\u002F\u002Fbit.cloud\u002Fbitdev\">Community\u003C\u002Fa> |\n  \u003Ca href=\"https:\u002F\u002Fbit.cloud\u002F\">Bit Cloud\u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003C\u002Fp>\n\n\u003Ch3 align=\"center\">\n\u003C\u002Fh3>\n\n\u003Cp align=\"center\">\n  \n\u003Cp align=\"center\">\n\u003Ca href=\"https:\u002F\u002Fopensource.org\u002Flicenses\u002FApache-2.0\">\u003Cimg alt=\"apache\" src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLicense-Apache%202.0-blue.svg\">\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fteambit\u002Fbit\u002Fblob\u002Fmaster\u002FCONTRIBUTING.md\">\u003Cimg alt=\"prs\" src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FPRs-welcome-brightgreen.svg\">\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fcircleci.com\u002Fgh\u002Fteambit\u002Fbit\u002Ftree\u002Fmaster\">\u003Cimg alt=\"Circle Status\" src=\"https:\u002F\u002Fcircleci.com\u002Fgh\u002Fteambit\u002Fbit\u002Ftree\u002Fmaster.svg?style=shield\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fprettier\u002Fprettier\">\u003Cimg alt =\"Styled with Prettier\" src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fstyled_with-prettier-ff69b4.svg\">\n\u003Ca href=\"https:\u002F\u002Fjoin.slack.com\u002Ft\u002Fbit-dev-community\u002Fshared_invite\u002Fzt-1vq1vcxxu-CEVobR1p9BurmW8QnQFh1w\" >\u003Cimg alt=\"Join Slack\" src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FSlack-Join%20Bit%20Slack-blueviolet\"\u002F>\u003C\u002Fa>\n\n[Bit](https:\u002F\u002Fbit.dev) is the build system to connect components and apps from development to CI in the AI era. Bit organizes source code into composable components, empowering to build reliable, scalable and consistent applications. It enables AI agents to intelligenly create and reuse components via MCP preventing duplication and accelerating development.\n\n⚡ **Features**\n\n- **Reusable components.** Create reusable UI components and modules to reuse across your software.\n- **Standard building blocks.** Define the blueprints templates for creating components for devs and AI as one.\n- **Shell applications.** Compose reusable components and features into application shells.\n- **Atomic and safe deployments.** Ensure simple, safe and optimized deployments of apps and services for testing and production.\n\nBit supports all tooling in the JS ecosystem and comes out of the box with official dev environments for [NodeJS](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fbackend-intro), [React](https:\u002F\u002Fbit.dev\u002Fdocs\u002Freact-intro), [Angular](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fangular-introduction), [Vue](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fvue-intro), [React Native](https:\u002F\u002Fbit.dev\u002Fdocs\u002Freact-native-intro), [NextJS](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fquick-start\u002Fhello-world-nextjs) and [far more](https:\u002F\u002Fbit.dev\u002Fdocs). All are native to TypeScript and ESM and equipped with the best dev tooling.\n\nBit is a fit to every codebase structure. You can use Bit components in a monorepo, polyrepo, or even without repositories at all.\n\n## Getting started\n\n### Install Bit\n\nUse the Bit installer to install Bit to be available on your PATH.\n\n```bash\nnpx @teambit\u002Fbvm install\n```\n\nInitialize Bit on a new folder or in an existing project by running the following command:\n\n```bash\nbit init --default-scope my-org.my-project\n```\n\nMake sure to [create your scope on the Bit platform](https:\u002F\u002Fbit.cloud\u002Fsignup) and use the right org and project name. After running the command, Bit is initialized on the chosen directory, and ready to be used via Bit commands, [AI agent, your editor](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Finstalling-bit\u002Feditor-setup) or the Bit UI!\n\n### Create shell application\n\nCreate the application shell to run, compose and deploy your application:\n\n```bash\nbit create react-app corporate-website\n```\n\nRun the platform:\n\n```\nbit run corporate-website\n```\n\nHead to http:\u002F\u002Flocalhost:3000 to view your application shell. You can start composing the application layout and specific pages to build your application. Learn more on [building shell applications](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Fcomposing\u002Fcreate-apps).\n\n### Compose components\n\nCreate the components to compose into the feature. Run the following command to create a new React UI component for the application login route:\n\n```\nbit create react pages\u002Flogin\n```\n\nFind simple guides for creating NodeJS modules, UI components and apps, backend services and more on the [Create Component docs](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Fcomposing\u002Fcreating-components\u002F).\n\nCompose the component into the application shell:\n\n```ts\nimport { Login } from '@my-org\u002Fusers.pages.login';\nimport { Routes, Route } from 'react-router-dom';\n\nexport function CorporateWebsite() {\n  return (\n    \u003CAcmeTheme>\n      \u003CNavigationProvider>\n        \u003CRoutes>\n          \u003CRoute path=\"\u002F\" element={\u003Cdiv>Hello world\u003C\u002Fdiv>} \u002F>\n          \u003CRoute path=\"\u002Flogin\" element={\u003CLogin \u002F>} \u002F>\n        \u003C\u002FRoutes>\n      \u003C\u002FNavigationProvider>\n    \u003C\u002FAcmeTheme>\n  );\n}\n\n```\n\nHead to http:\u002F\u002Flocalhost:3000\u002Flogin to view your new login page.\nYou can use bit templates to list official templates or find guides for creating React hooks, backend services, NodeJS modules, UI components and more on our [create components docs](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Fcomposing\u002Fcreating-components). Optionally, use bit start to run the Bit UI to preview components in isolation.\n\n### Release and deploy\n\nYou can either use hosted scopes on [Bit Cloud](https:\u002F\u002Fbit.cloud) or by [hosting scopes on your own](https:\u002F\u002Fbit.dev\u002Freference\u002Fscope\u002Frunning-a-scope-server). Use the following command to create your Bit Cloud account and your first scope.\n\n```bash\nbit login\n```\n\nUse semantic versioning to version your components:\n\n```bash\nbit tag --message \"my first release\" --major\n```\n\nBy default, Bit uses [Ripple CI](https:\u002F\u002Fbit.cloud\u002Fproducts\u002Fripple-ci) to build components. You can use the `--build` flag to build the components on the local machine. To tag and export from your CI of choice to automate the release process or use [our official CI scripts](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Fcollaborate\u002Fexporting-components#ci-scripts).\n\nAfter versioning, you can proceed to release your components:\n\n```bash\nbit export\n```\n\n### Modernize existing projects\n\nHead over to your [bit.cloud account](https:\u002F\u002Fbit.cloud) to see your components build progress. Once the build process is completed, the components will be available for use using standard package managers:\n\n```bash\nnpm install @my-org\u002Fusers.pages.login\n```\n\n## Next steps\n\n- [Create more components](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Fcomposing\u002Fcreating-components\u002F)\n- [Setup your editor](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Finstalling-bit\u002Feditor-setup)\n- [Configure CI of choice](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Fcollaborate\u002Fexporting-components\u002F#ci-scripts)\n- [Start from an existing project](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Finstalling-bit\u002Fstart-from-existing-project)\n\n## Contributors\n\nBit is entirely built with Bit and you can find all its components on [Bit Cloud](https:\u002F\u002Fbit.cloud\u002Fteambit\u002F~scopes).\n\n\u003Ca href=\"..\u002F..\u002Fgraphs\u002Fcontributors\">\u003Cimg src=\"https:\u002F\u002Fopencollective.com\u002Fbit\u002Fcontributors.svg?width=890&button=false\" \u002F>\u003C\u002Fa>\n\nYour contribution, no matter how big or small, is much appreciated. Before contributing, please read the [code of conduct](CODE_OF_CONDUCT.md).\n\nSee [Contributing](CONTRIBUTING.md).\n\n## License\n\n[Apache License, Version 2.0](https:\u002F\u002Fgithub.com\u002Fteambit\u002Fbit\u002Fblob\u002Fmaster\u002FLICENSE)\n","\u003Cp align=\"center\">\n  \u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fteambit_bit_readme_0ac9bff9178c.png\"\u002F>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fbit.dev\u002F\">官网\u003C\u002Fa> |\n  \u003Ca href=\"https:\u002F\u002Fbit.dev\u002Fdocs\u002F\">文档\u003C\u002Fa> |\n  \u003Ca href=\"https:\u002F\u002Fbit.cloud\u002Fbitdev\">社区\u003C\u002Fa> |\n  \u003Ca href=\"https:\u002F\u002Fbit.cloud\u002F\">Bit Cloud\u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003C\u002Fp>\n\n\u003Ch3 align=\"center\">\n\u003C\u002Fh3>\n\n\u003Cp align=\"center\">\n  \n\u003Cp align=\"center\">\n\u003Ca href=\"https:\u002F\u002Fopensource.org\u002Flicenses\u002FApache-2.0\">\u003Cimg alt=\"apache\" src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLicense-Apache%202.0-blue.svg\">\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fteambit\u002Fbit\u002Fblob\u002Fmaster\u002FCONTRIBUTING.md\">\u003Cimg alt=\"prs\" src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FPRs-welcome-brightgreen.svg\">\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fcircleci.com\u002Fgh\u002Fteambit\u002Fbit\u002Ftree\u002Fmaster\">\u003Cimg alt=\"Circle Status\" src=\"https:\u002F\u002Fcircleci.com\u002Fgh\u002Fteambit\u002Fbit\u002Ftree\u002Fmaster.svg?style=shield\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fprettier\u002Fprettier\">\u003Cimg alt =\"Styled with Prettier\" src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fstyled_with-prettier-ff69b4.svg\">\n\u003Ca href=\"https:\u002F\u002Fjoin.slack.com\u002Ft\u002Fbit-dev-community\u002Fshared_invite\u002Fzt-1vq1vcxxu-CEVobR1p9BurmW8QnQFh1w\" >\u003Cimg alt=\"Join Slack\" src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FSlack-Join%20Bit%20Slack-blueviolet\"\u002F>\u003C\u002Fa>\n\n[Bit](https:\u002F\u002Fbit.dev) 是一款在 AI 时代将组件与应用从开发阶段无缝连接到 CI 的构建系统。Bit 将源代码组织成可组合的组件，助力开发者构建可靠、可扩展且一致的应用程序。它使 AI 代理能够通过 MCP 智能地创建和复用组件，从而避免重复劳动并加速开发进程。\n\n⚡ **功能特性**\n\n- **可复用组件。** 创建可在整个软件中复用的 UI 组件和模块。\n- **标准构建块。** 定义用于为开发者和 AI 生成组件的蓝图模板。\n- **壳层应用。** 将可复用的组件和功能组合成应用壳层。\n- **原子化且安全的部署。** 确保应用和服务在测试和生产环境中的简单、安全及优化部署。\n\nBit 支持 JavaScript 生态系统中的所有工具，并开箱即用地提供针对 [NodeJS](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fbackend-intro)、[React](https:\u002F\u002Fbit.dev\u002Fdocs\u002Freact-intro)、[Angular](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fangular-introduction)、[Vue](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fvue-intro)、[React Native](https:\u002F\u002Fbit.dev\u002Fdocs\u002Freact-native-intro)、[NextJS](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fquick-start\u002Fhello-world-nextjs) 以及更多框架的官方开发环境。这些环境原生支持 TypeScript 和 ESM，并配备了最佳的开发工具链。\n\nBit 适用于任何代码库结构。你可以在单体仓库、多仓库甚至无仓库的情况下使用 Bit 组件。\n\n## 开始使用\n\n### 安装 Bit\n\n使用 Bit 安装程序将 Bit 安装到你的 PATH 中：\n\n```bash\nnpx @teambit\u002Fbvm install\n```\n\n在新文件夹或现有项目中初始化 Bit，运行以下命令：\n\n```bash\nbit init --default-scope my-org.my-project\n```\n\n请务必在 [Bit 平台上创建你的作用域](https:\u002F\u002Fbit.cloud\u002Fsignup)，并使用正确的组织和项目名称。执行该命令后，Bit 就会在选定目录中初始化完毕，你可以通过 Bit 命令、AI 代理、编辑器插件（参见 [Bit 文档中的编辑器设置](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Finstalling-bit\u002Feditor-setup)）或 Bit UI 来开始使用了！\n\n### 创建壳层应用\n\n创建应用壳层以运行、组合并部署你的应用：\n\n```bash\nbit create react-app corporate-website\n```\n\n运行平台：\n\n```\nbit run corporate-website\n```\n\n访问 http:\u002F\u002Flocalhost:3000 查看你的应用壳层。你可以开始设计应用布局和具体页面，逐步构建你的应用。更多关于 [构建壳层应用](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Fcomposing\u002Fcreate-apps) 的信息，请参阅相关文档。\n\n### 组合组件\n\n创建要组合到功能中的组件。例如，运行以下命令为应用的登录路由创建一个新的 React UI 组件：\n\n```\nbit create react pages\u002Flogin\n```\n\n有关创建 NodeJS 模块、UI 组件、应用、后端服务等的简单指南，请参阅 [创建组件文档](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Fcomposing\u002Fcreating-components\u002F)。\n\n将组件组合到应用壳层中：\n\n```ts\nimport { Login } from '@my-org\u002Fusers.pages.login';\nimport { Routes, Route } from 'react-router-dom';\n\nexport function CorporateWebsite() {\n  return (\n    \u003CAcmeTheme>\n      \u003CNavigationProvider>\n        \u003CRoutes>\n          \u003CRoute path=\"\u002F\" element={\u003Cdiv>Hello world\u003C\u002Fdiv>} \u002F>\n          \u003CRoute path=\"\u002Flogin\" element={\u003CLogin \u002F>} \u002F>\n        \u003C\u002FRoutes>\n      \u003C\u002FNavigationProvider>\n    \u003C\u002FAcmeTheme>\n  );\n}\n\n```\n\n访问 http:\u002F\u002Flocalhost:3000\u002Flogin 查看你的新登录页面。\n你可以使用 Bit 提供的模板来查看官方模板，或者在我们的 [创建组件文档](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Fcomposing\u002Fcreating-components) 中找到关于创建 React Hooks、后端服务、NodeJS 模块、UI 组件等方面的指南。此外，还可以使用 Bit Start 启动 Bit UI，以独立预览组件。\n\n### 发布与部署\n\n你可以选择在 [Bit Cloud](https:\u002F\u002Fbit.cloud) 上托管作用域，也可以 [自行托管作用域](https:\u002F\u002Fbit.dev\u002Freference\u002Fscope\u002Frunning-a-scope-server)。使用以下命令创建你的 Bit Cloud 账户和第一个作用域：\n\n```bash\nbit login\n```\n\n采用语义化版本控制为你的组件打标签：\n\n```bash\nbit tag --message \"my first release\" --major\n```\n\n默认情况下，Bit 使用 [Ripple CI](https:\u002F\u002Fbit.cloud\u002Fproducts\u002Fripple-ci) 构建组件。你也可以使用 `--build` 标志在本地机器上构建组件。为了自动化发布流程，可以使用你选择的 CI 工具进行标记和导出，或者直接使用我们提供的 [官方 CI 脚本](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Fcollaborate\u002Fexporting-components#ci-scripts)。\n\n完成版本标记后，即可发布你的组件：\n\n```bash\nbit export\n```\n\n### 现有项目的现代化改造\n\n前往你的 [Bit Cloud 账户](https:\u002F\u002Fbit.cloud)，查看组件的构建进度。构建完成后，这些组件就可以通过标准包管理器使用了：\n\n```bash\nnpm install @my-org\u002Fusers.pages.login\n```\n\n## 下一步\n\n- [创建更多组件](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Fcomposing\u002Fcreating-components\u002F)\n- [配置你的编辑器](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Finstalling-bit\u002Feditor-setup)\n- [配置你选择的 CI](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Fcollaborate\u002Fexporting-components\u002F#ci-scripts)\n- [从现有项目开始](https:\u002F\u002Fbit.dev\u002Fdocs\u002Fgetting-started\u002Finstalling-bit\u002Fstart-from-existing-project)\n\n## 贡献者\n\nBit 完全由 Bit 框架构建，您可以在 [Bit Cloud](https:\u002F\u002Fbit.cloud\u002Fteambit\u002F~scopes) 上找到其所有组件。\n\n\u003Ca href=\"..\u002F..\u002Fgraphs\u002Fcontributors\">\u003Cimg src=\"https:\u002F\u002Fopencollective.com\u002Fbit\u002Fcontributors.svg?width=890&button=false\" \u002F>\u003C\u002Fa>\n\n无论您的贡献大小，我们都深表感谢。在贡献之前，请阅读[行为准则](CODE_OF_CONDUCT.md)。\n\n请参阅[贡献指南](CONTRIBUTING.md)。\n\n## 许可证\n\n[Apache 2.0 许可证](https:\u002F\u002Fgithub.com\u002Fteambit\u002Fbit\u002Fblob\u002Fmaster\u002FLICENSE)","# Bit 快速上手指南\n\nBit 是一个面向 AI 时代的构建系统，旨在将源代码组织为可组合的组件。它支持从开发到 CI 的全流程，帮助开发者（及 AI 代理）高效创建、复用和部署可靠的应用程序。Bit 原生支持 TypeScript 和 ESM，并兼容 React、Vue、Angular、Next.js 等主流前端框架及 Node.js 后端环境。\n\n## 环境准备\n\n在开始之前，请确保您的开发环境满足以下要求：\n\n*   **操作系统**：Windows, macOS, 或 Linux\n*   **Node.js**：建议安装 LTS 版本（Bit 依赖 Node 环境运行）\n*   **包管理器**：npm, yarn, 或 pnpm（任选其一）\n*   **代码编辑器**：推荐 VS Code，并安装 Bit 相关插件以获得最佳体验\n\n> **注意**：目前官方未提供特定的中国镜像源，请使用全局网络环境或自行配置 npm 镜像加速安装依赖。\n\n## 安装步骤\n\n### 1. 安装 Bit 命令行工具\n使用 `npx` 运行 Bit 版本管理器 (BVM) 进行安装，这将把 `bit` 命令添加到您的系统路径中：\n\n```bash\nnpx @teambit\u002Fbvm install\n```\n\n### 2. 初始化项目\n在新文件夹或现有项目中初始化 Bit。请将 `my-org.my-project` 替换为您在 [Bit Cloud](https:\u002F\u002Fbit.cloud) 上创建的组织和项目名称（需先注册账号）：\n\n```bash\nbit init --default-scope my-org.my-project\n```\n\n初始化完成后，即可在当前目录使用 Bit 命令、AI 代理或 Bit UI 界面。\n\n## 基本使用\n\n以下是创建一个简单的 React 应用壳（Shell Application）并组合组件的最小化流程。\n\n### 1. 创建应用壳\n创建一个用于运行和部署的基础应用结构（以 React 为例）：\n\n```bash\nbit create react-app corporate-website\n```\n\n启动开发服务器预览应用：\n\n```bash\nbit run corporate-website\n```\n\n访问 `http:\u002F\u002Flocalhost:3000` 即可查看初始应用页面。\n\n### 2. 创建组件\n创建具体的功能组件，例如一个登录页面组件：\n\n```bash\nbit create react pages\u002Flogin\n```\n\n### 3. 组合组件\n在应用壳的代码中引入并组合新创建的组件。编辑主入口文件（如 `corporate-website.tsx`）：\n\n```ts\nimport { Login } from '@my-org\u002Fusers.pages.login';\nimport { Routes, Route } from 'react-router-dom';\n\nexport function CorporateWebsite() {\n  return (\n    \u003CAcmeTheme>\n      \u003CNavigationProvider>\n        \u003CRoutes>\n          \u003CRoute path=\"\u002F\" element={\u003Cdiv>Hello world\u003C\u002Fdiv>} \u002F>\n          \u003CRoute path=\"\u002Flogin\" element={\u003CLogin \u002F>} \u002F>\n        \u003C\u002FRoutes>\n      \u003C\u002FNavigationProvider>\n    \u003C\u002FAcmeTheme>\n  );\n}\n```\n\n刷新浏览器访问 `http:\u002F\u002Flocalhost:3000\u002Flogin` 即可看到新组件生效。\n\n### 4. 发布与部署\n当组件开发完成后，可以将其版本化并发布到 Bit Cloud 或私有 Scope。\n\n登录账户：\n```bash\nbit login\n```\n\n标记版本（遵循语义化版本控制）：\n```bash\nbit tag --message \"my first release\" --major\n```\n\n导出组件：\n```bash\nbit export\n```\n\n发布成功后，其他项目可通过标准包管理器安装使用该组件：\n```bash\nnpm install @my-org\u002Fusers.pages.login\n```","某中型电商团队正在重构其多端应用（Web、小程序、App），急需统一分散在各项目中的登录、支付和商品卡片等核心功能模块。\n\n### 没有 bit 时\n- **代码重复严重**：每个新项目都需复制粘贴旧代码，导致登录逻辑在三个端有五份不同实现，修复一个 Bug 需同步修改多处。\n- **架构混乱难维护**：组件耦合在项目源码中，缺乏独立版本管理，新人难以理清依赖关系，架构清晰度极低。\n- **协作与交付低效**：前端与 AI 助手无法直接调用标准化模块，每次开发新功能都要重新造轮子，且部署测试常因环境差异失败。\n\n### 使用 bit 后\n- **组件一次编写处处复用**：将登录、支付等封装为独立 Bit 组件，通过 `bit create` 快速生成标准模板，所有端自动同步最新修复，彻底消除重复代码。\n- **架构清晰可组合**：Bit 将源码组织为原子化组件，提供可视化的依赖图谱，开发者能像搭积木一样通过 `bit compose` 快速组装应用壳，架构一目了然。\n- **AI 驱动高效交付**：借助 MCP 协议，AI 代理能智能识别并复用现有 Bit 组件加速开发；同时支持原子化安全部署，确保从测试到生产的环境一致性。\n\nbit 通过将代码转化为可智能复用的原子组件，让团队在 AI 时代实现了从“复制粘贴”到“组合创新”的研发范式转型。","https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fteambit_bit_93b973e8.png","teambit","Bit","https:\u002F\u002Foss.gittoolsai.com\u002Favatars\u002Fteambit_6057bf62.png","Bit is the platform for the modular web. Join 200,000+ developers to build and ship modular web apps together, in a fast and scalable way.",null,"team@bit.dev","https:\u002F\u002Fbit.dev","https:\u002F\u002Fgithub.com\u002Fteambit",[82,86,90,94,97,101,105,108,111,114],{"name":83,"color":84,"percentage":85},"TypeScript","#3178c6",91.2,{"name":87,"color":88,"percentage":89},"MDX","#fcb32c",5.4,{"name":91,"color":92,"percentage":93},"JavaScript","#f1e05a",2.1,{"name":95,"color":96,"percentage":42},"SCSS","#c6538c",{"name":98,"color":99,"percentage":100},"Shell","#89e051",0.2,{"name":102,"color":103,"percentage":104},"PowerShell","#012456",0,{"name":106,"color":107,"percentage":104},"CSS","#663399",{"name":109,"color":110,"percentage":104},"Ruby","#701516",{"name":112,"color":113,"percentage":104},"Dockerfile","#384d54",{"name":115,"color":116,"percentage":104},"Batchfile","#C1F12E",18377,954,"2026-04-17T14:06:02","NOASSERTION","未说明",{"notes":123,"python":121,"dependencies":124},"该工具是用于 JavaScript\u002FTypeScript 生态系统的组件构建系统，并非 AI 模型推理工具，因此无需 GPU。安装需通过 npx 运行 @teambit\u002Fbvm 安装器。支持多种前端框架（React, Vue, Angular 等）及 Node.js 后端环境。建议在使用前创建 Bit Cloud 账户以同步组件范围（scope）。",[125,83,126,127,128,129,130,131],"NodeJS","React","Angular","Vue","React Native","NextJS","@teambit\u002Fbvm",[14,15,13],[134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152],"react","javascript","typescript","front-end","node-js","vue","collaboration","component-driven","distributed","polyrepo","monorepo","micro-frontend","micro-services","multirepo","multirepo-maintenance","service-oriented-architecture","composable","composable-architecture","ai","2026-03-27T02:49:30.150509","2026-04-18T03:35:35.043660",[],[157,162,167,172,177,182,187,192,197,202,207,212,217,222,227,231,235,240,245,250],{"id":158,"version":159,"summary_zh":160,"released_at":161},314697,"v1.7.41","### Features\r\n\r\n- Automatically install `peerDependencies` (#8954)\r\n- Quick search in component dev-server (`bit start`) - Mac: `CMD+K`, Windows\u002FLinux: `CTRL+K` (#8964)\r\n\r\n### Improvements\r\n\r\n- Add generators to a new workspace during initialization (example: `bit init --generator frontend.module-federation\u002Fenvs\u002Fmf-react-env`) (#8963)\r\n- Use dedicated SCSS and SASS parsers for better static code analysis and dependency detection (#8973)\r\n- Automated API Reference supports `@link` and alias for object binding nodes (#8969)\r\n- `bit status` warns about components that use deleted envs (#9009)\r\n- `bit merge` to support component patterns (#8990)\r\n- Various UI and CLI message and tooltip updates (#8962, #8959, #8974, #8975, #8967)\r\n- Change the recommended node version to be >=20.0.0 (#8966)\r\n\r\n### Performance\r\n\r\n- Speed up rendering the component graph on workspace (`bit start`) (#8978)\r\n- Update component loading flow to improve performance (#8970)\r\n- Improve command bootstrap performance by making it unnecessary to add apps to `workspace.jsonc` (#8965)\r\n- Improved strategy for determining if a snap is a part of a lane (#8961)\r\n\r\n### Bug Fixes\r\n\r\n- Fix an issue where the proxy agent didn't get the correct configuration (#8972)\r\n- Fix an issue where during `bit install`, components that compiled to ESM didn't have `type:module` in `package.json` (#9006)\r\n- Fix an issue where `bit delete` allowed deleting components from `main`, when on a lane (#9003)\r\n- Fix an issue where files that were removed from a component in a lane caused diverged lanes (#8976)\r\n- Fix an issue where when a component was merged to lane in a different lane, it wasn't available when using `--head` (#8960)\r\n\r\n### Internal\r\n\r\n- Export type for install result (#8947)\r\n- Add a fallback for events in webpack config (#8993)\r\n- Support component load options for component compilation API (#9007)\r\n- Update dependency versions (#8953, #8952, #9004, #8977, #9008, #8951)\r\n- Refactor legacy functionalities to components (#9001, #8999, #8998, #8997, #8995, #8996, #8992, #8994, #8991, #8988, #8989, #8987, #8984, #8986, #8985, #8983, #8982, #8981, #8979)","2024-07-09T13:57:30",{"id":163,"version":164,"summary_zh":165,"released_at":166},314678,"v1.13.58","### 新特性\n\n- 新增 `bit deps diagnose` 命令，通过扫描 `node_modules\u002F.pnpm` 来分析工作区依赖膨胀情况，报告版本差异较大的顶级包，并识别导致组合爆炸的 peer 依赖。可使用 `--package \u003Cname>` 参数深入查看特定包的信息（#10189）\n- **社区工作区模板** 直接注册到核心中，使得 `bit new react`、`bit new platform` 和 `bit new harmony` 命令无需再指定 `--aspect` 或 `--env` 标志即可正常运行（#10156）\n- **车道历史** 命令现已稳定——移除了所有车道历史子命令上的 EXPERIMENTAL 标记。`bit lane history-diff` 现在支持 0、1 或 2 个参数，使用更加便捷（#10192）\n\n### 改进\n\n- 为 `bit ci merge` 命令新增 `--skip-push` 标志，适用于 CI 流水线需要单独处理推送步骤的组织（#10171）\n- **工作区概览聚合** 现在具有粘性，并由 URL 驱动（#10161）\n- 允许在当前车道存在暂存或分叉组件时创建新车道（#10155）\n- 当 `bit check-types` 没有需要检查的组件时，显示友好的提示信息，与其他命令保持一致（#10151）\n- 在 `bit templates` 的输出中显示实际的环境名称，而非内部 aspect ID（#10152）\n- 在 `bit import` 的帮助信息中进一步澄清 `--write-deps` 选项的用法（#10158）\n- 提升 CLI 技能命令的可发现性（#10190）\n\n### 性能优化\n\n- 对 `bit check-types` 中的 `getDiagnostic` 调用进行批处理，避免在大型工作区中过度占用 tsserver 资源，性能提升约 35%（#10180）\n- 将递归的版本历史遍历转换为迭代方式，以防止版本历史过深（超过 2000 个版本）的仓库发生栈溢出问题（#10144）\n\n### 问题修复\n\n- 修复了 `bit init --external-package-manager` 会向现有 `package.json` 文件中添加 `\"type\": \"module\"` 的问题（#10148）\n- 修复了当 `bit init` 使用 `externalPackageManager: true` 时，postinstall 脚本中未包含 `bit ws-config write` 的问题（#10147）\n- 修复了环境依赖被错误地安装为用户组件依赖的问题（#10150）\n- 修复了当 `env.jsonc` 包含 `+` 版本占位符时，`bit install` 会报错“不受任何可用解析器支持”的问题（#10154）\n- 修复了在快照后打标签时，若设置了 `populateArtifactsFrom`，隔离器会覆盖已合并的 `package.json` 文件的问题（#10166）\n- 修复了 `react-dom` 的 peer 依赖版本可能与环境默认 peer 中的 `react` 版本不同步的问题（#10195）\n- 修复了在不进行快照的情况下合并车道时，不会添加历史记录条目的问题（#10149）\n- 修复了从嵌套目录运行 `bit doctor --archive --exclude-local-scope` 时，未能排除 `.bit\u002Fobjects` 目录的问题（#10184）\n- 修复了 MDX 依赖检测在遇到旧版语法文件时会崩溃，而未能回退到基于正则表达式的导入提取方法的问题（#10174）\n- 修复了 TypeScript 解析器在遇到格式错误的 AST 节点时会崩溃，进而导致 UI 服务器宕机的问题（#10165）\n- 修复了…","2026-02-15T09:39:59",{"id":168,"version":169,"summary_zh":170,"released_at":171},314686,"v1.11.3","### 改进\n\n- 在 `env.jsonc` 中支持 npm 别名 (#9728)\n- 可以使用 `bit delete --snap` 删除快照 (#9701)\n- 各种 UI\u002FUX 和 CLI 输出的更新 (#9747, #9717, #9741)\n\n### Bug 修复\n\n- 修复将依赖从 `peer` 移动到 `dev` 时未更新依赖的问题 (#9720)\n- 修复当某些环境未实现预览 API 时，`bit start` 会报错的问题 (#9702)\n- 修复在添加已移除的依赖时，工作区策略未被验证的问题 (#9748)\n- 修复组件未找到错误被错误触发的问题 (#9705)\n\n### 内部改进\n\n- 更新依赖项 (#9739, #9697)\n- 修复在开发模式下运行 `bit start` 时使用 `--no-browser` 的问题 (#9708)\n- 修复当工作区中的组件作为依赖出现在依赖图中时，锁定文件生成失败的问题 (#9698)\n- 为 MCP 服务器准备命令 (#9744, #9742, #9743, #9740, #9737, #9735, #9727, #9730, #9726, #9725, #9719, #9710, #9704, #9706, #9731, #9733, #9699, #9723, #9716, #9707, #9711, #9736, #9732, #9722, #9729, #9712, #9738, #9718, #9721, #9695, #9734)","2025-06-10T11:37:35",{"id":173,"version":174,"summary_zh":175,"released_at":176},314687,"v1.10.0","### 改进\n\n- 通过在 `workspace.jsonc` 中的依赖解析器中添加新的 `componentRangePrefix` 属性来定义语义化版本前缀，从而支持组件的语义化版本范围（#9681、#9691）\n- 允许从 https\u002Fgit URL 安装依赖项（#9680）\n- 使用 `bit import ... --write-deps` 将导入组件的依赖项写入 `workspace.jsonc` 或 `package.json` 文件中（#9682）\n\n### Bug 修复\n\n- 修复了一个问题：`+` 号被保存到组件的 `package.json` 中，而不是实际解析后的版本号（#9685）\n- 修复了预览内容高度计算不正确的问题（#9684）\n\n### 内部改进\n\n- 改进文件监听器（#9686、#9683、#9678）\n- 改进插件加载问题的错误日志记录（#9687）\n- 更改日志模式命令的格式（#9675）\n- 支持将扁平化的依赖项保存为 `string[]` 而不是 `Object[]`（#9679）\n- 传播运行时预览错误（#9676）\n- 更新依赖项（#9677）","2025-04-29T13:11:42",{"id":178,"version":179,"summary_zh":180,"released_at":181},314688,"v1.9.124","### Improvements\r\n\r\n- Add test coverage report to test results (in supporting versions of the testers) (#9657)\r\n- Add support for `+` policy in `env.jsonc` for version to be resolved from the workspace (#9641)\r\n- `bit install --add-missing-deps` supports skipping unavailable packages with the `--skip-unavailable` flag (#9667) (#9667)\r\n\r\n### Performance\r\n\r\n- `bit start` faster at handling many changes in components (#9668, #9651, #9655, #9642, #9670)\r\n\r\n### Bug Fixes\r\n\r\n- Fix an issue where Bit mis-fired `componentNotFound` issue (#9671)\r\n- Fix an issue where an API type wasn't named correctly in API Reference (#9673)\r\n- Fix an issue where in some cases component size wasn't calculated (#9659)\r\n- Fix an issue where `bit env replace` failed when env wasn't loaded (#9632)\r\n\r\n### Internal\r\n\r\n- Update dependencies (#9664, #9666, #9660, #9637)\r\n- Refactoring legacy code (#9640, #9639, #9638, #9636, #9635, #9654, #9658, #9559, #9650, #9644, #9665)\r\n- Add integrities to dependency graph (#9574)\r\n- Add `trackMany` API (#9661)\r\n- Add more validations to deps-resolver aspect data before saving (#9648)","2025-04-15T18:54:54",{"id":183,"version":184,"summary_zh":185,"released_at":186},314689,"v1.9.100","### Improvements\r\n\r\n- Improve API Reference and documentation (#9569)\r\n  - Improved handling of internal and external type references\r\n  - Better handling of inferred array types, generic types, and Promise types\r\n  - Fixed type reference resolution for internal components\r\n  - Added support for displaying examples in function documentation\r\n  - Better code block extraction and formatting in JSDoc comments\r\n  - Improved rendering of tuple types\r\n  - Added external link icons for external type references\r\n- Added prompt support to `bit create` command for interactive templates (#9610)\r\n- `bit snap` natively supports publishing to privately hosted package registries (#9606)\r\n- Introduce `--json` option to `bit test` and `bit check-types` commands to get results in JSON format (#9615, #9614)\r\n- Improve various CLI outputs with more descriptive errors and messages (#9612, #9607, #9583, #9617, #9581)\r\n\r\n### Performance\r\n\r\n- Dramatically reduce file system I\u002FO to improve command execution time (#9604, #9590, #9591, #9598, #9596, #9589, #9586, #9568, #9588, #9578, #9577, #9572)\r\n\r\n### Bug Fixes\r\n\r\n- Fix an issue where if a component had `-preview` in it's name, it caused component-preview-chunk to have incorrect name (#9622)\r\n- Fix an issue where `bit install` didn't do proper validation on package name format (#9582)\r\n- Fix an issue where when `env.jsonc` was modified, dependency cache wasn't cleaned (#9564)\r\n- Fix an issue where SSR wasn't working on `bit start` in workspace nor on a Scope (#9585)\r\n- Fix an issue where `bit install` failed during `pnpm prune` (#9573)\r\n- Fix an issue where a default `viewport` property was set on all compositions (#9571)\r\n- Fix an issue where not all component IDs were available in the workspace dependency graph (#9565)\r\n\r\n### Internal\r\n\r\n- Update dependencies (#9594, #9593, #9592, #9527, #9528)\r\n- Refactoring (#9619, #9579, #9584, #9587)\r\n- Introduce \"--limit\" flag to limit the number of versions shown in the graph (#9603)\r\n- `getSchemas` API to always return `Schema[]` (#9605)\r\n- Replace incorrect uses of the term \"localScope\" with \"workspace\" (#9621)\r\n- New API for debugging filesystem reads during commands (#9599)\r\n- Add `config-conflict` data to the `api\u002Flanes\u002Fcheck-conflicts` route (#9602)","2025-03-17T13:13:45",{"id":188,"version":189,"summary_zh":190,"released_at":191},314694,"v1.8.52","### Improvements\r\n\r\n* Improve various CLI outputs to improve dev-experience (#9175, #9171, #9167, #9114, #9161, #9131, #9132, #9170, #9096)\r\n* Show dependents of a Lane in the component-drawer of the workspace and scope (#9151, #9154, #9152)\r\n\r\n### Performance\r\n\r\n* Reduce memory usage during peer dependencies resolution (#9156)\r\n\r\n### Bug Fixes\r\n\r\n* Fix an issue where modified components were rendered with opacity in the Bit dev-server (#9136)\r\n* Fix an issue where user-bar and compositions got re-rendered on route change in the Bit dev-server (#9137)\r\n* Fix an issue where `bit env replace` didn't work well when multiple versions of the same env is used for various components (#9174)\r\n* Fix an issue where link to line-of-code didn't scroll to selected line (#9160)\r\n* Fix an issue where automated API-reference had a missing API in tagged exports (#9162)\r\n* Fix an issue where Vite-generated previews didn't work well on windows (#9143)\r\n* Fix an issue where `onLoad` event wasn't triggered on webpack compilation errors (#9109)\r\n* Fix an issue where after `bit new` an error about \"missing tsconfig\" appears (#9092)\r\n\r\n### Internal\r\n\r\n* Additional APIs for the VScode-Bit-plugin (#9178, #9172, #9169, #9144, #9139, #9120, #9090, #9155, #9153, #9106, #9105, #9099, #9101, #9125, #9104, #9087, #9094, #9088)\r\n* Various fixes for \"env loading\" process (#9165, #9128, #9130, #9134, #9138, #9111)\r\n* Update dependencies (#9147, #9110, #9150, #9103, #9121, #9135, #9098)\r\n* Remove `--lane-history` from being a feature flag, as it is now the default (#9095)\r\n* Introduce more strategies to avoid fast-forward on `bit snap` or `tag` (#9159)\r\n* Add some documentation for `teambit.workspace\u002Fworkspace-config-files` aspect (#9116)\r\n* Prepare the `onlyOverview` mode for component-docs (#9124, #9141, #9119, #9166)\r\n* Store generator service data for envs in their model (#9089)\r\n* Fix types issues in config mutator (#9177)\r\n* Add add webpack alias `@teambit\u002Fbase-react.navigation.link` to ensure a single instance (#9113)\r\n* Gracefully handle missing compositions (#9093)\r\n* Improve backwards compatibility for legacy Jest testers (#9115)\r\n* Support HMR for legacy-react-apps when using \"port-forwarding\" (#9091)\r\n* Support define the env type by a type member as well as name (#9085)","2024-09-08T13:23:05",{"id":193,"version":194,"summary_zh":195,"released_at":196},314695,"v1.8.20","### New Features\r\n\r\n- Introduce **Local Only Component** workspace feature (#9059, #9057)\r\n  - Mark any number of components as **Local Only** with the new `bit local-only set \u003Ccomponent>` command \r\n  - **Local Only** components allow you to avoid tagging\u002Freleasing specific components, even if they are modified, or their dependencies are modified.\r\n  - Scenario 1 - I have an app in the workspace, which I want to be able to `bit run`, but I don't want to trigger it's build, as I am focused only on the components, while the app itself will be built and released from a different workflow.\r\n  - Scenario 2 - I want to have a small component in my workspace as a basic \"consumer\" for my other components, and I don't want it published, as it is a testing environment for me and not a reuseable asset.\r\n\r\n### Improvements\r\n\r\n- Jest upgraded from 26 to 29 for all core environments (#9015, #9052)\r\n  - Only relevant for teams who either directly use, or customize the following: `teambit.react\u002Freact`, `teambit.harmony\u002Fnode`, `teambit.react\u002Freact-native`.\r\n- Support `--update-snapshot` option for `bit test`\r\n  - Requires updating your env, or `@teambit\u002Fdefender.jest-tester` and `@teambit\u002Fvite.vitest-tester` plugins if you have a custom env (#9025)\r\n- Quick search (`cmd+k`) now supports opening links in new tabs and few more UX updates (#9054)\r\n- Workspace starter (`bit new`) now supports creating custom envs and new components that use the new custom envs (#9036)\r\n- Add tooltip with full filename in file tree (#9066)\r\n- Add environments when initializing a workspace with `bit init --generator [envs]` option (#9064)\r\n- Add deprecation warning for teams using the Eslint\u002FPrettier aspects directly and not through the designated plugins (#9050)\r\n- Introduce `--force-ours` and `--force-theirs` options for `bit switch` to override files in the workspace instead of trying to merge (#9048)\r\n- `bit list` command marks deleted components, and also sorted alphabetically (#9042, #9041)\r\n\r\n### Performance\r\n\r\n- Support SSR for the Bit UI during `bit start` (#8915)\r\n- Avoid adding apps to `workspace.jsonc` during `bit create`, as this is no longer needed (and impacts command load time) (#9061, #9037)\r\n\r\n### Bug Fixes\r\n\r\n- Fix an issue where `bit create` for a component with existing name but different scope failed (#9082)\r\n- Fix an issue where `bit doctor` command exited upon any check failure (#9072)\r\n- Fix an issue where if a package is duplicate in runtime and dev and `bit deps remove --dev` was used, dependency wasn't removed (#9070)\r\n- Fix an issue where short-hash version was written to `.bitmap` instead of long-hash (#9067)\r\n- Fix an issue where tagging a pre-release allows for an illegal version name (#9063)\r\n- Fix several issues in generating automated API References (#9062, #9060)\r\n- Fix an issue where dependency version was not saved correctly (#9039)\r\n- Fix an issue where `bit show` listed incorrect version when `bit deps set` was used (#9035)\r\n- Fix and issue where dependency installation on `bit switch --main` fails when app is configured in `workspace.jsonc` but not in `.bitmap` (#9038)\r\n\r\n### Internal\r\n\r\n- Refactor build pipeline for core environments (#9055)\r\n- Prepare Bit for Cloud Workspaces (#9081, #9080, #9079, #9078, #9077, #9076, #9069, #9053, #9046, #9047, #9028)\r\n- Prepare for VSCode plugin upgrades (#9065)\r\n- Ability to have a Bit Aspect with a custom env (#9045)","2024-08-04T15:02:53",{"id":198,"version":199,"summary_zh":200,"released_at":201},314696,"v1.7.48","### Improvements\r\n\r\n- Block running the `build` process when component issue is detected, and print the issue (unless manually approved) (#9031)\r\n\r\n### Bug Fixes\r\n\r\n- Fix an issue where Bit removed `types` entry in `package.json` that an env defined (#9034)\r\n- Fix an issue where CSS\u002FSCSS parsing silently fails and not returning list of dependencies (#9033)\r\n- Fix an issue where imports with a pattern that returned an empty list resulted in stopping the entire import process (#9027)\r\n- Fix an issue where API Reference tab wasn't able to render method schema for functions that return jsx (#9019)\r\n- Fix OOM when `ArtifactStorageError` throws (#9014)\r\n\r\n### Internal\r\n\r\n- Update dependencies (#9020, #9026, #9011)\r\n- Refactor legacy code to modern components (#9029, #9024, #9023, #9016, #9018, #9021, #9017, #9010, #9012, #9013, #9000)","2024-07-16T12:10:20",{"id":203,"version":204,"summary_zh":205,"released_at":206},314679,"v1.13.21","### 新特性\n\n- 为 `bit import` 添加 `--owner` 标志，用于导入某个所有者的所有作用域中的所有组件，例如：`bit import teambit --owner` (#10133)\n- 为 Bit CLI 参考文档添加 Claude Code 技能 (#10138)\n- **工作区概览聚合**，用于展示聚合的工作区信息 (#10124)\n\n### 改进\n\n- 默认阻止已知不信任的包（`es5-ext`、`less`、`protobufjs`、`core-js`、`core-js-pure`）的 postinstall 脚本执行 (#10140)\n- 默认信任带有 postinstall 脚本的最流行包，使用 Bun 的默认白名单 (#10134)\n\n### 性能优化\n\n- 优化工作区图构建，仅惰性导入通过过滤器的依赖项，避免为被过滤掉的组件拉取庞大的依赖树 (#10127)\n\n### Bug 修复\n\n- 修复 Watchman Cookie 被放置在工作区根目录而非 `.bit` 目录的问题 (#10137)\n- 修复 `transpileComponent` 输出未复制到所有 dist 目录的问题 (#10136)\n- 修复 CLI 参考 MDX 中的特殊字符导致渲染问题的问题 (#10131)\n- 修复环境路径解析未回退到根组件目录的未版本化路径的问题 (#10125)\n- 修复重复的 `\u002F_hmr` 代理导致 WebSocket HMR 失败的问题 (#9804)\n- 修复当目录不存在时，Webpack 静态目录监视器会监视整个工作区的问题 (#10116)\n- 修复在 macOS 上使用多个 Bit 监视器时，FSEvents 流错误会自动检测并改用 Watchman 的问题 (#10115)\n\n### 内部改进\n\n- 添加 `FetchVersionHistory` 操作，用于在导出过程中轻量级获取版本历史，提升具有较长历史记录的组件的性能 (#10132)\n- 添加 `bit cli generate --skill` 命令，用于自动生成 Claude Code 技能参考文件 (#10139)\n- 将所有 MDX 使用更新至 v3 版本 (#10122)\n- 将核心环境更新至最新版本的 TypeScript 编译器，并修复 cross-env 的 tsconfig 问题 (#10135)\n- 添加生成发布说明的 Claude 技能 (#10123)","2025-12-31T14:18:58",{"id":208,"version":209,"summary_zh":210,"released_at":211},314680,"v1.13.5","### 新特性\n\n- 通过 Unix 套接字实现**共享的监视守护进程**，以提升文件监视效率 (#10102)\n- 在工作区 UI 中新增主题切换器，支持**深色主题** (#10090)\n- 为 **Astro** 框架添加依赖项检测器 (#10038)\n- `bit create` 命令支持在组件名称中指定作用域，例如 `bit create my-scope\u002Fmy-component` (#10088)\n- 为 `bit fork` 命令添加模式匹配支持，可一次性分叉多个组件 (#10094)\n- 为 `bit pattern` 命令新增 `--remote` 标志，用于远程作用域操作 (#10100)\n- 添加 `allowScripts` 配置项，用于控制依赖项脚本的执行 (#10007)\n- `bit doctor` 现已支持远程作用域及作用域验证检查 (#10067)\n\n### 破坏性变更\n\n- **默认禁止依赖项中的脚本** - 出于安全考虑，依赖项脚本现已被默认阻止。如需启用特定包的脚本，请在 `workspace.jsonc` 中使用 `allowScripts` 配置项 (#10108)\n\n### 改进\n\n- 工作区 UI 现可通过 postMessage 广播 URL 变更，以更好地与 iframe 集成 (#10051, #10054)\n- 改进分支导出验证的错误信息，新增 `TargetHeadNotFound` 错误 (#10047)\n- 将组件概览 UI 中的默认包管理器更改为 npm (#10062)\n- 对极简模式的 UI 进行优化 (#10063)\n- 将 `bit check-types` 命令中的 `--all` 标志替换为 `--unmodified`，以提高清晰度 (#10077)\n- 改进分支删除时的错误和提示信息 (#10076)\n- 清晰化 `bit delete` 命令中 `--lane` 标志的说明 (#10099)\n- 改进 FSEvents 错误信息，并提供可操作的建议 (#10111)\n- 改进安装脚本警告信息 (#10118)\n- 将问题绕过说明从错误信息移至 `component-issues` 命令的输出中 (#10041)\n\n### 性能优化\n\n- 仅对前 10 个快照组件计算依赖关系图，从而提升快照性能 (#10060)\n- 在 `getDivergeDataBetweenTwoSnaps` 中使用 Set 数据结构，以加快快照过滤速度 (#10085)\n\n### Bug 修复\n\n- 修复监视器无法从 FSEvents 缓冲区溢出中恢复的问题 (#10052)\n- 修复锁文件在写入文件系统之前未被验证的问题 (#10053)\n- 修复在合并未更改配置与自动依赖项时，`force:true` 依赖项未能保留的问题 (#10049)\n- 修复合并策略提示前加载器未停止的问题 (#10050)\n- 修复在 `snapFromScope` 过程中应用合并配置时，方面数据未能保留的问题 (#10056)\n- 修复分支合并过程中 `force:true` 依赖项未能保留的问题 (#10057)\n- 修复构建图时，组件 ID 未从哈希值转换为标签的问题 (#10058)\n- 修复裸作用域分支合并时，依赖项未更新为带有标签的合并版本的问题 (#10059)\n- 修复使用分离头时，未导出的主头版本未能一并导出的问题 (#10064)\n- 修复分支名称未转换为小写作为分支 ID 的问题 (#10070)\n- 修复 Jest 的 `testEnvironment` 未设置为 node 导致的问题","2025-12-10T12:10:38",{"id":213,"version":214,"summary_zh":215,"released_at":216},314681,"v1.12.158","### 新特性\n\n- 新增 `bit validate` 命令，可在提交到 CI 之前为项目运行完整的 `test`、`lint`、`compile` 和 `typecheck` 检查 (#10022)\n- 新增 **Bit 脚本**，用于组件的简单 Shell 命令或函数执行 (#10028)\n- 支持 pnpm 的 [`minimumReleaseAge`](https:\u002F\u002Fpnpm.io\u002Fsettings#minimumreleaseage) 和 [`minimumReleaseAgeExclude`](https:\u002F\u002Fpnpm.io\u002Fsettings#minimumreleaseageexclude)，以提升软件供应链安全性 (#10002)\n- 为 `workspace.jsonc` 添加 `externalPackageManager:true` 配置，使 Bit 将依赖管理交由 `package.jsonc` 处理 (#9821)\n\n### 改进\n\n- Bit MCP 更新 (#10004, #9967, #9965, #9963, #9953, #9951, #9952, #9980, #9979)\n  - 改进面向消费者的 `bit_component_details` 工具，包括批量支持和数据优化\n  - `bit_remote_search` 支持并行查询\n  - 更新规则模板\n  - 新增专用的 `bit_create` 工具\n- 对 `bit start` 的外观和交互进行小幅优化 (#9994, #9993, #9992, #9991, #9989, #9978, #9908, #10017)\n- `bit recover` 命令现支持组件及 glob 模式 (#10033)\n- `bit install` 支持组件 ID (#9930)\n- `bit run` 支持自动打开浏览器 (#9942, #9941)\n- 改善 CLI 中的错误信息 (#10027, #9983, #10020, #9987, #9937)\n\n### 性能\n\n- 在计算依赖图时，不再多次读取和解析 lockfile (#10019)\n\n### 修复的 Bug\n\n- 修复测试时长显示格式错误的问题 (#9940)\n- 修复组件负债中组件数量计算错误的问题 (#10021)\n- 修复 `package.json` 别名未被正确注册为依赖的问题 (#10011, #9975, #9955)\n- 修复 `env.jsonc` 中依赖项使用 `+` 符号时未正确注册的问题 (#10037)\n- 修复 `bit new` 无法解析远程环境的问题 (#9981)\n- 修复模式排除在使用否定模式时失效的问题 (#10031)\n- 修复 Windows 系统上创建的硬链接损坏的问题 (#10030)\n\n### 内部改进\n\n- 更新依赖项 (#10018, #10015, #10006, #10003, #10001, #9971, #9948, #9939, #9938, #9934, #9932, #9931, #9928, #9923, #10008, #9986, #9957, #9990, #9997, #10036, #9973, #9998, #9946, #10005, #9929, #10026, #9949)\n- 对部分遗留代码进行现代化改造 (#10024, #10014)\n- 在网络配置中新增记录慢速网络请求的日志设置 (#10016)","2025-10-15T12:05:14",{"id":218,"version":219,"summary_zh":220,"released_at":221},314682,"v1.12.67","进行中","2025-08-14T15:32:21",{"id":223,"version":224,"summary_zh":225,"released_at":226},314683,"v1.12.10","### 新特性\n\n- **实时控件预览**：可动态更改组件的预览状态，以不同方式查看组件渲染效果（#9776、#9772、#9766）\n- **Bit MCP 服务器**：更好地将 Bit 与您选择的 AI 助手集成（#9779、#9778、#9777、#9743、#9744、#9742、#9740、#9738、#9737、#9736、#9735、#9733、#9732、#9731、#9730、#9727、#9726、#9725、#9719、#9716、#9712、#9711、#9710、#9707、#9706、#9704、#9699、#9788、#9784、#9799、#9840）\n  - 运行 `bit mcp-server setup` 和 `bit mcp-server rules` 来添加配置和指令（请参阅 `--help` 了解文件位置及对助手的支持情况）\n  - `--consumer-project` 参数适用于 `setup` 和 `rules` 命令，帮助组件使用者查找并复用组件。\n  - 您的助手现在具备协助您创建、复用和维护 Bit 组件的能力。\n- 使用 `bit lane import ... --branch` 从远程车道创建 Git 分支（#9795）\n- `bit ci` 命令：简化并加速 CI 执行流程（#9844、#9838、#9836、#9833、#9834、#9835、#9831、#9832、#9812、#9810、#9811、#9825、#9797、#9803）\n- 在现有项目中添加 Bit 时，以“访客模式”初始化 Bit（#9824、#9787）\n  - 使用 `bit init --interactive` 进行交互式初始化\n  - 使用 `bit init --external-package-manager` 禁用 Bit 的依赖管理功能（或通过交互式界面操作）\n  - 简化开发工具配置\n\n### 改进\n\n- 简化 `bit link` 命令的 CLI 输出（#9802）\n\n### 性能优化\n\n- 优化未修改导出依赖项的构建封装体创建过程（#9820）\n\n### Bug 修复\n\n- 修复在识别工作区中可用应用时出现的多个问题（#9852、#9786）\n- 修复更新配置时 `workspace.jsonc` 文件中的注释未能保留的问题（#9851）\n\n### 内部改进\n\n- 更新依赖项（#9857、#9818、#9842、#9809、#9793、#9792、#9789、#9785）\n- 加速 Bit 的 CI 流程（#9823、#9814、#9807、#9808、#9806、#9805、#9801、#9790）","2025-07-24T11:08:42",{"id":228,"version":229,"summary_zh":220,"released_at":230},314684,"v1.11.24","2025-06-26T14:17:00",{"id":232,"version":233,"summary_zh":220,"released_at":234},314685,"v1.11.17","2025-06-17T09:31:06",{"id":236,"version":237,"summary_zh":238,"released_at":239},314690,"v1.9.75","### Improvements\r\n\r\n* Allow setting up per-workspace with `--local` option `bit config set user.token xxx --local`, or `--local-track` to have config in `workspace.jsonc` (#9557, #9555)\r\n* Support VScode extension to produce a visual workspace graph for components (#9547, #9545)\r\n* Allow for better control over component's `package.json` when running `bit compile` (#9530)\r\n* Enable auto-formatting components before snap\u002Ftag with `workspace.jsonc` config (#9497)\r\n  ```\r\n  \"teambit.defender\u002Fformatter\": {\r\n    \"formatOnPreSnap\": true\r\n  }\r\n  ```\r\n* Simplify getting `diff` from a version it's parent with `--parent`. Instead of `bit diff foo 0.0.1 0.0.2` you can `bit diff foo 0.0.2 --parent` (#9498)\r\n* Improve various CLI\u002FUI outputs and errors for better DX (#9507, #9502, #9506)\r\n* Support syntax highlighting for `.cjs` and `\u002Fmjs` (#9492)\r\n\r\n\r\n### Bug Fixes\r\n\r\n* Fix an issue where `bit login` didn't validate the token when it announced user is \"logged in\" (#9562)\r\n* Fix an issue where sometimes in workspace UI you can't compare past version with current changes (#9549)\r\n* Fix an issue where component data got mutated fix, avoid mutating scope aspects when loading a component from the workspace (#9551)\r\n* Fix an issue where `bit install` picked up unrelated `package.json` and installed dependencies from them (#9554)\r\n* Fix an issue where active component wasn't picked up correctly when URL had several query params (#9550)\r\n* Fix an issue where getting out-of-memory during `bit snap` due to high number of concurrent `add-dependencies-graph` (#9475)\r\n* Fix an issue where `artifacts` directory got into the generated component package (#9532)\r\n* Fix an issue where `bit start` HMR failed (#9534)\r\n* Fix an issue where running `bit checkout reset --all` to write removed components failed on a lane (#9533)\r\n* Fix an issue where `bit watch` didn't re-compile modified components  (#9523)\r\n* Fix an issue where API-reference didn't pick up on exported types (#9512)\r\n* Fix an issue where config-writer throws an error about `failed generating config files` after deleting `node_modules` (#9508)\r\n* Fix an issue where `bit server-forever` failed on Windows (#9499)\r\n* Fix and issue where plugin resolution path was incorrect and led to \"file not found\" errors (#9561)\r\n\r\n### Internal\r\n\r\n* Update dependencies (#9483, #9539, #9522, #9525, #9521, #9526, #9485, #9486, #9490, #9520, #9535)\r\n* Remove dependencies (#9484, #9536, #9538, #9519, #9501, #9518)\r\n* Move to node 22.14.0 (#9548)\r\n* Update component's envs for better suited compilation (#9503, #9529)\r\n* Remove some internal circular components (#9537)\r\n* Support no-op env, and env with no dev-services (#9504)\r\n* Move `NpmCiRegistry` class from the repo to e2e-helper component (#9558)\r\n* Refactoring (#9517, #9495, #9496, #9487)","2025-02-19T11:36:43",{"id":241,"version":242,"summary_zh":243,"released_at":244},314691,"v1.9.44","### Improvements\r\n\r\n- Support maintaining multiple versions\u002Fbranches on main-lane (#9362, #9345)\r\n- Add Harmony templates to default `workspace.jsonc` (#9449)\r\n- Allow checking out components where on a lane to quickly edit components (#9440)\r\n- Improve `bit import` fallback strategy when importing components in a lane to try and get the component from its original scope (#9428)\r\n- Improve various CLI\u002FUI outputs and errors for better DX (#9421, #9420, #9458, #9472, #9419, #9343, #9408, #9392, #9377, #9358, #9355, #9347, #9354)\r\n- Add sandbox mode for component preview in scope (#9366)\r\n\r\n### Bug Fixes\r\n\r\n- Fix many edge cases for the `env.jsonc` ability to `extend` and use external `env.jsonc` files as dependencies (#9257)\r\n- Fix an issue when running `tag --build` may not update build status correctly (#9477)\r\n- Fix an issue where navigating in API reference had incorrect routes from failed to serialize of some node signatures (#9474)\r\n- Fix an issue where component in a lane didn't get updates from the env, when the env in main (#9432)\r\n- Fix an issue where sometimes Bit assumes a component is new (#9411)\r\n- Fix an issue where during merge Bit may throw a \"version not found\" error (#9414)\r\n- Fix an issue where after `bit checkout` user needed to run `bit import` (#9409)\r\n- Fix an issue where after snap\u002Ftag some data on apps is not available (#9406)\r\n- Fix an issue where some commands may fail when user decided not to send analytics (#9382)\r\n- Fix an issue where env-url wasn't generated correctly when component modified in a lane  (#9341)\r\n- Fix an issue where sometimes `bit install -a` didn't work for new components (#9333)\r\n\r\n### Internal\r\n\r\n- Better handling of internal scope cache (#9435, #9434, #9399)\r\n- Improve handling of complex workspaces with various envs that compiled to multiple targets (ESM, CJS, etc) (#9400, #9415, #9402, #9397)\r\n- Optimize `preview` entry point and handle different files (#9348, #9426)\r\n- Set preview sandbox policy via API slot (#9454)\r\n- Use pre-bundle in build (#9351)\r\n- Ensure a single instance of `@teambit\u002Fbase-ui.graph.tree.collapsable-tree-node` (#9391)\r\n- Better handling of open ports (#9381)\r\n- Update dependencies (#9334, #8900, #9335, #9338, #9361, #9367, #9376, #9412, #9371, #9401, #9370, #9353, #9473, #9398, #9452, #9386, #9461, #9471, #9465, #9467, #9464, #9466, #9462, #9459, #9457, #9445, #9450, #9448, #9444, #9446, #9443, #9447, #9442, #9453, #9433)\r\n- Removed dependencies(#9342, #9369, #9210, #9456, #9455, #9375, #9416, #9423, #9422, #9418)\r\n- Refactor legacy code to modern components (#9384, #9478, #9344, #9352, #9356, #9359, #9373)\r\n- Remove unused code (#9437, #9439)\r\n- Add missing exports to cli esm.mjs (#9385)\r\n- Update env for core aspects (doctor, host-initializer) to the correct env (#9387)\r\n- Fix circular between constant and global-config legacy components (#9470)\r\n- Make the teambit.scope\u002Fobjects component a core-aspect (#9441)\r\n- Remove occurrences of v8 cache, which is not used anymore (#9390)\r\n- Keep per-component lockfile (#9427, #9388, #9214, #9396, #9339)","2025-01-20T14:35:49",{"id":246,"version":247,"summary_zh":248,"released_at":249},314692,"v1.8.127","## Improvements\r\n\r\n- `bit compile` and `bit watch` can generate types with `--generate-types` flag (#9308, #9314, #9301)\r\n- Support syntax highlighting for `.vue` files (#9282)\r\n- Support passing arguments to app dev server on `bit run` with `--args` option (eg `--args=\"--a=1 --b=2\"`) (#9216)\r\n- Component patterns support more complex selector on various commands (unlimited `AND`, multiple states and more) (#9235)\r\n- `bit stash` supports stashing new components with `--include-new` (#9273)\r\n- New experimental commands:\r\n  - Introduce a `bit lane history-diff` command to see the the history of all components on a given lane (#9285)\r\n  - Introduce a new `bit blame` command to show a per-line information on when it was last modified and by whom (#9271, #9272)\r\n- UI, CLI, error messages, outputs and various Dev-Ex improvements (#9297, #9217, #9311, #9275, #9260, #9293, #9283, #9245, #9291, #9238, #9302, #9288, #9248, #9294, #9284, #9241, #9316, #9250)\r\n\r\n## Bug Fixes\r\n\r\n- Make sure component history does not contain redundant information (#9281)\r\n- Fix an issue where dependencies marked as missing were not possible to be removed (#9265)\r\n- Fix an issue where components marked as `local-only` where still printed in the `snapped` or `pending` in `bit status` (#9266)\r\n- Fix an issue where fork information is not available before trying to extract it (#9229)\r\n- Fix an issue where in API-schema generation where functions weren't serialized correctly (#9258)\r\n- Ignore cases `bit deps-set` used to self-apply or remove \"self\" as a dependency (#9237)\r\n- Fix an issue where duplications occurred on a components auto-generated `package.json` (#9240)\r\n- Fix an issue where during switching lanes with `bit switch` command, redundant components were re-written (#9318)\r\n- Fix an issue where during `bit import` env configuration was removed from `component.json` (#9319)\r\n- Fix an issue where `bit install` crashed when it failed to delete unwanted items in `node_modules` (#9224)\r\n- Fix an issue where `bit start` failed when the same env with several version was used in a workspace (#9244)\r\n- Fix an issue where `ComponentNotFound` error was thrown on new components in various cases (#9317)\r\n- Fix an issue where `.DS_Store` was added to components (#9313)\r\n- Fix an issue where renamed components were not deleted upon lane merge (#9307)\r\n- Fix an issue where deleted components weren't reintroduced back into .bitmap after `bit reset` (#9300)\r\n- Fix an issue where `bit start` spinners abstracted errors (#9287)\r\n- Fix an error where outdated local index caused Bit to fail communicating with remote server (#9242)\r\n\r\n## Internal\r\n\r\n- Update dependencies (#9299, #9227, #9310, #9298, #9222, #9315, #9246, #9220, #9243, #9259, #9270)\r\n- Bit-Server improvements for IDE plugin (#9320, #9253, #9252, #9236, #9268, #9321, #9309, #9296, #9289, #9255, #9254, #9247, #9225, #9330, #9295, #9303, #9276, #9280, #9328)\r\n- Refactor old code and cleanups (#9324, #9326, #9325, #9323, #9322, #9306, #9261, #9286)\r\n- Avoid watching local-scope files on Windows (#9226)\r\n- Improve merge between workspace\u002Fscope config and global Bit config (#9231, #9223)\r\n- Ensure `package.json` is available in capsules root directory (#9329)\r\n- Improve error handling for aspect loading (#9263)","2024-11-26T15:48:44",{"id":251,"version":252,"summary_zh":253,"released_at":254},314693,"v1.8.68","### Improvements\r\n\r\n- Sort component IDs in `bit export` output, and introduce `--verbose` option to show which versions exported (#9219)\r\n- Add additional examples to `bit env set --help` (#9212)\r\n- Automated API reference now shows complete signature of every API node including docs (#9206)\r\n- Improve CSS\u002FSASS\u002FSCSS dependency detection to support `import ... as ...` and more (#9205)\r\n- `bit dependents` support `--json` option to get easily parse output by another process (#9204)\r\n- `bit build | snap | tag` supports `--skip-tasks` to skip any task from the build pipeline (#9196)\r\n- `bit test` exit with non-zero code when tester fails due to coverage (#9218)\r\n- Following commands and flags are no longer marked as experimental: (#9200)\r\n  - `bit fork --ast` `bit scope fork --ast` `bit rename --ast` `bit scope rename --ast` - use AST to transform component instead of regular expressions\r\n  - `bit recover` - recover component(s) soft-deleted from the workspace, or a remote scope\r\n  - `bit stash` - stash modified components\r\n  - `bit mini-status` - light and fast variation of `bit status`\r\n  - `bit dependencies --tree` - render dependencies as a tree, similar to `npm ls`.\r\n  - `bit lane rename` - change the lane-name locally\r\n  - `bit watch --check-types` - show errors\u002Fwarnings for types during `bit watch`\r\n\r\n### Bug Fixes\r\n\r\n- Fix an issue where if compilers did side-effects during build pipeline on `package.json`, these changes would not be in the generated `package.json` (#9207)\r\n- Fix an issue where the component-preview-template from the env was not included for core-environments (#9215)\r\n- Fix an issue where Bit tried to fetch local aspects from remote (#9208)\r\n\r\n### Internal\r\n\r\n- Fix many linting issues (#9209)\r\n- Remove `component.jsonc` files from some core components (#9211)\r\n- Update envs for core aspects (#9201)\r\n- Update dependencies (#9199, #9195, #9184, #9180, #9182)\r\n- Make the process of loading components and apps more robust (#9198, #9194)\r\n- Improve Scope garbage collect (#9193, #9192, #9190, #9189)\r\n- Add more APIs for VScode plugin to proxy for additional Bit commands (#9183)","2024-09-29T13:11:43"]