Open AdeptSEO opened 4 years ago
I have the same issue,
var stream = gulp.src(streamSource).pipe(webpack({ mode: 'production', stats: 'none', }))
can you look at this problem?
npm 6.11.13 node v10.16.3 gulp Local version: 4.02 gulp CLI version: 2.2.0
@shotlandec1980 why did you close this? Did you find a solution?
@eballeste Unfortunately, I did not find a solution ( I don’t know why, but there are no more errors) Оnly changed node.js to v12.18.0, but I don’t think that is the reason
@shotlandec1980 @sc-illiakovalenko is this still an issue? This occurs because https://nodejs.org/docs/latest-v12.x/api/domain.html is deprecated in node 12 and likely because a module in the dependency was using it. I don't see that deprecation message with node 12 so I'm guessing a module removed the deprecation.
@shama @shotlandec1980 Im getting this issue also after installing webpack-stream 6.1.2. It happens when I set the mode to production.
node.js: 12.8.4 npm: 6.14.6.
Update: I managed to get this to work on suddenly on my local environment when developing. I only managed to get this to fail few times and after switching between development and production mode it stopped throwing error anymore. I tested this on another computer also and same thing there. Didnt work first times and after few try with different modes it works.
However on my workplace CI pipeline it always fails. I'm starting to think is there something happening on background after few tries and it works. CI pipeline always starts building website from scratch and it fails always when mode is production.
gulp is using a module which uses 'domain' module that is deprecated. Latest and version later than node.js 14.6 shouldn't care about it but for some reason setting mode to "production" makes it break. No idea how these two are related.
mode: 'production' gives an error message
npm 6.13.7 node v13.11.0 gulp CLI version: 2.2.0 gulp Local version: 4.0.2