DownloadA CLI dashboard for your webpack dev server. You can alternatively globally install the dashboard (e.g. npm install -g webpack-dashboard) for use with any project and everything should work the same. When choosing a custom port, you need to find one that is not already in use. You should not choose one that is being used by webpack-dev-server / devServer or any other process. Instead, pick one that is only for webpack-dashboard and pair that up in the plugin configuration and CLI port flag. We've standardized our local development process for webpack-dashboard on using yarn. We recommend using yarn 1.10.x+, as these versions include the integrity checksum. The checksum helps to verify the integrity of an installed package before its code is executed. We re-use a small handful of the fixtures from inspectpack so that you can work locally on the dashboard while simulating common node_modules dependency issues you might face in the wild.
Features
- Because sockets use a port, the constructor now supports passing an options object that can include a custom port
- Formidable is actively working on this project, and we expect to continue for work for the foreseeable future
- You can alternatively globally install the dashboard for use with any project and everything should work the same
- Webpack Dashboard works in Terminal, iTerm 2, and Hyper
- For mouse events, like scrolling, in Terminal you will need to ensure View → Enable Mouse Reporting is enabled
- Webpack Dashboard works in Command Prompt, PowerShell, and Linux Subsystem for Windows
Project Samples
