@modern-js/module-tools-docs 2.0.2 → 2.2.0-beta.0

package/doc_build/static/js/async/en_guide_intro_welcome.js

@@ -14,14 +14,14 @@ __webpack_require__.r(__webpack_exports__);
 /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ = __webpack_require__("../../node_modules/.pnpm/react@18.2.0/node_modules/react/jsx-runtime.js");
 /*@jsxRuntime automatic @jsxImportSource react*/
 
-var frontmatter = {
+const frontmatter = {
   "sidebar_position": 1
 };
-var toc = [];
-var title = "Welcome to Module Tools";
-var content = "\"---\\nsidebar_position: 1\\n---\\n\\n# Welcome to Module Tools\\n\\nModule Tools is a modules engineering solution for Modern.js, as well as a core dependency. It allows developers to build, debug, and publish module type project more easily. A module type project can mostly be thought of as an npm package type project, which may be a component, component library or tool library project.\\n\\nIf you are planning to develop a project of the npm package type, then you came to the right place! Modern.js provides a professional module engineering solution. It gives you:\\n\\n- **Simple project initialization**: simply execute the `npx @modern-js/create project-dir` command, followed by a few interactive questions, to create a complete module type project. The created project also supports the choice of two package managers, [**pnpm**](https://pnpm.io/) and [**Yarn**](https://classic.yarnpkg.com/).\\n- **Code formatting**: In a module project, you can execute `modern lint` to format the code. The initialized module project includes the [ESLint](https://eslint.org/docs/latest/user-guide/core-concepts#what-is-eslint) ruleset for Modern.js for most scenarios.\\n- **Comprehensive build capabilities and faster builds**: Module Tools provides high-performance build capabilities based on [esbuild](https://esbuild.github.io/getting-started/) and [SWC](https://swc.rs/), and provides rich configurations for different build scenarios.\\n- **Storybook debugging tools**: Module Tools provides [Storybook](https://storybook.js.org/) debugging tools for debugging module projects. After installing the Storybook plugin for Module Tools, you can start it with the `modern dev storybook` command. You can use Storybook not only for debugging components, but also for other types of modules.\\n- **Testing capabilities with Jest**: When you need to test a module, you can use the `modern test` command of Module Tools, which not only integrates with [Jest](https://jestjs.io/), but also provides an API for configuring [Jest](https://jestjs.io/docs/configuration).\\n- **Versioning based on Changesets**: When you need to record changes to a project, you can use the `modern change` command to generate a Markdown file containing the changes; when you need to upgrade a project, you can use the `modern bump` command to analyze and upgrade the version through the Markdown file; when you need to release a project, you can use the `modern release` command to release the project; Module Tools implements these commands based on [Changesets](https://github.com/changesets/changesets).\\n- **Extensible plug-in mechanism**: Want to integrate additional debugging tools for your project? Or maybe you want to do some extra processing during the build process, Module Tools provides a plugin mechanism and plugin hooks that cover both the `dev` command and the `build` command process. You can use them to extend the capabilities of your project.\\n- **Lots more!** Module Tools will continue to optimize its build and debug features in the future. If there are important issues to be solved in module project building, or if a mainstream module project debugging tool or pattern emerges, then they will probably be supported by Module Tools.\\n\"";
+const toc = [];
+const title = `Welcome to Module Tools`;
+const content = "\"---\\nsidebar_position: 1\\n---\\n\\n# Welcome to Module Tools\\n\\nModule Tools is a modules engineering solution for Modern.js, as well as a core dependency. It allows developers to build, debug, and publish module type project more easily. A module type project can mostly be thought of as an npm package type project, which may be a component, component library or tool library project.\\n\\nIf you are planning to develop a project of the npm package type, then you came to the right place! Modern.js provides a professional module engineering solution. It gives you:\\n\\n- **Simple project initialization**: simply execute the `npx @modern-js/create project-dir` command, followed by a few interactive questions, to create a complete module type project. The created project also supports the choice of two package managers, [**pnpm**](https://pnpm.io/) and [**Yarn**](https://classic.yarnpkg.com/).\\n- **Code formatting**: In a module project, you can execute `modern lint` to format the code. The initialized module project includes the [ESLint](https://eslint.org/docs/latest/user-guide/core-concepts#what-is-eslint) ruleset for Modern.js for most scenarios.\\n- **Comprehensive build capabilities and faster builds**: Module Tools provides high-performance build capabilities based on [esbuild](https://esbuild.github.io/getting-started/) and [SWC](https://swc.rs/), and provides rich configurations for different build scenarios.\\n- **Storybook debugging tools**: Module Tools provides [Storybook](https://storybook.js.org/) debugging tools for debugging module projects. After installing the Storybook plugin for Module Tools, you can start it with the `modern dev storybook` command. You can use Storybook not only for debugging components, but also for other types of modules.\\n- **Testing capabilities with Jest**: When you need to test a module, you can use the `modern test` command of Module Tools, which not only integrates with [Jest](https://jestjs.io/), but also provides an API for configuring [Jest](https://jestjs.io/docs/configuration).\\n- **Versioning based on Changesets**: When you need to record changes to a project, you can use the `modern change` command to generate a Markdown file containing the changes; when you need to upgrade a project, you can use the `modern bump` command to analyze and upgrade the version through the Markdown file; when you need to release a project, you can use the `modern release` command to release the project; Module Tools implements these commands based on [Changesets](https://github.com/changesets/changesets).\\n- **Extensible plug-in mechanism**: Want to integrate additional debugging tools for your project? Or maybe you want to do some extra processing during the build process, Module Tools provides a plugin mechanism and plugin hooks that cover both the `dev` command and the `build` command process. You can use them to extend the capabilities of your project.\\n- **Lots more!** Module Tools will continue to optimize its build and debug features in the future. If there are important issues to be solved in module project building, or if a mainstream module project debugging tool or pattern emerges, then they will probably be supported by Module Tools.\\n\"";
 function _createMdxContent(props) {
-  var _components = Object.assign({
+  const _components = Object.assign({
     h1: "h1",
     a: "a",
     p: "p",
@@ -51,11 +51,15 @@ function _createMdxContent(props) {
           children: "npx @modern-js/create project-dir"
         }), " command, followed by a few interactive questions, to create a complete module type project. The created project also supports the choice of two package managers, ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
           href: "https://pnpm.io/",
+          target: "_blank",
+          rel: "nofollow",
           children: (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.strong, {
             children: "pnpm"
           })
         }), " and ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
           href: "https://classic.yarnpkg.com/",
+          target: "_blank",
+          rel: "nofollow",
           children: (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.strong, {
             children: "Yarn"
           })
@@ -66,7 +70,9 @@ function _createMdxContent(props) {
         }), ": In a module project, you can execute ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.code, {
           children: "modern lint"
         }), " to format the code. The initialized module project includes the ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
