Skip to content

Commit c88ec92

Browse files
Coly010chenxsan
andauthored
docs(configuration): move name option to correct place (#6407)
* docs(configuration): move `name` option to correct place The `name` option was listed under the `output` object which is incorrect. Move it to top-level configuration object. * docs(configuration): place `name` option at the top of config object * docs(configuration): fix spacing * docs(configuration): fix whitespace Co-authored-by: Sam Chen <chenxsan@gmail.com> Co-authored-by: Sam Chen <chenxsan@gmail.com>
1 parent ee5a23b commit c88ec92

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/content/configuration/index.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,7 @@ contributors:
1818
- bigdawggi
1919
- anshumanv
2020
- textbook
21+
- coly010
2122
---
2223

2324
Out of the box, webpack won't require you to use a configuration file. However, it will assume the entry point of your project is `src/index.js` and will output the result in `dist/main.js` minified and optimized for production.
@@ -56,6 +57,7 @@ W> Notice that many array configurations allow to reference the default value vi
5657
const path = require('path');
5758
5859
module.exports = {
60+
name: "my-config", // name of the configuration, shown in output
5961
<mode "/configuration/mode">
6062
<default>
6163
mode: "production", // "production" | "development" | "none"
@@ -178,8 +180,6 @@ module.exports = {
178180
},
179181
uniqueName: "my-application", // (defaults to package.json "name")
180182
// unique name for this build to avoid conflicts with other builds in the same HTML
181-
name: "my-config",
182-
// name of the configuration, shown in output
183183
<advancedOutput "#">
184184
<default>
185185
/* Advanced output configuration (click to show) */

0 commit comments

Comments
 (0)