docs(cn): translate src/content/contribute/release-process.mdx and src/content/contribute/debugging.mdx (#1643)

Co-authored-by: Yucohny <yucohny@163.com>

Author: jsbugwang

src/content/contribute/debugging.mdx

@@ -1,72 +1,75 @@
 ---
-title: Debugging
+title: 调试
 sort: 7
 contributors:
   - skipjack
   - tbroadley
   - madhavarshney
   - bhavya9107
   - akaustav
+translators:
+  - jsbugwang
+  - Yucohny
 related:
-  - title: Learn and Debug webpack with Chrome DevTools!
+  - title: 使用 Chrome DevTools 学习和调试 webpack！
     url: https://medium.com/webpack/webpack-bits-learn-and-debug-webpack-with-chrome-dev-tools-da1c5b19554
-  - title: Debugging Guide | Node
+  - title: 调试指南 | Node
     url: https://nodejs.org/en/docs/guides/debugging-getting-started/
-  - title: Debugging Node.js with Chrome DevTools
+  - title: 用 Chrome DevTools 调试 Node.js
     url: https://medium.com/@paul_irish/debugging-node-js-nightlies-with-chrome-devtools-7c4a1b95ae27
 ---
 
-When contributing to the core repo, writing a loader/plugin, or even working on a complex project, debugging tools can be central to your workflow. Whether the problem is slow performance on a large project or an unhelpful traceback, the following utilities can make figuring it out less painful.
+在为核心仓库贡献代码，编写 loader/plugin，又或是处理复杂的项目时，调试工具将会成为工作流程的重心。无论问题是大型项目的性能下降还是无用追溯，以下工具都可以使这些问题变得不那么痛苦。
 
-- The [`stats` data](/api/stats) made available through [Node](/api/node/#stats-object) and the [CLI](/api/cli/#common-options).
-- Chrome **DevTools** via `node-nightly` and the latest Node.js versions.
+- [Node](/api/node/#stats-object) 和 [CLI](/api/cli/#common-options) 提供的 [`stats` 数据](/api/stats)。
+- `node-nightly` 和 Node.js 最新版本提供的 Chrome **DevTools**。
 
 ## Stats $#stats$
 
-Whether you want to sift through [this data](/api/stats) manually or use a tool to process it, the `stats` data can be extremely useful when debugging build issues. We won't go in depth here as there's an [entire page](/api/stats) dedicated to its contents, but know that you can use it to find the following information:
+无论你是想手动还是使用工具来筛选 [这些数据](/api/stats)，`stats` 数据在调试构建的问题时都非常有用。我们不会在此处深入介绍，请参阅 [此页面](/api/stats) 以了解详细内容。但应该知道可以使用它来查找以下信息：
 
-- The contents of every module.
-- The modules contained within every chunk.
-- Per module compilation and resolving stats.
-- Build errors and warnings.
-- The relationships between modules.
-- And much more...
+- 每个模块的内容。
+- 每个 chunk 中包含的模块。
+- 每个模块编译(compilation)和解析的 stats。
+- 构建错误和警告。
+- 模块之间的关系。
+- 其他更多……
 
-On top of that, the official [analyze tool](https://github.com/webpack/analyse) and [various others](/guides/code-splitting/#bundle-analysis) will accept this data and visualize it in various ways.
+最重要的是，[官方分析工具](https://github.com/webpack/analyse) 和 [各种其他分析工具](/guides/code-splitting/#bundle-analysis) 会将这些数据展示为多种形式的可视化图表。
 
 ## DevTools $#devtools$
 
-While [`console`](https://nodejs.org/api/console.html) statements may work well in straightforward scenarios, sometimes a more robust solution is needed. As most front-end developers already know, Chrome DevTools are a life saver when debugging web applications, _but they don’t have to stop there_. As of Node v6.3.0+, developers can use the built-in `--inspect` flag to debug a node program in DevTools.
+虽然在简单场景中，可能 [`console`](https://nodejs.org/api/console.html) 语句会表现良好，然而有时还需要更加强大的解决方案。正如大多数前端开发人员已经知道的，将 Chrome DevTools 用在调试 web 应用程序，是一个能够解救我们的实用工具，**但它并没有局限于调试 web 应用程序**。从 Node v6.3.0+ 开始，开发人员可以使用内置的 `--inspect` 标记以使用 DevTools 调试 Node.js 应用程序。
 
-This gives you the power to easily create breakpoints, debug memory usage, expose and examine objects in the console, and much more. In this short demo, we'll utilize the [`node-nightly`](https://github.com/hemanth/node-nightly) package which provides access to the latest and greatest inspecting capabilities.
+这可以帮助轻松创建断点、调试内存使用情况、在控制台中暴露和检查对象等。在这个简短的演示中，我们将利用 [`node-nightly`](https://github.com/hemanth/node-nightly) 包，它提供最新和强大的检测能力。
 
-W> The `--inspect` interface has been available since v6.3.0 so feel free to try it out with your local version, but be warned that certain features and flags may differ from the ones in this demo.
+W> 从 v6.3.0 开始，`--inspect` 接口就一直可用，因此可以尝试使用本地版本的 npm 包，但要注意某些功能和标记，可能与这里演示中的版本有所不同。
 
-Let's start by installing it globally:
+首先在全局安装：
 
 ```bash
 npm install --global node-nightly
 ```
 
-Now, we'll need to run it once to finish the installation:
+现在，需要运行一次以结束安装：
 
 ```bash
 node-nightly
 ```
 
-Now, we can use `node-nightly` along with the `--inspect` flag to start our build in any webpack-based project. Note that we cannot run NPM `scripts`, e.g. `npm run build`, so we'll have to specify the full `node_modules` path:
+现在，我们可以直接使用带有 `--inspect` 标记的 `node-nightly`，在任何基于 webpack 的项目中开始构建。注意，我们不应该运行 NPM `scripts`，例如 `npm run build`，所以需要指定完整的 `node_modules` 路径：
 
 ```bash
 node-nightly --inspect ./node_modules/webpack/bin/webpack.js
 ```
 
-Which should output something like:
+应该输出类似如下内容：
 
 ```bash
 Debugger listening on ws://127.0.0.1:9229/c624201a-250f-416e-a018-300bbec7be2c
 For help see https://nodejs.org/en/docs/inspector
 ```
 
-Now jump to `chrome://inspect` in the browser and you should see any active scripts you've inspected under the _Remote Target_ header. Click the "inspect" link under each script to open a dedicated debugger or the _Open dedicated DevTools for Node_ link for a session that will connect automatically. You can also check out the [NiM extension](https://chrome.google.com/webstore/detail/nodejs-v8-inspector-manag/gnhhdgbaldcilmgcpfddgdbkhjohddkj), a handy Chrome plugin that will automatically open a DevTools tab every time you `--inspect` a script.
+现在，在浏览器中访问 `chrome://inspect`，你会看到在 **Remote Target** 标题下可以进行审查（inspect）的活动脚本。单击每个脚本下自动连接会话的“inspect”链接，会打开一个专门用于 debugger 或 **Open dedicated DevTools for Node** 链接。除此之外还可以看到 [NiM 扩展程序](https://chrome.google.com/webstore/detail/nodejs-v8-inspector-manag/gnhhdgbaldcilmgcpfddgdbkhjohddkj)，这是一个方便的 Chrome 插件。每当通过 `--inspect` 调试某个脚本时，都会自动打开 DevTools 标签页。
 
-We recommend using the `--inspect-brk` flag which will break on the first statement of the script allowing you to go through the source to set breakpoints and start/stop the build as you please. Also, don't forget that you can still pass arguments to the script. For example, if you have multiple configuration files you could pass `--config webpack.prod.js` to specify the configuration you'd like to debug.
+我们推荐使用 `--inspect-brk` 标记，此标记将在脚本的第一条语句处断开，以便你可以在源代码中设置断点，并根据需要启动/停止构建。此外不要忘记仍然可以向脚本传递参数。例如，如果你有多个配置文件，你可以通过 `--config webpack.prod.js` 指定想要调试的配置。

src/content/contribute/release-process.mdx

@@ -1,28 +1,31 @@
 ---
-title: Release Process
+title: 发布流程
 sort: 6
 contributors:
   - d3viant0ne
   - sokra
   - byzyk
   - chenxsan
+translators:
+  - jsbugwang
+  - Yucohny
 ---
 
-The release process for deploying webpack is actually quite painless. Read through the following steps, so you have a clear understanding of how it's done.
+部署 webpack 的发布流程实际上非常简单。请阅读以下步骤，以了解清楚这些是如何完成的。
 
-## Pull Requests $#pull-requests$
+## 拉取请求（pull request） $#pull-requests$
 
-When merging pull requests into the `main` branch, select the _Create Merge Commit_ option.
+当向 `main` 分支上提交 pull request 时，选择 **Create Merge Commit** 选项。
 
 
-## Releasing $#releasing$
+## 发布 $#releasing$
 
 ```bash
 npm version patch && git push --follow-tags && npm publish
 npm version minor && git push --follow-tags && npm publish
 npm version major && git push --follow-tags && npm publish
 ```
 
-_This will increment the package version, commits the changes, cuts a **local tag**, push to github & publish the npm package._
+**这样将递增包版本号，提交变更，然后创建一个本地标签（tag），并推送到 GitHub，然后发布到 npm package**。
 
-After that go to the github [releases page](https://github.com/webpack/webpack/releases) and write a Changelog for the new tag.
+之后就可以到 GitHub 的 [发布页面](https://github.com/webpack/webpack/releases) 上为新的标签（tag）编写 Changelog。