Skip to content

docs(en): merge docs-cn/sync-docs into docs-cn/dev @ b8458066#987

Open
docschina-bot wants to merge 5 commits into
devfrom
sync-b8458066-1
Open

docs(en): merge docs-cn/sync-docs into docs-cn/dev @ b8458066#987
docschina-bot wants to merge 5 commits into
devfrom
sync-b8458066-1

Conversation

@docschina-bot
Copy link
Copy Markdown
Collaborator

此 PR 自动生成。

合并 vitest-dev/docs-cn 的修改至本仓库(@ b845806

以下文件存在冲突,可能需要重新翻译:

请解决所有冲突后提交到此 pull request,可直接在 Github 修改、切换到 sync-b8458066-1 分支进行修改或者使用 Github Desktop 拉取此 pr 修改并提交。

禁止使用 Squash Merge 来合并此 Pull Request!

使用该操作会导致上游仓库的内容丢失,并致使下一次合并产生冲突。

@docschina-bot docschina-bot requested a review from elonehoo May 24, 2026 23:53
@netlify
Copy link
Copy Markdown

netlify Bot commented May 24, 2026

Deploy Preview for cn-vitest failed.

Name Link
🔨 Latest commit a9a776d
🔍 Latest deploy log https://app.netlify.com/projects/cn-vitest/deploys/6a138f8644c7af0008aa64cf

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a9a776d331

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

## browser.locators.exact <Version type="experimental">4.1.3</Version> {#browser-locators-exact}
## browser.locators.exact

<<<<<<< HEAD
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Remove unresolved merge-conflict markers from docs

This commit leaves raw merge-conflict markers (e.g. <<<<<<< HEAD / ======= / >>>>>>>) in multiple published docs pages, which causes users to see conflict noise and contradictory guidance (for example, competing defaults and duplicated headings) instead of a single canonical instruction set. Please resolve the conflicts and keep only one final version of each affected section before merging.

Useful? React with 👍 / 👎.

Comment thread releases.md

# Releases

Vitest releases follow [Semantic Versioning](https://semver.org/). You can see the latest stable version of Vitest in the [Vitest npm package page](https://www.npmjs.com/package/vite).
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Point Vitest release docs to the correct npm package

The "Vitest npm package page" link currently targets npmjs.com/package/vite, which sends readers to the Vite package and shows the wrong version/install context for Vitest. This makes the release guidance inaccurate for users trying to verify the latest Vitest version.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants