Merge branch 'cn' into sync-d054d465-1

Author: Yucohny

package.json

@@ -87,7 +87,7 @@
     "@babel/plugin-proposal-class-properties": "^7.17.12",
     "@babel/preset-env": "^7.19.4",
     "@babel/preset-react": "^7.18.6",
-    "@mdx-js/loader": "^2.0.0-next.9",
+    "@mdx-js/loader": "^2.3.0",
     "@octokit/auth-action": "^2.0.2",
     "@octokit/rest": "^19.0.5",
     "@pmmmwh/react-refresh-webpack-plugin": "next",
@@ -97,7 +97,7 @@
     "copy-webpack-plugin": "^11.0.0",
     "css-loader": "^6.7.1",
     "css-minimizer-webpack-plugin": "^4.2.2",
-    "cypress": "^10.11.0",
+    "cypress": "^12.7.0",
     "directory-tree": "^3.3.1",
     "directory-tree-webpack-plugin": "^1.0.3",
     "duplexer": "^0.1.1",
@@ -115,13 +115,13 @@
     "husky": "^8.0.1",
     "hyperlink": "^5.0.4",
     "jest": "^29.2.2",
-    "lightningcss": "^1.16.0",
+    "lightningcss": "^1.19.0",
     "lint-staged": "^13.0.3",
     "lodash": "^4.17.21",
     "markdownlint": "^0.26.2",
     "markdownlint-cli": "^0.32.2",
     "mdast-util-to-string": "^3.1.0",
-    "mini-css-extract-plugin": "^2.6.1",
+    "mini-css-extract-plugin": "^2.7.2",
     "mkdirp": "^1.0.4",
     "modularscale-sass": "^3.0.3",
     "node-fetch": "^3.2.10",
@@ -198,7 +198,7 @@
     "style-loader": "^3.3.1",
     "tailwindcss": "^3.2.1",
     "tap-spot": "^1.1.2",
-    "textlint": "^11.8.2",
+    "textlint": "^13.3.1",
     "textlint-rule-heading": "^1.0.10",
     "unist-util-visit": "^4.1.1",
     "webpack": "^5.74.0",

src/content/api/normalmodulefactory-hooks.mdx

@@ -86,7 +86,7 @@ NormalModuleFactory.hooks.someHook.for('identifier').tap(/* ... */);
 
 `HookMap<SyncBailHook>`
 
