Package Exports
- webpack-dev-server
- webpack-dev-server/bin/webpack-dev-server
- webpack-dev-server/bin/webpack-dev-server.js
- webpack-dev-server/client
- webpack-dev-server/client/index
- webpack-dev-server/client/index.bundle.js
- webpack-dev-server/client/index.js
- webpack-dev-server/client/live.bundle.js
- webpack-dev-server/client/live.html
- webpack-dev-server/client/overlay
- webpack-dev-server/client/socket
- webpack-dev-server/client/sockjs.bundle.js
- webpack-dev-server/lib/OptionsValidationError
- webpack-dev-server/lib/Server
- webpack-dev-server/lib/optionsSchema.json
- webpack-dev-server/lib/util/addDevServerEntrypoints
- webpack-dev-server/lib/util/createDomain
- webpack-dev-server/package.json
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (webpack-dev-server) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
webpack-dev-server
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.
Install
npm install webpack-dev-server --save-dev
Usage
The easiest way to use it is with the CLI. In the directory where your webpack.config.js
is, run:
node_modules/.bin/webpack-dev-server
This will start a server, listening on connections from localhost
on port 8080
.
Now, when you change something in your assets, it should live-reload the files.
See the documentation for more use cases and options.
Contributing
We appreciate all help! Check out CONTRIBUTING.md for more information on how to help.
Maintainers
Kees Kluskens |
Inspiration
This project is heavily inspired by peerigon/nof5.