BrowserSync plugin for Webpack
Easily use BrowserSync in your Webpack project.
Install:
$ npm install --save-dev browser-sync-webpack-plugin
or
$ yarn add --dev browser-sync-webpack-plugin
With release of 2.0.0 the plugin is expected to be used in Node v4+ environment.
Support for Node v3 and lower was dropped, but you can install and use the plugin version of 1.2.0 in older environments.
Usage:
BrowserSync will start only when you run Webpack in watch mode:
$ webpack --watch
Basic:
If you're not using Webpack Dev Server, you can make BrowserSync to serve your project.
The setup is pretty easy: just pass the BrowserSync options to the plugin as the first argument.
In your webpack.config.js:
const BrowserSyncPlugin = require('browser-sync-webpack-plugin')
module.exports = {
// ...
plugins: [
new BrowserSyncPlugin({
// browse to http://localhost:3000/ during development,
// ./public directory is being served
host: 'localhost',
port: 3000,
server: { baseDir: ['public'] }
})
]
}
Advanced:
The advanced usage is about using Webpack Dev Server with BrowserSync in order to use awesome features of both.
To achieve this, BrowserSync offers the proxy option.
So, basically, you are about to proxy the output from the Webpack Dev Server through BrowserSync to get the best out of both.
In your webpack.config.js:
const BrowserSyncPlugin = require('browser-sync-webpack-plugin')
module.exports = {
// ...
plugins: [
new BrowserSyncPlugin(
// BrowserSync options
{
// browse to http://localhost:3000/ during development
host: 'localhost',
port: 3000,
// proxy the Webpack Dev Server endpoint
// (which should be serving on http://localhost:3100/)
// through BrowserSync
proxy: 'http://localhost:3100/'
},
// plugin options
{
// prevent BrowserSync from reloading the page
// and let Webpack Dev Server take care of this
reload: false
}
)
]
}
Other supported plugin options are:
name- default:bs-webpack-plugin, BrowserSync instance namecallback- default:undefined, BrowserSync instance init callback.injectCss- default:false, allows BrowserSync to inject changes inplace instead of reloading the page when changed chunks are all CSS files
Contributing:
Feel free to open issues to propose stuff and participate. Pull requests are also welcome.