vitest-dev / vitest-dev/docs-cn
0.x 发布前准备
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 164
- Forks
- 109
- Avg merge
- 2h 30m
- Merged PRs (30d)
- 21
Description
[!CAUTION]
提交目标分支为v0
待处理页面
指南
- /guide/why
- /guide/
- /guide/features
- /guide/workspace
- /guide/cli
- /guide/filtering
- /guide/coverage
- /guide/snapshot
- /guide/mocking
- /guide/testing-types
- /guide/ui
- /guide/browser
- /guide/in-source
- /guide/test-context
- /guide/environment
- /guide/extending-matchers
- /guide/ide
- /guide/debugging
- /guide/comparisons
- /guide/migration
/guide/common-errors
API
- /api/
- /api/mock
- /api/vi
- /api/expect
- /api/expect-typeof
- /api/assert-type
配置
/config/
高级
- /advanced/api
- /advanced/runner
- /advanced/metadata
- /advanced/reporters
其他任务
- 旧版本警告
- public/assets
- package.json
- 英文版0.x link
- 中文版0.x link
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Work against the v0 target branch and review the listed guide, API, configuration, and advanced page paths first. Then check the remaining tasks for public/assets, package.json, version warnings, and English and Chinese 0.x links. Done means every checklist item is completed and the documentation is ready for the 0.x release.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100