├─┬ [email protected]
│ └─┬ [email protected]
│ └── [email protected]
npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
{cli command here}
{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();
});
:thumbleweed:
Node.js 14 is active LTS now: https://nodejs.org/en/about/releases/
Will this issue be fixed soon?
@nstuyvesant did you find any work around this issue ?
Is this being looked into?
@smares upgrading to webpack 5 from webpack 4 fixed for me.
But what does Webpack 5 have to do with this? 🤔
@smares you are the one with the problem, I'm just giving you solution mate.
"webpack-dev-middleware": "^4.1.0",
"webpack": "^5.24.2",
Most helpful comment
:thumbleweed: