Skip to content

Commit 2d699fd

Browse files
committed
docs: missing changes guides
1 parent 7caf114 commit 2d699fd

File tree

2 files changed

+8
-42
lines changed

2 files changed

+8
-42
lines changed

changes/per-environment-apis.md

Lines changed: 4 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -4,25 +4,12 @@
44
可以在 [环境 API 讨论](https://github.com/vitejs/vite/discussions/16358) 中向我们提供反馈
55
:::
66

7-
<<<<<<< HEAD
8-
ViteDevServer 中与模块图相关的多个 API 已经被更加独立的环境 API 所替代。
9-
10-
- `server.moduleGraph` -> [`environment.moduleGraph`](/guide/api-environment#separate-module-graphs)
11-
- `server.transformRequest` -> `environment.transformRequest`
12-
- `server.warmupRequest` -> `environment.warmupRequest`
13-
=======
14-
Multiple APIs from `ViteDevServer` related to module graph and modules transforms have been moved to the `DevEnvironment` instances.
15-
>>>>>>> d8c74e66bba83268fb86bc8aef187cf2a9f1be55
7+
`ViteDevServer` 中与 module graph 和 modules transforms 相关的多个 API 已移至 `DevEnvironment` 实例。
168

179
影响范围:`Vite 插件作者`
1810

19-
<<<<<<< HEAD
2011
::: warning 即将废弃
21-
环境实例首次在 `v6.0` 中引入。计划在 `v7.0` 中废弃现在的 `server.moduleGraph` 和其他方法。我们不建议你现在就放弃 server 方法。要识别你的使用情况,请在你的 vite 配置中设置以下。
22-
=======
23-
::: warning Future Deprecation
24-
The `Environment` instance was first introduced at `v6.0`. The deprecation of `server.moduleGraph` and other methods that are now in environments is planned for `v7.0`. We don't recommend moving away from server methods yet. To identify your usage, set these in your vite config.
25-
>>>>>>> d8c74e66bba83268fb86bc8aef187cf2a9f1be55
12+
`环境`实例首次在 `v6.0` 中引入。计划在 `v7.0` 中废弃现在的 `server.moduleGraph` 和其他方法。我们不建议你现在就放弃 server 方法。要识别你的使用情况,请在你的 vite 配置中设置以下。
2613

2714
```ts
2815
future: {
@@ -35,20 +22,12 @@ future: {
3522

3623
## 动机 {#motivation}
3724

38-
<<<<<<< HEAD
39-
// TODO: (保持原文)
40-
=======
41-
In Vite v5 and before, a single Vite dev server always had two environments (`client` and `ssr`). The `server.moduleGraph` had mixed modules from both of these environments. Nodes were connected through `clientImportedModules` and `ssrImportedModules` lists (but a single `importers` list was maintained for each). A transformed module was represented by an `id` and a `ssr` boolean. This boolean needed to be passed to APIs, for example `server.moduleGraph.getModuleByUrl(url, ssr)` and `server.transformRequest(url, { ssr })`.
25+
在 Vite v5 及之前的版本中,一个 Vite 开发服务器总是有两个环境(`client``ssr`)。`server.moduleGraph` 混合了来自这两个环境的模块。节点通过 `clientImportedModules``ssrImportedModules` 列表连接(但每种环境只维护一个 `importers` 列表)。转换后的模块由一个 `id` 和一个 `ssr` 布尔值表示。该布尔值需要传递给 API,例如 `server.moduleGraph.getModuleByUrl(url, ssr)``server.transformRequest(url, { ssr })`
4226

43-
In Vite v6, it is now possible to create any number of custom environments (`client`, `ssr`, `edge`, etc). A single `ssr` boolean isn't enough anymore. Instead of changing the APIs to be of the form `server.transformRequest(url, { environment })`, we moved these methods to the environment instance allowing them to be called without a Vite dev server.
44-
>>>>>>> d8c74e66bba83268fb86bc8aef187cf2a9f1be55
27+
在 Vite v6 中,现在可以创建任意数量的自定义环境(`client`, `ssr`, `edge`等)。单一的 `ssr` 布尔值已经不够用了。我们没有将 API 改为 `server.transformRequest(url, { environment })`,而是将这些方法移到了环境实例中,这样就可以在没有 Vite dev 服务器的情况下调用这些方法。
4528

4629
## 迁移指南 {#migration-guide}
4730

48-
<<<<<<< HEAD
49-
// TODO: (保持原文)
50-
=======
5131
- `server.moduleGraph` -> [`environment.moduleGraph`](/guide/api-environment#separate-module-graphs)
5232
- `server.transformRequest(url, ssr)` -> `environment.transformRequest(url)`
5333
- `server.warmupRequest(url, ssr)` -> `environment.warmupRequest(url)`
54-
>>>>>>> d8c74e66bba83268fb86bc8aef187cf2a9f1be55

changes/shared-plugins-during-build.md

Lines changed: 4 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,7 @@
44
可以在 [环境 API 讨论](https://github.com/vitejs/vite/discussions/16358) 中向我们提供反馈
55
:::
66

7-
<<<<<<< HEAD
8-
// TODO:(保持原文)
97
查看 [构建过程中的共享插件](/guide/api-environment.md#shared-plugins-during-build).
10-
=======
11-
See [Shared plugins during build](/guide/api-environment.md#shared-plugins-during-build).
12-
>>>>>>> d8c74e66bba83268fb86bc8aef187cf2a9f1be55
138

149
影响范围:`Vite 插件作者`
1510

@@ -19,18 +14,11 @@ See [Shared plugins during build](/guide/api-environment.md#shared-plugins-durin
1914

2015
## 动机 {#motivation}
2116

22-
<<<<<<< HEAD
23-
// TODO: (保持原文)
24-
=======
25-
Align dev and build plugin pipelines.
26-
>>>>>>> d8c74e66bba83268fb86bc8aef187cf2a9f1be55
17+
调整开发和构建插件管道。
2718

2819
## 迁移指南 {#migration-guide}
2920

30-
<<<<<<< HEAD
31-
// TODO: (保持原文)
32-
=======
33-
To be able to share plugins across environments, plugin state must be keyed by the current environment. A plugin of the following form will count the number of transformed modules across all environments.
21+
为实现跨环境共享插件,插件状态必须以当前环境为关键。以下形式的插件将计算所有环境中已转换模块的数量。
3422

3523
```js
3624
function CountTransformedModulesPlugin() {
@@ -50,7 +38,7 @@ function CountTransformedModulesPlugin() {
5038
}
5139
```
5240

53-
If we instead want to count the number of transformed modules for each environment, we need to keep a map:
41+
如果我们想要计算每个环境中已转换模块的数量,我们需要维护一个映射表。
5442

5543
```js
5644
function PerEnvironmentCountTransformedModulesPlugin() {
@@ -71,7 +59,7 @@ function PerEnvironmentCountTransformedModulesPlugin() {
7159
}
7260
```
7361

74-
To simplify this pattern, internally in Vite, we use a `usePerEnvironmentState` helper:
62+
为了简化这种模式,我们在 Vite 内部使用了 `usePerEnvironmentState` 助手:
7563

7664
```js
7765
function PerEnvironmentCountTransformedModulesPlugin() {
@@ -91,4 +79,3 @@ function PerEnvironmentCountTransformedModulesPlugin() {
9179
}
9280
}
9381
```
94-
>>>>>>> d8c74e66bba83268fb86bc8aef187cf2a9f1be55

0 commit comments

Comments
 (0)