-          href: "https://eslint.org/docs/latest/user-guide/core-concepts#what-is-eslint",
+          href: "https://eslint.org/docs/latest/user-guide/core-concepts#what-is-eslint-1",
+          target: "_blank",
+          rel: "nofollow",
           children: "ESLint"
         }), " ruleset for Modern.js for most scenarios."]
       }), "\n", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxs)(_components.li, {
@@ -74,9 +80,13 @@ function _createMdxContent(props) {
           children: "Comprehensive build capabilities and faster builds"
         }), ": Module Tools provides high-performance build capabilities based on ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
           href: "https://esbuild.github.io/getting-started/",
+          target: "_blank",
+          rel: "nofollow",
           children: "esbuild"
         }), " and ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
           href: "https://swc.rs/",
+          target: "_blank",
+          rel: "nofollow",
           children: "SWC"
         }), ", and provides rich configurations for different build scenarios."]
       }), "\n", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxs)(_components.li, {
@@ -84,6 +94,8 @@ function _createMdxContent(props) {
           children: "Storybook debugging tools"
         }), ": Module Tools provides ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
           href: "https://storybook.js.org/",
+          target: "_blank",
+          rel: "nofollow",
           children: "Storybook"
         }), " debugging tools for debugging module projects. After installing the Storybook plugin for Module Tools, you can start it with the ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.code, {
           children: "modern dev storybook"
@@ -95,9 +107,13 @@ function _createMdxContent(props) {
           children: "modern test"
         }), " command of Module Tools, which not only integrates with ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
           href: "https://jestjs.io/",
+          target: "_blank",
+          rel: "nofollow",
           children: "Jest"
         }), ", but also provides an API for configuring ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
           href: "https://jestjs.io/docs/configuration",
+          target: "_blank",
+          rel: "nofollow",
           children: "Jest"
         }), "."]
       }), "\n", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxs)(_components.li, {
@@ -111,6 +127,8 @@ function _createMdxContent(props) {
           children: "modern release"
         }), " command to release the project; Module Tools implements these commands based on ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
           href: "https://github.com/changesets/changesets",
+          target: "_blank",
+          rel: "nofollow",
           children: "Changesets"
         }), "."]
       }), "\n", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxs)(_components.li, {
@@ -129,18 +147,14 @@ function _createMdxContent(props) {
     })]
   });
 }
-function MDXContent() {
-  var props = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : {};
-  var _ref = props.components || {},
-    MDXLayout = _ref.wrapper;
+function MDXContent(props = {}) {
+  const {wrapper: MDXLayout} = props.components || ({});
   return MDXLayout ? (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(MDXLayout, Object.assign({}, props, {
     children: (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_createMdxContent, props)
   })) : _createMdxContent(props);
 }
-_c = MDXContent;
 /* harmony default export */ __webpack_exports__["default"] = (MDXContent);
-var _c;
-__webpack_require__.$Refresh$.register(_c, "MDXContent");
+
 
 /***/ })
 

package/doc_build/static/js/async/en_guide_intro_welcome.js.map

