browser-sync not compatible with node 14+ due to outdated chokidar version using outdated fsevents
See original GitHub issueIssue details
├─┬ browser-sync@2.26.7 │ └─┬ chokidar@2.1.8 │ └── fsevents@1.2.13
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
Steps to reproduce/test case
- Install node 14+
- Add devDependency for browser-sync@2.26.7
- npm install to see warning
Please specify which version of Browsersync, node and npm you’re running
- Browsersync [2.26.7]
- Node [14.3.0]
- Npm [6.14.5]
Affected platforms
- linux
- windows
- macOS
- freebsd
- solaris
- other (please specify which)
Browsersync use-case
- API
- Gulp
- Grunt
- CLI
If CLI, please paste the entire command below
{cli command here}
for all other use-cases, (gulp, grunt etc), please show us exactly how you’re using Browsersync
{Browsersync init code here}
const browserSync = require('browser-sync').create();
browserSync.init({
open: false,
logFileChanges: false,
proxy: `localhost:${config.port}`,
ws: true,
middleware: [
webpackDevMiddleware(compiler, {
noInfo: false,
stats: {
assets: true,
cached: false,
cachedAssets: false,
children: false,
colors: true,
chunks: false,
chunkModules: false,
chunkOrigins: false,
depth: false,
env: false,
errors: true,
errorDetails: true,
hash: false,
modules: false,
performance: true,
reasons: false,
timings: false, // Redundant since gulp provides timing
warnings: false
}
})
],
port: config.browserSyncPort,
plugins: ['bs-fullscreen-message']
});
compiler.hooks.done.tap('ReloadDevices', stats => {
if(stats.hasErrors() || stats.hasWarnings()) {
return browserSync.sockets.emit('fullscreen:message', {
title: 'Webpack Error:',
body: stripAnsi(stats.toString()),
timeout: 100000 // 100 seconds
});
}
browserSync.reload();
});
Issue Analytics
- State:
- Created 3 years ago
- Reactions:28
- Comments:8
Top Results From Across the Web
Not compatible with your operating system or architecture
If you're getting ERR! not WARN a likely cause of this issue is that you're using a really outdated version of NPM.
Read more >Yarn dependencies outdated - sage - Roots Discourse
Hey guys, Seem to be getting a lot of warnings when running yarn on a fresh Sage install. Not to mention the node-sass...
Read more >This version has been deprecated - chokidar - npm
This version has been deprecated. Author message: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
Read more >Browsersync - Time-saving synchronised browser testing
Browsersync makes your browser testing workflow faster by synchronising URLs, interactions and code changes across multiple devices.
Read more >Folder "bower_components" is missing / Grunt not work ...
But i dont know must Grunt on the Webserver or on my client? ... hell is what this is) It may be an...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
:thumbleweed:
Node.js 14 is active LTS now: https://nodejs.org/en/about/releases/ Will this issue be fixed soon?