
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
browser-sync-webpack-plugin
Advanced tools
Supply Chain Security
Vulnerability
Quality
Maintenance
License
Easily use BrowserSync in your Webpack project.
$ 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.
BrowserSync will start only when you run Webpack in watch mode:
$ webpack --watch
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'] }
})
]
}
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 filesFeel free to open issues to propose stuff and participate. Pull requests are also welcome.
FAQs
BrowserSync and Webpack integration
The npm package browser-sync-webpack-plugin receives a total of 88,116 weekly downloads. As such, browser-sync-webpack-plugin popularity was classified as popular.
We found that browser-sync-webpack-plugin demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.