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.

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

fix(dev-server): delete lazy and filename options #3716

Closed
wants to merge 2 commits into from
Closed

fix(dev-server): delete lazy and filename options #3716

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
812328c
fix(dev-server): delete lazy and filename options
hiroppy Apr 28, 2020
0c669b4
Merge branch 'master' into feature/remove-lazy-and-filename-in-dev-se…
EugeneHlushko Sep 29, 2020
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
59 changes: 2 additions & 57 deletions src/content/configuration/dev-server.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,7 @@ contributors:
- g100g
- anikethsaha
- snitin315
- hiroppy
---

[webpack-dev-server](https://github.com/webpack/webpack-dev-server) can be used to quickly develop an application. See the [development guide](/guides/development/) to get started.
Expand Down Expand Up @@ -354,35 +355,6 @@ webpack-dev-server --disable-host-check
```


## `devServer.filename` 🔑

`string`

This option lets you reduce the compilations in [lazy mode](#devserverlazy-).
By default in [lazy mode](#devserverlazy-), every request results in a new compilation. With `filename`, it's possible to only compile when a certain file is requested.

If [`output.filename`](/configuration/output/#outputfilename) is set to `'bundle.js'` and `devServer.filename` is used like this:

__webpack.config.js__

```javascript
module.exports = {
//...
output: {
filename: 'bundle.js'
},
devServer: {
lazy: true,
filename: 'bundle.js'
}
};
```

It will now only compile the bundle when `/bundle.js` is requested.

T> `filename` has no effect when used without [lazy mode](#devserverlazy-).


## `devServer.headers` 🔑

`object`
Expand Down Expand Up @@ -724,33 +696,6 @@ webpack-dev-server --inline=false
T> Inline mode is recommended for [Hot Module Replacement](/plugins/hot-module-replacement-plugin/) as it includes an HMR trigger from the websocket. Polling mode can be used as an alternative, but requires an additional entry point, `'webpack/hot/poll?1000'`.


## `devServer.lazy` 🔑

`boolean`

When `devServer.lazy` is enabled, the dev-server will only compile the bundle when it gets requested. This means that webpack will not watch any file changes. We call this __lazy mode__.

__webpack.config.js__

```javascript
module.exports = {
//...
devServer: {
lazy: true
}
};
```

Usage via the CLI

```bash
webpack-dev-server --lazy
```

T> [`watchOptions`](#devserverwatchoptions-) will have no effect when used with __lazy mode__.

T> If you use the CLI, make sure __inline mode__ is disabled.

## `devServer.liveReload`

`boolean = true`
Expand Down Expand Up @@ -1224,7 +1169,7 @@ webpack-dev-server --public myapp.test:80

The bundled files will be available in the browser under this path.

Imagine that the server is running under `http://localhost:8080` and [`output.filename`](/configuration/output/#outputfilename) is set to `bundle.js`. By default the `devServer.publicPath` is `'/'`, so your bundle is available as `http://localhost:8080/bundle.js`.
Imagine that the server is running under `http://localhost:8080` and the filename is set to `bundle.js`. By default the `devServer.publicPath` is `'/'`, so your bundle is available as `http://localhost:8080/bundle.js`.

Change `devServer.publicPath` to put bundle under specific directory:

Expand Down