Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(configuration): move name option to correct place #6407

Merged
merged 4 commits into from
Sep 20, 2022
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/content/configuration/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ contributors:
- bigdawggi
- anshumanv
- textbook
- coly010
---

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.
Expand Down Expand Up @@ -56,6 +57,7 @@ W> Notice that many array configurations allow to reference the default value vi
const path = require('path');

module.exports = {
name: "my-config", // name of the configuration, shown in output
Coly010 marked this conversation as resolved.
Show resolved Hide resolved
<mode "/configuration/mode">
<default>
mode: "production", // "production" | "development" | "none"
Expand Down Expand Up @@ -178,8 +180,6 @@ module.exports = {
},
uniqueName: "my-application", // (defaults to package.json "name")
// unique name for this build to avoid conflicts with other builds in the same HTML
name: "my-config",
// name of the configuration, shown in output
<advancedOutput "#">
<default>
/* Advanced output configuration (click to show) */
Expand Down