Skip to content

docs(development): Mention runtimeChunk: single for multi-endpoint dev server #6098

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Apr 20, 2022
Merged

docs(development): Mention runtimeChunk: single for multi-endpoint dev server #6098

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
98f314a
Mention runtimeChunk: single for multi-endpoint dev server
f3ndot Apr 15, 2022
ebd02ea
Make it a tip, use "chapter" not "section"
f3ndot Apr 15, 2022
91edd5e
Add self to contributors
f3ndot Apr 15, 2022
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
6 changes: 6 additions & 0 deletions src/content/guides/development.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ contributors:
- chenxsan
- maxloh
- snitin315
- f3ndot
---

T> This guide extends on code examples found in the [Output Management](/guides/output-management) guide.
Expand Down Expand Up @@ -225,11 +226,16 @@ Change your configuration file to tell the dev server where to look for files:
path: path.resolve(__dirname, 'dist'),
clean: true,
},
+ optimization: {
+ runtimeChunk: 'single',
+ },
};
```

This tells `webpack-dev-server` to serve the files from the `dist` directory on `localhost:8080`.

T> The `optimization.runtimeChunk: 'single'` was added because in this example we have more than one entrypoint on a single HTML page. Without this, we could get into trouble described [here](https://bundlers.tooling.report/code-splitting/multi-entry/). Read the [Code Splitting](/guides/code-splitting/) chapter for more details.

T> `webpack-dev-server` serves bundled files from the directory defined in [`output.path`](/configuration/output/#outputpath), i.e., files will be available under `http://[devServer.host]:[devServer.port]/[output.publicPath]/[output.filename]`.

W> webpack-dev-server doesn't write any output files after compiling. Instead, it keeps bundle files in memory and serves them as if they were real files mounted at the server's root path. If your page expects to find the bundle files on a different path, you can change this with the [`devMiddleware.publicPath`](/configuration/dev-server/#devserverdevmiddleware) option in the dev server's configuration.
Expand Down