@@ -1 +1 @@
-{"version":3,"file":"static/js/async/en_guide_intro_welcome.js","mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAIA;;AAEA;;AAEA;;;;AAEA;AAAA;;AAAA;;;AAAA;;AAAA;;;AAAA;;AAAA;;;AACA;AAAA;;AAAA;;AAAA;AAAA;;;AACA;AAAA;;AAAA;AAAA;;AAAA;AAAA;;;AACA;AAAA;;AAAA;AAAA;;AAAA;;;AACA;AAAA;;AAAA;;AAAA;AAAA;;AAAA;AAAA;;;AACA;AAAA;;AAAA;;AAAA;;AAAA;;AAAA;AAAA;;;AACA;AAAA;;AAAA;;AAAA;;;AACA;AAAA","sources":["webpack://@modern-js/module-tools-docs/./docs/en/guide/intro/welcome.md"],"names":[],"sourceRoot":""}
+{"version":3,"file":"static/js/async/en_guide_intro_welcome.js","mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAIA;;AAEA;;AAEA;;;;AAEA;AAAA;;AAAA;;;;;AAAA;;AAAA;;;;;AAAA;;AAAA;;;AACA;AAAA;;AAAA;;;;AAAA;AAAA;;;AACA;AAAA;;;;AAAA;AAAA;;;;AAAA;AAAA;;;AACA;AAAA;;;;AAAA;AAAA;;AAAA;;;AACA;AAAA;;AAAA;;;;AAAA;AAAA;;;;AAAA;AAAA;;;AACA;AAAA;;AAAA;;AAAA;;AAAA;;;;AAAA;AAAA;;;AACA;AAAA;;AAAA;;AAAA;;;AACA;AAAA","sources":["webpack://@modern-js/module-tools-docs/./docs/en/guide/intro/welcome.md"],"names":[],"sourceRoot":""}

package/doc_build/static/js/async/en_guide_intro_why-module-engineering-solution.js

@@ -14,14 +14,14 @@ __webpack_require__.r(__webpack_exports__);
 /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ = __webpack_require__("../../node_modules/.pnpm/react@18.2.0/node_modules/react/jsx-runtime.js");
 /*@jsxRuntime automatic @jsxImportSource react*/
 
-var frontmatter = {
+const frontmatter = {
   "sidebar_position": 2
 };
-var toc = [];
-var title = "Why module project solution";
-var content = "\"---\\nsidebar_position: 2\\n---\\n\\n# Why module project solution\\n\\nYou've probably all experienced it: when developing a component library or tool library from scratch, we have to consider not only how to write the code logic of the project itself, but also how to build, debug, test, format the code, and other things that have nothing to do with the code logic.\\n\\nFor example, when we consider which builder is used to build the code for a module project, we might previously consider [webpack](https://webpack.js.org/) or [Rollup](https://rollupjs.org/guide/en/), but now we might also consider [esbuild](https://esbuild.github.io/) or [SWC](https://swc.rs/).\\n\\nRegardless of which builder is chosen, this is going to be a costly learning curve for developers who are not skilled in the use of these build tools. Even if you want to use them quickly, it will take a lot of time and effort.\\n\\nIn addition to the build, things like providing debugging tools for projects, supporting testing capabilities, adding code format validation, etc. can take a long time and effort for a novice to understand or master them and actually serve the current project.\\n\\nTo ensure the quality of the code and the integrity of the project, we often need to do these things that are not related to the logical implementation of the code. However, these things are likely to affect the overall project development progress, reduce the developer's development experience, and make the developer feel that the development threshold of the module project is very high.\\n\\nIf you have to go through all this work every time you develop a module type project, you will spend most of your development time in the beginning on these things that are not related to code implementation. If we could provide a module engineering solution that would help developers to solve the project engineering issues and allow them to focus more on code implementation, it would greatly improve the module type project development experience.\\n\\n![Not using engineering solution vs. using engineering solution](https://lf3-static.bytednsdoc.com/obj/eden-cn/uhbfnupenuhf/module-tools/why-module-solution.png)\\n\\nModern.js, in order to make developing module type projects easier, provides a module engineering solution in order to solve the above mentioned problems and provides the main features using Module Tools. **Module-tools can be understood as a tool dedicated to the development of module type projects**.\\n\"";
+const toc = [];
+const title = `Why module project solution`;
+const content = "\"---\\nsidebar_position: 2\\n---\\n\\n# Why module project solution\\n\\nYou've probably all experienced it: when developing a component library or tool library from scratch, we have to consider not only how to write the code logic of the project itself, but also how to build, debug, test, format the code, and other things that have nothing to do with the code logic.\\n\\nFor example, when we consider which builder is used to build the code for a module project, we might previously consider [webpack](https://webpack.js.org/) or [Rollup](https://rollupjs.org/guide/en/), but now we might also consider [esbuild](https://esbuild.github.io/) or [SWC](https://swc.rs/).\\n\\nRegardless of which builder is chosen, this is going to be a costly learning curve for developers who are not skilled in the use of these build tools. Even if you want to use them quickly, it will take a lot of time and effort.\\n\\nIn addition to the build, things like providing debugging tools for projects, supporting testing capabilities, adding code format validation, etc. can take a long time and effort for a novice to understand or master them and actually serve the current project.\\n\\nTo ensure the quality of the code and the integrity of the project, we often need to do these things that are not related to the logical implementation of the code. However, these things are likely to affect the overall project development progress, reduce the developer's development experience, and make the developer feel that the development threshold of the module project is very high.\\n\\nIf you have to go through all this work every time you develop a module type project, you will spend most of your development time in the beginning on these things that are not related to code implementation. If we could provide a module engineering solution that would help developers to solve the project engineering issues and allow them to focus more on code implementation, it would greatly improve the module type project development experience.\\n\\n![Not using engineering solution vs. using engineering solution](https://lf3-static.bytednsdoc.com/obj/eden-cn/uhbfnupenuhf/module-tools/why-module-solution.png)\\n\\nModern.js, in order to make developing module type projects easier, provides a module engineering solution in order to solve the above mentioned problems and provides the main features using Module Tools. **Module-tools can be understood as a tool dedicated to the development of module type projects**.\\n\"";
 function _createMdxContent(props) {
-  var _components = Object.assign({
+  const _components = Object.assign({
     h1: "h1",
     a: "a",
     p: "p",
@@ -42,15 +42,23 @@ function _createMdxContent(props) {
     }), "\n", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxs)(_components.p, {
       children: ["For example, when we consider which builder is used to build the code for a module project, we might previously consider ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
         href: "https://webpack.js.org/",
+        target: "_blank",
+        rel: "nofollow",
         children: "webpack"
       }), " or ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
         href: "https://rollupjs.org/guide/en/",
+        target: "_blank",
+        rel: "nofollow",
         children: "Rollup"
       }), ", but now we might also consider ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
         href: "https://esbuild.github.io/",
+        target: "_blank",
+        rel: "nofollow",
         children: "esbuild"
       }), " or ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
         href: "https://swc.rs/",
+        target: "_blank",
+        rel: "nofollow",
         children: "SWC"
       }), "."]
     }), "\n", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.p, {
@@ -73,18 +81,14 @@ function _createMdxContent(props) {
     })]
   });
 }
