Use webpack with a development server that provides live reloading. This should be used for development only.
It uses webpack-dev-middleware under the hood, which provides fast in-memory access to the webpack assets.
npm install webpack-dev-server --save-dev
The easiest way to use it is with the CLI. In the directory where your
webpack.config.js is, run:
This will start a server, listening on connections from
localhost on port
Now, when you change something in your assets, it should live-reload the files.
See the documentation for more use cases and options.
This project is heavily inspired by peerigon/nof5.
The client scripts are built with
npm run-script prepublish.
Run the relevant examples to see if all functionality still works. When introducing new functionality, also add an example. This helps the maintainers to understand it and check if it still works.
When making a PR, keep these goals in mind:
- The communication library (
SockJS) should not be exposed to the user.
- A user should not try to implement stuff that accesses the webpack filesystem, because this lead to bugs (the middleware does it while blocking requests until the compilation has finished, the blocking is important).
- It should be a development only tool (compiling in production is bad, one should precompile and deliver the compiled assets).
- There are hooks to add your own features, so we should not add less-common features.
- Processing options and stats display is delegated to webpack, so webpack-dev-server/middleware should not do much with it. This also helps us to keep up-to-date with webpack updates.
- The workflow should be to start webpack-dev-server as a separate process, next to the "normal" server and to request the script from this server or to proxy from dev-server to "normal" server (because webpack blocks the event queue too much while compiling which can affect "normal" server).