I got a weird error running npm run watch using the latest LTS of Node, which is 10.
DONE Compiled successfully in 7880ms 7:56:42 PM
webpack: Compiled successfully.
internal/stream_base_commons.js:62
var err = req.handle.writev(req, chunks, allBuffers);
^
TypeError: req.handle.writev is not a function
at writevGeneric (internal/stream_base_commons.js:62:24)
at Socket._writeGeneric (net.js:711:5)
at Socket._writev (net.js:720:8)
at doWrite (_stream_writable.js:408:12)
at clearBuffer (_stream_writable.js:517:5)
at Socket.Writable.uncork (_stream_writable.js:314:7)
at connectionCorkNT (_http_outgoing.js:641:8)
at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! crestcenter@1.0.0 dev:client: `webpack-dev-server --config ./build/webpack.client.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the crestcenter@1.0.0 dev:client script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Worked fine until I refreshed the page. Googling the error presents results like these:
nodejs/node#21665
"Fixed" by running nvm use 8.
I got a weird error running
npm run watchusing the latest LTS of Node, which is 10.Worked fine until I refreshed the page. Googling the error presents results like these:
nodejs/node#21665
"Fixed" by running
nvm use 8.