chore(cnb): 开发环境
⚠️ No Changeset found
Latest commit: 3e4e694889b6f70d90a65c975fe69a7c9b4895b9
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
【预览链接】
- 完整版
- 基础
- 移动端
- 多实例
- 无工具栏
- 纯预览模式
- XSS 测试(默认禁用,需配置后允许)
- 图片编辑
- 表格编辑
- 自动编号标题
- 流式输入模式(AI chat 场景)
- VIM 编辑模式
- 使用自带或自定义的 Mermaid.js
- 自定义代码块外层容器
📦 cherry-markdown dev preview published
⚠️ 注意: 此版本为开发预览版,禁止在生产环境使用!
此方式引用代码中仍然可以使用
cherry-markdown包名,不需要修改现有的 import 语句
⚠️ Note: This version is a developer preview and should not be used in production environments!
This way of referencing allows you to still use the package name
cherry-markdown, no need to modify existing import statements
Install NPM with :
pnpm add cherry-markdown@npm:@cherry-markdown/[email protected]
yarn add cherry-markdown@npm:@cherry-markdown/[email protected]
npm i cherry-markdown@npm:@cherry-markdown/[email protected]
如果你使用了其他以 cherry-markdown 作为同等依赖(peer dependency)的元框架,你需要在 package.json 文件中覆盖 cherry-markdown 依赖,具体操作方式会因你使用的包管理器而略有不同
If you use a meta framework that has cherry-markdown as peer dependency, you have to override the cherry-markdown dependency in your package.json, which works slightly different depending on your package manager
# npm
{
"overrides": {
"cherry-markdown": "npm:@cherry-markdown/[email protected]"
}
}
# yarn
{
"resolutions": {
"cherry-markdown": "npm:@cherry-markdown/[email protected]"
}
}
# pnpm
{
"pnpm": {
"overrides": {
"cherry-markdown": "npm:@cherry-markdown/[email protected]"
}
}
}
在添加 overrides 之后,重新安装你的依赖并像往常一样启动你的开发服务器或构建你的项目即可,无需进一步的配置更改
After adding these overrides, reinstall your dependencies and start your development server or build your project as usual. No further configuration changes are required