-function MDXContent() {
-  var props = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : {};
-  var _ref = props.components || {},
-    MDXLayout = _ref.wrapper;
+function MDXContent(props = {}) {
+  const {wrapper: MDXLayout} = props.components || ({});
   return MDXLayout ? (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(MDXLayout, Object.assign({}, props, {
     children: (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_createMdxContent, props)
   })) : _createMdxContent(props);
 }
-_c = MDXContent;
 /* harmony default export */ __webpack_exports__["default"] = (MDXContent);
-var _c;
-__webpack_require__.$Refresh$.register(_c, "MDXContent");
+
 
 /***/ })
 

package/doc_build/static/js/async/en_guide_intro_why-module-engineering-solution.js.map

@@ -1 +1 @@
-{"version":3,"file":"static/js/async/en_guide_intro_why-module-engineering-solution.js","mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAIA;;AAEA;;AAEA;;AAAA;AAAA;;AAAA;AAAA;;AAAA;AAAA;;AAAA;AAAA;;AAEA;;AAEA;;AAEA;;AAEA;;;;;;;AAIA;AAAA;AAAA","sources":["webpack://@modern-js/module-tools-docs/./docs/en/guide/intro/why-module-engineering-solution.md"],"names":[],"sourceRoot":""}
+{"version":3,"file":"static/js/async/en_guide_intro_why-module-engineering-solution.js","mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAIA;;AAEA;;AAEA;;;;AAAA;AAAA;;;;AAAA;AAAA;;;;AAAA;AAAA;;;;AAAA;AAAA;;AAEA;;AAEA;;AAEA;;AAEA;;;;;;;AAIA;AAAA;AAAA","sources":["webpack://@modern-js/module-tools-docs/./docs/en/guide/intro/why-module-engineering-solution.md"],"names":[],"sourceRoot":""}

package/doc_build/static/js/async/{en_.js → en_index.js}

@@ -1,5 +1,5 @@
 "use strict";