-在 `Parser` 实例创建后调用。`parserOptions` 是 [module.parser](/configuration/module/#moduleparser) 中对应标识符或空对象的选项。
+在 `Parser` 实例创建之前调用。`parserOptions` 是 [module.parser](/configuration/module/#moduleparser) 中对应标识符或空对象的选项。
 
 - 钩子参数：`identifier`
 
@@ -116,7 +116,7 @@ NormalModuleFactory.hooks.someHook.for('identifier').tap(/* ... */);
 
 `HookMap<SyncBailHook>`
 
-在 `Generator` 实例创建后调用。`generatorOptions` 是 [module.parser](/configuration/module/#modulegenerator) 中对应标识符或空对象的选项。
+在 `Generator` 实例创建之前调用。`generatorOptions` 是 [module.parser](/configuration/module/#modulegenerator) 中对应标识符或空对象的选项。
 
 - 钩子参数：`identifier`
 

src/content/concepts/under-the-hood.mdx

@@ -66,7 +66,7 @@ module.exports = {
 这会创建出两个名为 `home` 和 `about` 的 chunk 组。
 每个 chunk 组都有一个包含一个模块的 chunk：`./home.js` 对应 `home`，`./about.js` 对应 `about`
 
-> 一个 chunk 组中可能有多个 chunk。例如，[SplitChunksPlugin](/plugins/split-chunks-plugin/) 会将一个 chunk 拆分为一个或多个 chunk。
+> 一个 chunk 组中可能有多个 chunk。例如，[SplitChunksPlugin](/plugins/split-chunks-plugin/) 会将一个 chunk 组拆分为一个或多个 chunk。
 
 ## chunk $#chunks$
 

src/content/contribute/plugin-patterns.mdx

@@ -1,37 +1,40 @@
 ---
-title: Plugin Patterns
+title: 插件模式
 sort: 5
 contributors:
   - nveenjain
   - EugeneHlushko
   - benglynn
+  - Yucohny
+translators:
+  - jsbugwang
 ---
 
-Plugins grant unlimited opportunity to perform customizations within the webpack build system. This allows you to create custom asset types, perform unique build modifications, or even enhance the webpack runtime while using middleware. The following are some features of webpack that become useful while writing plugins.
+在 webpack 构建系统中，能够通过插件进行定制，这赋予了无限的可能性。这使你可以创建自定义资源类型，执行唯一的构建修改，甚至可以使用中间件来增强 webpack 运行时。下面是在编写插件时非常有用一些 webpack 的功能。
 
-## Exploring assets, chunks, modules, and dependencies $#exploring-assets-chunks-modules-and-dependencies$
+## 检索遍历资源、chunk、模块和依赖 $#exploring-assets-chunks-modules-and-dependencies$
 
-After a compilation is sealed, all structures within the compilation may be traversed.
+在执行完成编译的封存阶段后，编译的所有结构都可以遍历。
 
 ```javascript
 class MyPlugin {
   apply(compiler) {
     compiler.hooks.emit.tapAsync('MyPlugin', (compilation, callback) => {
-      // Explore each chunk (build output):
+      // 检索每个（构建输出的）chunk：
       compilation.chunks.forEach((chunk) => {
-        // Explore each module within the chunk (built inputs):
+        // 检索 chunk 中（内置输入的）的每个模块：
         chunk.getModules().forEach((module) => {
-          // Explore each source file path that was included into the module:
+          // 检索模块中包含的每个源文件路径：
           module.buildInfo &&
             module.buildInfo.fileDependencies &&
             module.buildInfo.fileDependencies.forEach((filepath) => {
-              // we've learned a lot about the source structure now...
+              // 我们现在已经对源结构有不少了解……
             });
         });
 
-        // Explore each asset filename generated by the chunk:
+        // 检索由 chunk 生成的每个资源文件名：
         chunk.files.forEach((filename) => {
-          // Get the asset source for each file generated by the chunk:
+          // 获取 chunk 生成的每个文件的资源源代码：
           var source = compilation.assets[filename].source();
         });
       });
@@ -43,21 +46,21 @@ class MyPlugin {
 module.exports = MyPlugin;
 ```
 
-- `compilation.modules`: A set of modules (built inputs) in the compilation. Each module manages the build of a raw file from your source library.
+- `compilation.modules`：编译后的（内置输入的）模块数组。每个模块管理控制来源代码库中的原始文件的构建。
 
-W> **Deprecation warning**: Array functions will still work.
+W> **弃用警告**：数组函数依然可用。
 
-- `module.fileDependencies`: An array of source file paths included into a module. This includes the source JavaScript file itself (ex: `index.js`), and all dependency asset files (stylesheets, images, etc) that it has required. Reviewing dependencies is useful for seeing what source files belong to a module.
-- `compilation.chunks`: A set of chunks (build outputs) in the compilation. Each chunk manages the composition of a final rendered assets.
+- `module.fileDependencies`：模块中引入的源文件路径构成的数组。这包括源 JavaScript 文件本身（例如：index.js）以及它所需的所有依赖资源文件（样式表、图像等）。审查依赖，可以用于查看一个模块有哪些从属的源文件。
+- `compilation.chunks`：编译后的（构建输出的）chunk 集合。每个 chunk 所管理控制的最终渲染资源的组合。
 
-W> **Deprecation warning**: Array functions will still work.
+W> **弃用警告**：数组函数依然可用。
 
-- `chunk.getModules()`: An array of modules that are included into a chunk. By extension, you may look through each module's dependencies to see what raw source files fed into a chunk.
-- `chunk.files`: A Set of output filenames generated by the chunk. You may access these asset sources from the `compilation.assets` table.
+- `chunk.getModules()`：chunk 中引入的模块构成的数组。通过扩展可以审查每个模块的依赖，来查看哪些原始源文件被注入到 chunk 中。
+- `chunk.files`：chunk 生成的输出文件名构成的集合。你可以从 `compilation.assets` 表中访问这些资源来源。
 
-### Monitoring the watch graph $#monitoring-the-watch-graph$
+### 监听观察图的修改 $#monitoring-the-watch-graph$
 
-While running webpack middleware, each compilation includes a `fileDependencies` `Set` (what files are being watched) and a `fileTimestamps` `Map` that maps watched file paths to a timestamp. These are extremely useful for detecting what files have changed within the compilation:
+运行 webpack 中间件时，每个编译包括一个 `fileDependencies` `Set`（正在观察哪些文件）和一个 `fileTimestamps` `Map`，它将被观察的文件路径映射到时间戳。这可以用于检测编译中哪些文件已经修改：
 
 ```javascript
 class MyPlugin {
@@ -85,15 +88,15 @@ class MyPlugin {
 module.exports = MyPlugin;
 ```
 
-You may also feed new file paths into the watch graph to receive compilation triggers when those files change. Add valid file paths into the `compilation.fileDependencies` `Set` to add them to the watched files.
+还可以将新文件路径添加到观察图中，以在这些文件修改时，接收消息和重新触发编译。只要将有效的文件路径推送到 `compilation.fileDependencies` `Set` 中，就可以将其添加到观察图中。
 
-T> The `fileDependencies` `Set` is rebuilt in each compilation, so your plugin must add its own watched dependencies into each compilation to keep them under watch.
+T> `fileDependencies` `Set` 在每次编译时都会重新构建，因此你的插件必须将自己要观察的依赖都推送到每次编译中，以使它们都处于观察中。
 
-W> Since webpack 5, `compilation.fileDependencies`, `compilation.contextDependencies` and `compilation.missingDependencies` are now a `Set` instead of a `Sortable Set` and thus no longer sorted.
+W> 从 webpack v5 开始, `compilation.fileDependencies`，`compilation.contextDependencies` 和 `compilation.missingDependencies` 是 `Set` 类型，而不是 `Sortable Set`，因此不再是有序的了。
 
-## Changed chunks $#changed-chunks$
+## 监听 chunk 的修改 $#changed-chunks$
 
-Similar to the watch graph, you can monitor changed chunks (or modules, for that matter) within a compilation by tracking their hashes.
+类似于观察图，监听 chunk（或者模块，就当前情况而言）的修改也很简单，通过在编译时跟踪它们的哈希来实现。
 
 ```javascript
 class MyPlugin {