-(self["webpackChunk_modern_js_module_tools_docs"] = self["webpackChunk_modern_js_module_tools_docs"] || []).push([["en_"],{
+(self["webpackChunk_modern_js_module_tools_docs"] = self["webpackChunk_modern_js_module_tools_docs"] || []).push([["en_index"],{
 
 /***/ "./docs/en/index.md":
 /***/ (function(__unused_webpack_module, __webpack_exports__, __webpack_require__) {
@@ -14,10 +14,10 @@ __webpack_require__.r(__webpack_exports__);
 /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ = __webpack_require__("../../node_modules/.pnpm/react@18.2.0/node_modules/react/jsx-runtime.js");
 /*@jsxRuntime automatic @jsxImportSource react*/
 
-var frontmatter = {
+const frontmatter = {
   "pageType": "home",
   "hero": {
-    "name": "Module tools",
+    "name": "Module Tools",
     "text": "Module engineering solutions",
     "tagline": "simple, powerful, high-performance modern npm package development solution",
     "actions": [{
@@ -44,15 +44,15 @@ var frontmatter = {
     "icon": "🛠️"
   }, {
     "title": "Extensible: Provides a powerful plugin mechanism",
-    "details": "With its plugin extension mechanism, you can easily extend the capabilities of Module tools.",
+    "details": "With its plugin extension mechanism, you can easily extend the capabilities of Module Tools.",
     "icon": "🎨"
   }]
 };
-var toc = [];
-var title = "index";
-var content = "\"---\\npageType: home\\n\\nhero:\\n  name: Module tools\\n  text: Module engineering solutions\\n  tagline: simple, powerful, high-performance modern npm package development solution\\n  actions:\\n    - theme: brand\\n      text: welcome\\n      link: /guide/intro/welcome\\n\\nfeatures:\\n  - title: 'Esbuild: The High Performance JS Bundler'\\n    details: Built on Esbuild, the build is extremely fast and gives you the ultimate development experience.\\n    icon: 🚀\\n  - title: 'Storybook: The community popular UI development tool'\\n    details: Integrated with Storybook, you can use it to debug UI.\\n    icon: 📦\\n  - title: 'transform + bundle'\\n    details: Both bundle and bundleless build modes are supported.\\n    icon: ✨\\n  - title: 'zero configuration'\\n    details: Develop your npm packages without any configuration, with built-in presets covering multiple scenarios.\\n    icon: 🛠️\\n  - title: 'Extensible: Provides a powerful plugin mechanism'\\n    details: With its plugin extension mechanism, you can easily extend the capabilities of Module tools.\\n    icon: 🎨\\n---\\n# index\\n\"";
+const toc = [];
+const title = `index`;
+const content = "\"---\\npageType: home\\n\\nhero:\\n  name: Module Tools\\n  text: Module engineering solutions\\n  tagline: simple, powerful, high-performance modern npm package development solution\\n  actions:\\n    - theme: brand\\n      text: welcome\\n      link: /guide/intro/welcome\\n\\nfeatures:\\n  - title: 'Esbuild: The High Performance JS Bundler'\\n    details: Built on Esbuild, the build is extremely fast and gives you the ultimate development experience.\\n    icon: 🚀\\n  - title: 'Storybook: The community popular UI development tool'\\n    details: Integrated with Storybook, you can use it to debug UI.\\n    icon: 📦\\n  - title: 'transform + bundle'\\n    details: Both bundle and bundleless build modes are supported.\\n    icon: ✨\\n  - title: 'zero configuration'\\n    details: Develop your npm packages without any configuration, with built-in presets covering multiple scenarios.\\n    icon: 🛠️\\n  - title: 'Extensible: Provides a powerful plugin mechanism'\\n    details: With its plugin extension mechanism, you can easily extend the capabilities of Module Tools.\\n    icon: 🎨\\n---\\n# index\\n\"";
 function _createMdxContent(props) {
-  var _components = Object.assign({
+  const _components = Object.assign({
     h1: "h1",
     a: "a"
   }, props.components);
@@ -66,20 +66,16 @@ function _createMdxContent(props) {
     }), "index"]
   });
 }
-function MDXContent() {
-  var props = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : {};
-  var _ref = props.components || {},
-    MDXLayout = _ref.wrapper;
+function MDXContent(props = {}) {
+  const {wrapper: MDXLayout} = props.components || ({});
   return MDXLayout ? (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(MDXLayout, Object.assign({}, props, {
     children: (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_createMdxContent, props)
   })) : _createMdxContent(props);
 }
-_c = MDXContent;
 /* harmony default export */ __webpack_exports__["default"] = (MDXContent);
-var _c;
-__webpack_require__.$Refresh$.register(_c, "MDXContent");
+
 
 /***/ })
 
 }]);
-//# sourceMappingURL=en_.js.map
+//# sourceMappingURL=en_index.js.map

package/doc_build/static/js/async/en_index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"static/js/async/en_index.js","mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA6BA","sources":["webpack://@modern-js/module-tools-docs/./docs/en/index.md"],"names":[],"sourceRoot":""}

package/doc_build/static/js/async/en_plugins_guide_getting-started.js

@@ -18,12 +18,12 @@ __webpack_require__.r(__webpack_exports__);
 /*@jsxRuntime automatic @jsxImportSource react*/
 
 
-var CH = {
+const CH = {
   annotations: _code_hike_mdx_dist_components_cjs_js__WEBPACK_IMPORTED_MODULE_1__.annotations,
   Spotlight: _code_hike_mdx_dist_components_cjs_js__WEBPACK_IMPORTED_MODULE_1__.Spotlight,
   CodeSlot: _code_hike_mdx_dist_components_cjs_js__WEBPACK_IMPORTED_MODULE_1__.CodeSlot
 };
-var chCodeConfig = {
+const chCodeConfig = {
   "staticMediaQuery": "not screen, (max-width: 768px)",
   "theme": {
     "name": "nord",
@@ -1186,16 +1186,16 @@ var chCodeConfig = {
   "autoImport": true,
   "showCopyButton": true,
   "skipLanguages": [],
-  "filepath": "/Users/bytedance/modern.js/website/module-tools/docs/en/plugins/guide/getting-started.mdx"
+  "filepath": "/Users/targeral/github/targeral-modern-js/website/module-tools/docs/en/plugins/guide/getting-started.mdx"
 };
-var frontmatter = {
+const frontmatter = {
   "sidebar_position": 1
 };
-var toc = [];
-var title = "Quick Start";
-var content = "\"---\\nsidebar_position: 1\\n---\\n\\n# Quick Start\\n\\nModule engineering solution not only provides a rich set of features, but also supports extending the capabilities of the current project by way of plugins.\\n\\nWe can quickly see how to write a module-tools plugin by using the following example.\\n\\n<CH.Spotlight>\\n\\n```md . /project\\n. /project .\\n├── plugins\\n│ └── example.ts\\n├── src/\\n└── modern.config.ts\\n```\\n\\n---\\n\\nFirst we create `. /plugins/example.ts` file under the initialized project.\\n\\n```md . /project\\n\\n```\\n\\n---\\n\\nNext add the code for the plugin to the `example.ts` file.\\n\\n```ts\\nimport type { CliPlugin, ModuleTools } from '@modern-js/module-tools';\\n\\nexport const ExamplePlugin = (): CliPlugin<ModuleTools> => {\\n  return {\\n    name: 'example',\\n    setup() {\\n      console.info('this is example plugin');\\n      return {\\n        // use hooks\\n        afterBuild() {\\n          console.info('build over');\\n        }\\n      };\\n    };\\n  };\\n};\\n```\\n\\n---\\n\\nThen we register the plugin we just wrote via the [`plugins`](/en/api/config/plugins) API.\\n\\n```ts . /modern.config.ts\\nimport { ExamplePlugin } from '. /plugins/example';\\nexport default defineConfig({\\n  plugins: [ExamplePlugin()],\\n});\\n```\\n\\n---\\n\\nFinally, run `modern build` and you will see.\\n\\n```bash terminal\\nThis is example plugin\\nBuild succeed: 510.684ms\\nbuild over\\n```\\n\\n</CH.Spotlight>\\n\\nWith the above example, we learned the following things.\\n\\n- The recommended plugin directory structure\\n- The initialization code of the plugin\\n- Plugin registration\\n\\nIn addition to the above, we also need to understand.\\n\\n- [plugin objects, type definitions and recommended configuration items](/en/plugins/guide/plugin-object)\\n- [setup functions, `api` object parameters, lifecycle hooks](/en/plugins/guide/setup-function)\\n\"";
+const toc = [];
+const title = `Quick Start`;
+const content = "\"---\\nsidebar_position: 1\\n---\\n\\n# Quick Start\\n\\nModule engineering solution not only provides a rich set of features, but also supports extending the capabilities of the current project by way of plugins.\\n\\nWe can quickly see how to write a module-tools plugin by using the following example.\\n\\n<CH.Spotlight>\\n\\n```md . /project\\n. /project .\\n├── plugins\\n│ └── example.ts\\n├── src/\\n└── modern.config.ts\\n```\\n\\n---\\n\\nFirst we create `. /plugins/example.ts` file under the initialized project.\\n\\n```md . /project\\n\\n```\\n\\n---\\n\\nNext add the code for the plugin to the `example.ts` file.\\n\\n```ts\\nimport type { CliPlugin, ModuleTools } from '@modern-js/module-tools';\\n\\nexport const ExamplePlugin = (): CliPlugin<ModuleTools> => {\\n  return {\\n    name: 'example',\\n    setup() {\\n      console.info('this is example plugin');\\n      return {\\n        // use hooks\\n        afterBuild() {\\n          console.info('build over');\\n        }\\n      };\\n    };\\n  };\\n};\\n```\\n\\n---\\n\\nThen we register the plugin we just wrote via the [`plugins`](/en/api/config/plugins) API.\\n\\n```ts . /modern.config.ts\\nimport { examplePlugin } from '. /plugins/example';\\nexport default defineConfig({\\n  plugins: [examplePlugin()],\\n});\\n```\\n\\n---\\n\\nFinally, run `modern build` and you will see.\\n\\n```bash terminal\\nThis is example plugin\\nBuild succeed: 510.684ms\\nbuild over\\n```\\n\\n</CH.Spotlight>\\n\\nWith the above example, we learned the following things.\\n\\n- The recommended plugin directory structure\\n- The initialization code of the plugin\\n- Plugin registration\\n\\nIn addition to the above, we also need to understand.\\n\\n- [plugin objects, type definitions and recommended configuration items](/en/plugins/guide/plugin-object)\\n- [setup functions, `api` object parameters, lifecycle hooks](/en/plugins/guide/setup-function)\\n\"";
 function _createMdxContent(props) {
-  var _components = Object.assign({
+  const _components = Object.assign({
     h1: "h1",
     a: "a",
     p: "p",
@@ -2180,7 +2180,7 @@ function _createMdxContent(props) {
                   }
                 }
               }, {
-                "content": "ExamplePlugin",
+                "content": "examplePlugin",
                 "props": {
                   "style": {
                     "color": "#D8DEE9"
@@ -2331,7 +2331,7 @@ function _createMdxContent(props) {
                   }
                 }
               }, {
-                "content": "ExamplePlugin",
+                "content": "examplePlugin",
                 "props": {
                   "style": {
                     "color": "#88C0D0"
@@ -2496,7 +2496,7 @@ function _createMdxContent(props) {
       }), (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxs)(react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.Fragment, {
         children: [(0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxs)(_components.p, {
           children: ["Then we register the plugin we just wrote via the ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
-            href: "/en/api/config/plugins.html",
+            href: "/module-tools/en/api/config/plugins.html",
             children: (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.code, {
               children: "plugins"
             })
@@ -2524,12 +2524,12 @@ function _createMdxContent(props) {
     }), "\n", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxs)(_components.ul, {
       children: ["\n", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.li, {
         children: (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.a, {
-          href: "/en/plugins/guide/plugin-object.html",
+          href: "/module-tools/en/plugins/guide/plugin-object.html",
           children: "plugin objects, type definitions and recommended configuration items"
         })
       }), "\n", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.li, {
         children: (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxs)(_components.a, {
-          href: "/en/plugins/guide/setup-function.html",
+          href: "/module-tools/en/plugins/guide/setup-function.html",
           children: ["setup functions, ", (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_components.code, {
             children: "api"
           }), " object parameters, lifecycle hooks"]
@@ -2538,21 +2538,17 @@ function _createMdxContent(props) {
     })]
   });
 }
-function MDXContent() {
-  var props = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : {};
-  var _ref = props.components || {},
-    MDXLayout = _ref.wrapper;
+function MDXContent(props = {}) {
+  const {wrapper: MDXLayout} = props.components || ({});
   return MDXLayout ? (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(MDXLayout, Object.assign({}, props, {
     children: (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_createMdxContent, props)
   })) : _createMdxContent(props);
 }
-_c = MDXContent;
 /* harmony default export */ __webpack_exports__["default"] = (MDXContent);
 function _missingMdxReference(id, component, place) {
-  throw new Error("Expected " + (component ? "component" : "object") + " `" + id + "` to be defined: you likely forgot to import, pass, or provide it." + (place ? "\nIt’s referenced in your code at `" + place + "` in `/Users/bytedance/modern.js/website/module-tools/docs/en/plugins/guide/getting-started.mdx`" : ""));
+  throw new Error("Expected " + (component ? "component" : "object") + " `" + id + "` to be defined: you likely forgot to import, pass, or provide it." + (place ? "\nIt’s referenced in your code at `" + place + "` in `/Users/targeral/github/targeral-modern-js/website/module-tools/docs/en/plugins/guide/getting-started.mdx`" : ""));
 }
-var _c;
-__webpack_require__.$Refresh$.register(_c, "MDXContent");
+
 
 /***/ })
 

package/doc_build/static/js/async/en_plugins_guide_plugin-object.js

@@ -18,11 +18,11 @@ __webpack_require__.r(__webpack_exports__);
 /*@jsxRuntime automatic @jsxImportSource react*/
 
 
-var CH = {
+const CH = {
   annotations: _code_hike_mdx_dist_components_cjs_js__WEBPACK_IMPORTED_MODULE_1__.annotations,
   Code: _code_hike_mdx_dist_components_cjs_js__WEBPACK_IMPORTED_MODULE_1__.Code
 };
-var chCodeConfig = {
+const chCodeConfig = {
   "staticMediaQuery": "not screen, (max-width: 768px)",
   "theme": {
     "name": "nord",
@@ -1185,12 +1185,12 @@ var chCodeConfig = {
   "autoImport": true,
   "showCopyButton": true,
   "skipLanguages": [],
-  "filepath": "/Users/bytedance/modern.js/website/module-tools/docs/en/plugins/guide/plugin-object.mdx"
+  "filepath": "/Users/targeral/github/targeral-modern-js/website/module-tools/docs/en/plugins/guide/plugin-object.mdx"
 };
-var frontmatter = {
+const frontmatter = {
   "sidebar_position": 2
 };
-var toc = [{
+const toc = [{
   "id": "plugin-type-definitions",
   "text": "Plugin type definitions",
   "depth": 2
@@ -1199,10 +1199,10 @@ var toc = [{
   "text": "Plugin configuration items",
   "depth": 2
 }];
-var title = "Plugin Object";
-var content = "\"---\\nsidebar_position: 2\\n---\\n\\n# Plugin Object\\n\\nThe module-tools plugin is an object, and the object contains the following properties.\\n\\n- `name`: The name of the plugin, a unique identifier.\\n- `setup`: plugin initialization function, which will be executed only once. setup function can return a [Hooks object](), and module-tools will execute the function corresponding to the Hook defined on the Hooks object at a specific time.\\n\\nFor example, in the following plugin code example, the `beforeBuild` function is triggered before the project starts the build task and the `build start` log is printed.\\n\\n<CH.Code>\\n\\n```ts . /plugins/demo.tsx\\nimport type { CliPlugin, ModuleTools } from '@modern-js/module-tools';\\n\\nconst MyPlugin: CliPlugin<ModuleTools> = {\\n  name: 'my-plugin',\\n\\n  setup() {\\n    return {\\n      // this is hook\\n      beforeBuild: () => {\\n        console.info('build start');\\n      },\\n    };\\n  },\\n};\\n```\\n\\n---\\n\\n```ts . /modern.config.ts\\nimport { MyPlugin } from '. /plugins/demo';\\nexport default {\\n  plugins: [MyPlugin()],\\n};\\n```\\n\\n</CH.Code>\\n\\n## Plugin type definitions\\n\\nWhen using TypeScript, you can introduce the built-in `CliPlugin` and `ModuleTools` types to provide the correct type derivation for plugins: ``\\n\\n```ts\\nimport type { CliPlugin, ModuleTools } from '@modern-js/module-tools';\\n\\nconst MyPlugin: CliPlugin<ModuleTools> = {\\n  name: 'my-plugin',\\n\\n  setup() {\\n    const foo = '1';\\n\\n    return {\\n      // this is hook\\n      afterBuild: () => {\\n        //...\\n      },\\n    };\\n  },\\n};\\n```\\n\\n## Plugin configuration items\\n\\n**It is recommended to write the plugin as a function**, so that the plugin can receive configuration items via function entry.\\n\\n```ts\\nimport type { CliPlugin, ModuleTools } from '@modern-js/module-tools';\\n\\ntype MyPluginOptions = {\\n  foo: string;\\n};\\n\\nconst MyPlugin = (options: MyPluginOptions): CliPlugin<ModuleTools> => ({\\n  name: 'my-plugin',\\n\\n  setup() {\\n    console.log(options.foo);\\n  },\\n});\\n```\\n\"";
+const title = `Plugin Object`;
+const content = "\"---\\nsidebar_position: 2\\n---\\n\\n# Plugin Object\\n\\nThe module-tools plugin is an object, and the object contains the following properties.\\n\\n- `name`: The name of the plugin, a unique identifier.\\n- `setup`: plugin initialization function, which will be executed only once. setup function can return a [Hooks object](), and module-tools will execute the function corresponding to the Hook defined on the Hooks object at a specific time.\\n\\nFor example, in the following plugin code example, the `beforeBuild` function is triggered before the project starts the build task and the `build start` log is printed.\\n\\n<CH.Code>\\n\\n```ts . /plugins/demo.tsx\\nimport type { CliPlugin, ModuleTools } from '@modern-js/module-tools';\\n\\nconst myPlugin: CliPlugin<ModuleTools> = {\\n  name: 'my-plugin',\\n\\n  setup() {\\n    return {\\n      // this is hook\\n      beforeBuild: () => {\\n        console.info('build start');\\n      },\\n    };\\n  },\\n};\\n```\\n\\n---\\n\\n```ts . /modern.config.ts\\nimport { myPlugin } from '. /plugins/demo';\\nexport default {\\n  plugins: [myPlugin()],\\n};\\n```\\n\\n</CH.Code>\\n\\n## Plugin type definitions\\n\\nWhen using TypeScript, you can introduce the built-in `CliPlugin` and `ModuleTools` types to provide the correct type derivation for plugins: ``\\n\\n```ts\\nimport type { CliPlugin, ModuleTools } from '@modern-js/module-tools';\\n\\nconst myPlugin: CliPlugin<ModuleTools> = {\\n  name: 'my-plugin',\\n\\n  setup() {\\n    const foo = '1';\\n\\n    return {\\n      // this is hook\\n      afterBuild: () => {\\n        //...\\n      },\\n    };\\n  },\\n};\\n```\\n\\n## Plugin configuration items\\n\\n**It is recommended to write the plugin as a function**, so that the plugin can receive configuration items via function entry.\\n\\n```ts\\nimport type { CliPlugin, ModuleTools } from '@modern-js/module-tools';\\n\\ntype MyPluginOptions = {\\n  foo: string;\\n};\\n\\nconst myPlugin = (options: MyPluginOptions): CliPlugin<ModuleTools> => ({\\n  name: 'my-plugin',\\n\\n  setup() {\\n    console.log(options.foo);\\n  },\\n});\\n```\\n\"";
 function _createMdxContent(props) {
-  var _components = Object.assign({
+  const _components = Object.assign({
     h1: "h1",
     a: "a",
     p: "p",
@@ -1415,7 +1415,7 @@ function _createMdxContent(props) {
                 }
               }
             }, {
-              "content": "MyPlugin",
+              "content": "myPlugin",
               "props": {
                 "style": {
                   "color": "#D8DEE9"
@@ -1882,7 +1882,7 @@ function _createMdxContent(props) {
                 }
               }
             }, {
-              "content": "MyPlugin",
+              "content": "myPlugin",
               "props": {
                 "style": {
                   "color": "#D8DEE9"
@@ -2019,7 +2019,7 @@ function _createMdxContent(props) {
                 }
               }
             }, {
-              "content": "MyPlugin",
+              "content": "myPlugin",
               "props": {
                 "style": {
                   "color": "#88C0D0"
@@ -2226,7 +2226,7 @@ function _createMdxContent(props) {
                   }
                 }
               }, {
-                "content": "MyPlugin",
+                "content": "myPlugin",
                 "props": {
                   "style": {
                     "color": "#D8DEE9"
@@ -2701,7 +2701,7 @@ function _createMdxContent(props) {
                   }
                 }
               }, {
-                "content": "MyPlugin",
+                "content": "myPlugin",
                 "props": {
                   "style": {
                     "color": "#D8DEE9"
@@ -2838,7 +2838,7 @@ function _createMdxContent(props) {
                   }
                 }
               }, {
-                "content": "MyPlugin",
+                "content": "myPlugin",
                 "props": {
                   "style": {
                     "color": "#88C0D0"
@@ -3059,7 +3059,7 @@ function _createMdxContent(props) {
                 }
               }
             }, {
-              "content": "MyPlugin",
+              "content": "myPlugin",
               "props": {
                 "style": {
                   "color": "#D8DEE9"
@@ -3799,7 +3799,7 @@ function _createMdxContent(props) {
                 }
               }
             }, {
-              "content": "MyPlugin",
+              "content": "myPlugin",
               "props": {
                 "style": {
                   "color": "#88C0D0"
@@ -4155,21 +4155,17 @@ function _createMdxContent(props) {
     })]
   });
 }
-function MDXContent() {
-  var props = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : {};
-  var _ref = props.components || {},
-    MDXLayout = _ref.wrapper;
+function MDXContent(props = {}) {
+  const {wrapper: MDXLayout} = props.components || ({});
   return MDXLayout ? (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(MDXLayout, Object.assign({}, props, {
     children: (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_createMdxContent, props)
   })) : _createMdxContent(props);
 }
-_c = MDXContent;
 /* harmony default export */ __webpack_exports__["default"] = (MDXContent);
 function _missingMdxReference(id, component, place) {
-  throw new Error("Expected " + (component ? "component" : "object") + " `" + id + "` to be defined: you likely forgot to import, pass, or provide it." + (place ? "\nIt’s referenced in your code at `" + place + "` in `/Users/bytedance/modern.js/website/module-tools/docs/en/plugins/guide/plugin-object.mdx`" : ""));
+  throw new Error("Expected " + (component ? "component" : "object") + " `" + id + "` to be defined: you likely forgot to import, pass, or provide it." + (place ? "\nIt’s referenced in your code at `" + place + "` in `/Users/targeral/github/targeral-modern-js/website/module-tools/docs/en/plugins/guide/plugin-object.mdx`" : ""));
 }
-var _c;
-__webpack_require__.$Refresh$.register(_c, "MDXContent");
+
 
 /***/ })