gireeshpunathil
commented
6 years ago a minimal reproduce please?
Closed Jessidhia closed 6 years ago
gireeshpunathil
commented
6 years ago a minimal reproduce please?
MymmiJ
commented
6 years ago Not OP & don't have a minimal reproduce as such unfortunately, but I'm having the same problem on my local build (Mac OS X v 10.13.4) and others have verified on the same OS. Seems to happen on build while building the ttf2woff2 module, and while running it happens with some XHRs that timeout, but sometimes it just appears to fall over with no consistent pattern. It doesn't happen every time that we build using 10.6.0, but if it doesn't happen during build it always happens at some point while running, usually within 5-20 minutes.
Building the ttf2woff2 module is the longest stage of our build process and therefore it may be just a coincidence that this error tends to throw during this particular stage (i.e. it could happen any time but this is the time it's most likely to happen statistically), or it may be that long-running processes themselves cause the issue. This is about as helpful as I can get I'm afraid, it's all I can tell from where I'm sat.
We're currently just reverting to an earlier version, we haven't found a reliable workaround.
Jesseppi
commented
6 years ago Im getting the same issue. Version: 10.6.0 Platform: OSX HighSierra 10.13.6
when running webpack-dev-server, and seems to only happen when im accessing the page from IOS device.
addaleax
commented
6 years ago Since this already has 18 upvotes: Please provide a way to reproduce this. It seems like enough people are running into this issue to make that possible…
WesSouza
commented
6 years ago Boy this is complicated.
I was able to create a reproducible flow for this:
npm install this https://github.com/WesleydeSouza/subway-timeHTTPS=1 node scripts/start.jshttps://[IP]:3000
/eventsource repeatedly, which immediately crashes the server again.I'm on macOS 10.14 18A326h (Mojave), and tested on iOS 11.4 simulator and a device with iOS 12, always with the same results. Desktop Chrome doesn't trigger this problem.
danyim
commented
6 years ago I ran into this issue when I was running Node 10 in a new shell while trying to start a Node 7 project. Try rm -rf node_modules && nvm use 7 && yarn install if all else fails.
YvanGuidoin
commented
6 years ago Same issue running Node v10.7.0 on Ubuntu 18.04, with the latest webpack-dev-server, and accessing with Chromium
lundibundi
commented
6 years ago @YvanGuidoin is it possible for you to provide what are you actually running with the webpack-dev-server? As it seems that we may be able to reproduce your case much more easily than @WesleydeSouza one (I actually tried that one with MacOS in VBox but I guess it's outdated enough to not trigger this bug).
geminiyellow
commented
6 years ago same, webpack-dev-server down.
"webpack": "3.8.1",
"webpack-dev-server": "2.9.4",
WellspringCS
commented
6 years ago same. Windows 10 Node v10.7.0 using angular "@angular-devkit/build-angular": "~0.6.8", "@angular/cli": "^6.0.8", "@angular/compiler-cli": "6.0.9", rebooted my machine and the problem is gone.
For now.
YvanGuidoin
commented
6 years ago @lundibundi I can't give you access to the code sorry ;) but I cleaned our webpack config from the "private" parts so you can see it
const path = require("path");
const webpack = require("webpack");
const autoprefixer = require("autoprefixer");
const UglifyJsPlugin = require("uglifyjs-webpack-plugin");
const MiniCssExtractPlugin = require("mini-css-extract-plugin");
const HtmlWebpackPlugin = require("html-webpack-plugin");
const { BundleAnalyzerPlugin } = require("webpack-bundle-analyzer");
const CopyWebpackPlugin = require("copy-webpack-plugin");
const OfflinePlugin = require("offline-plugin");
const WebpackPwaManifest = require("webpack-pwa-manifest");
const LodashModuleReplacementPlugin = require("lodash-webpack-plugin");
const CleanWebpackPlugin = require("clean-webpack-plugin");
const confHotReload = {
contentBase: path.resolve(__dirname, "dist"),
compress: false,
historyApiFallback: true,
hot: true,
https: true,
index: "index.html",
open: false,
inline: true,
overlay: true,
watchOptions: {
poll: true,
ignored: [/node_modules/, "**/*.d.ts"],
},
port: 9000,
proxy: {
// some apis
},
};
const configProxy = {
target: "https://localhost/",
secure: false,
changeOrigin: true,
ws: true,
proxyTimeout: 60000,
};
const getPlugins = function getPlugins(isProd, isHot) {
const pluginsProduction = [
new CleanWebpackPlugin(["dist/*"]),
new LodashModuleReplacementPlugin(),
new OfflinePlugin({
appShell: "/",
externals: ["https://fonts.googleapis.com/css?family=Montserrat", "/"],
ServiceWorker: {
minify: true,
events: true,
},
autoUpdate: true,
AppCache: false,
excludes: ["**/*.d.ts", "**/locale/*.js"],
}),
new WebpackPwaManifest({
name: "Test",
short_name: "Test",
background_color: "#ffffff",
fingerprints: true,
inject: true,
theme_color: "#ff7f27",
start_url: "/",
icons: [
{
src: path.resolve("public/splash.png"),
sizes: [36, 128, 192, 256, 384, 512], // multiple sizes
},
],
}),
new BundleAnalyzerPlugin({
analyzerMode: "static",
openAnalyzer: false,
logLevel: "error",
}),
];
const commonsPlugins = [
new webpack.DefinePlugin({
"process.env": {
NODE_ENV: JSON.stringify(isProd ? "production" : "development"),
BROWSER: true,
},
DOMAIN_API: JSON.stringify(process.env.DOMAIN_API),
}),
new webpack.IgnorePlugin(/^\.\/locale$/, /moment$/), // not included in bundle
new HtmlWebpackPlugin({
template: "public/index.html",
filename: "index.html",
inject: true,
chunksSortMode: "none",
cache: isHot,
minify: {
preserveLineBreaks: true,
html5: true,
removeComments: false,
collapseWhitespace: true,
},
favicon: "public/favicon.png",
}),
new HtmlWebpackPlugin({
template: "public/unsupported.html",
filename: "unsupported.html",
inject: false,
chunksSortMode: "none",
cache: isHot,
minify: {
preserveLineBreaks: true,
html5: true,
removeComments: false,
collapseWhitespace: true,
},
favicon: "public/favicon.png",
}),
new MiniCssExtractPlugin({
filename: "[name].css",
chunkFilename: "[id].css",
}),
new CopyWebpackPlugin([
{
context: "node_modules/moment/locale",
from: "*",
to: "./locale/",
},
{
context: "node_modules/videojs-contrib-hls/dist",
from: "videojs-contrib-hls.min.js",
to: "./videojs/",
},
{
context: "node_modules/video.js/dist",
from: "video.min.js",
to: "./videojs/",
},
{
context: "public/",
from: "robots.txt",
to: ".",
},
]),
];
if (isHot) {
commonsPlugins.push(new webpack.HotModuleReplacementPlugin());
}
const pluginsToUse = isProd ? [...commonsPlugins, ...pluginsProduction] : commonsPlugins;
return pluginsToUse;
};
const aliases = {
moment$: "moment/moment",
"react-loadable": "@7rulnik/react-loadable",
// ... private aliases for modules
};
const webpackStatsProd = {
children: true,
chunks: false,
chunkModules: false,
chunkOrigins: false,
optimizationBailout: true,
source: false,
};
module.exports = function(env) {
const isHot = (env && env.hot) || false;
const isProd = (!isHot && (env && env.production)) || false;
const pluginsToUse = getPlugins(isProd, isHot);
return {
cache: !isProd,
devtool: false,
mode: !isProd ? "development" : "production",
stats: isProd ? webpackStatsProd : "minimal",
entry: path.resolve(__dirname, "src", "check.ts"),
output: {
path: path.resolve(__dirname, "dist"),
filename: isProd ? "[chunkhash].js" : "[name].bundle.js",
chunkFilename: isProd ? "[chunkhash].chunk.js" : "[name].chunk.js",
pathinfo: !isProd,
},
devServer: confHotReload,
performance: {
hints: isProd ? "warning" : false,
},
optimization: {
splitChunks: { chunks: "all", cacheGroups: {} },
sideEffects: false,
minimize: isProd,
minimizer: [
new UglifyJsPlugin({
uglifyOptions: {
ecma: 7,
},
cache: false,
parallel: true,
sourceMap: false,
}),
],
runtimeChunk: false,
concatenateModules: isProd,
},
resolve: {
extensions: [".tsx", ".ts", ".jsx", ".js", ".json"],
mainFields: ["module", "browser", "main"],
alias: aliases,
modules: [path.resolve(__dirname, "node_modules")],
},
target: "web",
module: {
rules: [
{
test: function(modulePath) {
return (
modulePath.endsWith(".ts") | modulePath.endsWith(".tsx") &&
!(modulePath.endsWith("test.ts") | modulePath.endsWith("test.tsx"))
);
},
use: [
{
loader: "babel-loader",
options: {
cacheDirectory: !isProd,
},
},
"ts-loader",
],
include: /src/,
exclude: /node_modules/,
},
{
test: /\.(js|jsx)$/,
use: {
loader: "babel-loader",
options: {
cacheDirectory: !isProd,
},
},
include: /src/,
exclude: /node_modules/,
},
{
test: /\.css$/,
use: [
isHot ? { loader: "style-loader", options: { hmr: true } } : MiniCssExtractPlugin.loader,
{ loader: "css-loader", options: { minimize: isProd } },
// {
// loader: "postcss-loader",
// options: {
// plugins: [autoprefixer],
// },
// },
],
},
{
test: /\.scss$/,
use: [
isHot ? { loader: "style-loader", options: { hmr: true } } : MiniCssExtractPlugin.loader,
{
loader: "typings-for-css-modules-loader",
query: {
modules: true,
localIdentName: isProd ? "[hash:base64:10]" : "[name]__[local]",
camelCase: false,
namedExport: true,
banner:
"// This file is automatically generated by typings-for-css-modules.\n// Please do not change this file!",
},
},
{
loader: "postcss-loader",
options: {
plugins: [autoprefixer],
},
},
{
loader: "sass-loader",
query: {
modules: true,
},
},
],
},
{
test: /\.(jpe?g|png|gif|ogg|mp4|woff|woff2|ttf|eot)$/i,
use: {
loader: "file-loader",
options: {
name: "[name].[ext]",
outputPath: "assets/",
},
},
},
{
test: /\.svg/,
use: [
{
loader: "file-loader",
options: {
name: "[name].[ext]",
outputPath: "assets/",
},
},
{
loader: "svgo-loader",
options: {
plugins: [
{ removeTitle: true },
{ cleanupAttrs: true },
{ removeComments: true },
{ removeUnknownsAndDefaults: true },
{ removeDesc: true },
{ convertColors: { shorthex: false } },
{ convertPathData: false },
],
},
},
],
},
],
},
plugins: pluginsToUse,
};
};and the error I have
ℹ ｢wdm｣: Compiled successfully.
internal/stream_base_commons.js:59
var err = req.handle.writev(req, chunks, allBuffers);
^
TypeError: req.handle.writev is not a function
at writevGeneric (internal/stream_base_commons.js:59:24)
at Socket._writeGeneric (net.js:759:5)
at Socket._writev (net.js:768: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:644:8)
at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR!<[project]>@1.1.0 start: `DOMAIN_API=localhost:9000 webpack-dev-server --env.hot`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the <[project]>@1.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.Edit: Two of webpack dev server proxy path are used for Websocket connections to our backend launched in Docker locally, don't know if that might have an impact?
addaleax
commented
6 years ago @YvanGuidoin Do you think you could work out a full reproduction based on this?
YvanGuidoin
commented
6 years ago @addaleax Tried to recreate a cleaned reproduction, but it isn't happening wihout the backend, and tried to recreate it with clean code (create-react-app) and a websocket server it's not happening either (even when calling 9/10 websocket in parallel per browser) ><
addaleax
commented
6 years ago @YvanGuidoin Can you provide other information about the issue? Maybe you could attach the inspector to the Node process and see what the actual values of req.handle/req.handle.writev are?
YvanGuidoin
commented
6 years ago @addaleax yes I can, and if you have the time we can look at it together on our actual code, I haven't dwelled into the node inspector for now, so maybe your insight would make it faster.
I just tested and it seems to be fired almost each time, I know where to put the debugger to have the req values, but it is a circular structure so I can't get you a JSON of it.
addaleax
commented
6 years ago @YvanGuidoin Hm, okay … maybe, alternatively, do you think you could patch Node.js yourself do to some debugging? E.g. add if (typeof req.handle.writev !== 'function') console.log(req.handle) before the offending line?
karneaud
commented
6 years ago +1 for this error as well below is a link I had posted to stack
https://stackoverflow.com/questions/51567590/req-handle-writev-is-not-a-function
thought it was something I was doing wrong with React.
addaleax
commented
6 years ago Has anyone been able to come up with a reproduction that does not require access to an iOS simulator?
Has anyone tried to raise this issue at https://github.com/webpack/webpack-dev-server, since it only seems to affect this one particular CLI application?
Does anybody have more information than a stack trace (e.g. inspected the crash with chrome devtools)?
karneaud
commented
6 years ago @addaleax sorry but I could not provide a reproduction project because its really sporadic.
Jessidhia
commented
6 years ago It looks like the constructor for the req.handle that is attempted to have writev called on it is made by the spdy package; the last "user code" instruction that runs before it's all internal is proxyRes.pipe(res) (normal piping from a read into a write socket).
Were there maybe any breaking changes made in 10.6.0 that could have broken spdy? This crash also happens in 10.7.0, but not in 10.5.0.
Jessidhia
commented
6 years ago Looks like it has been known it would be broken soon because of it using node internals; it just wasn't expected to break in Node 10.
addaleax
commented
6 years ago @Kovensky Ah! Thanks for digging that up. I think this might be the relevant change: https://github.com/nodejs/node/commit/64a3fadf7192485197b9695b7bb2165c7e7d762d#diff-e6ef024c3775d787c38487a6309e491dL215
It’s easy enough to undo, but I’m a bit torn on whether we should. The spdy package is effectively unmaintained and, more importantly, could break again at any time due to its extremely fragile implementation – we even haven’t been able to test it in Node’s CI infastructure anymore because of this for a while. Acting as if what spdy does is supported behaviour is somewhat reckless, imo.
I’d prefer to look into adding support for the built-in HTTP/2 module for webpack-dev-server and/or disabling spdy in it for Node 10 – the latter is easy, and the former shouldn’t be too hard, and make both our and their lives a bit easier…
Jessidhia
commented
6 years ago It also looks like webpack-dev-server (or anything using express) can't easily be migrated due to https://github.com/expressjs/express/issues/3388 🤔
addaleax
commented
6 years ago Opened a PR for webpack-dev-server to move away from spdy @ https://github.com/webpack/webpack-dev-server/pull/1451.
Edit: If somebody wants to try that PR out in the "real" world, here’s how: https://github.com/webpack/webpack-dev-server/blob/master/CONTRIBUTING.md#testing-a-pull-request
karneaud
commented
6 years ago @addaleax i'm going to try the pull request
i put
"webpack-dev-server": "webpack/webpack-dev-server#1451/head"as package
but get met with
Command failed: /usr/bin/git checkout 1451/head
lundibundi
commented
6 years ago @karneaud that may be for yarn, see https://stackoverflow.com/a/36743127/3923380,
It should probably be
npm i --save-dev webpack/webpack-dev-server#pull/1451/head
or in package.json
"webpack-dev-server": "github:webpack/webpack-dev-server#pull/1451/head".
karneaud
commented
6 years ago @addaleax
tried your pull request and got the following
Cannot read property 'compile' of undefined
npm info it worked if it ends with ok npm verb cli [ '/usr/local/bin/node', npm verb cli '/usr/local/bin/npm', npm verb cli 'run', npm verb cli 'build-css' ] npm info using npm@6.1.0 npm info using node@v10.7.0 npm verb run-script [ 'prebuild-css', 'build-css', 'postbuild-css' ] npm info lifecycle bartendergame@0.1.0~prebuild-css: bartendergame@0.1.0 npm info lifecycle bartendergame@0.1.0~build-css: bartendergame@0.1.0
bartendergame@0.1.0 build-css /usr/src/app node-sass-chokidar --include-path ./src --include-path ./node_modules src/ -o src/
Wrote 5 CSS files to /usr/src/app/src/ npm verb lifecycle bartendergame@0.1.0~build-css: unsafe-perm in lifecycle true npm verb lifecycle bartendergame@0.1.0~build-css: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/app/node_modules/.bin:/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/app/node_modules/.bin:/usr/src/app/node_modules/.bin:/usr/local/share/.config/yarn/link/node_modules/.bin:/usr/src/app/node_modules/.bin:/usr/local/share/.config/yarn/link/node_modules/.bin:/usr/local/libexec/lib/node_modules/npm/bin/node-gyp-bin:/usr/local/lib/node_modules/npm/bin/node-gyp-bin:/usr/local/bin/node_modules/npm/bin/node-gyp-bin:/usr/local/bin:/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/app/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin npm verb lifecycle bartendergame@0.1.0~build-css: CWD: /usr/src/app npm info lifecycle bartendergame@0.1.0~postbuild-css: bartendergame@0.1.0 npm verb exit [ 0, true ] npm timing npm Completed in 7983ms npm info ok => changed: /usr/src/app/src/sass/game.scss => changed: /usr/src/app/src/sass/help.scss => changed: /usr/src/app/src/sass/home.scss => changed: /usr/src/app/src/sass/index.scss => changed: /usr/src/app/src/sass/start.scss Cannot read property 'compile' of undefined npm verb lifecycle bartendergame@0.1.0~start-js: unsafe-perm in lifecycle true npm verb lifecycle bartendergame@0.1.0~start-js: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/app/node_modules/.bin:/usr/src/app/node_modules/.bin:/usr/local/share/.config/yarn/link/node_modules/.bin:/usr/src/app/node_modules/.bin:/usr/local/share/.config/yarn/link/node_modules/.bin:/usr/local/libexec/lib/node_modules/npm/bin/node-gyp-bin:/usr/local/lib/node_modules/npm/bin/node-gyp-bin:/usr/local/bin/node_modules/npm/bin/node-gyp-bin:/usr/local/bin:/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/app/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin npm verb lifecycle bartendergame@0.1.0~start-js: CWD: /usr/src/app npm info lifecycle bartendergame@0.1.0~start-js: Failed to exec start-js script npm verb stack Error: bartendergame@0.1.0 start-js:
react-scripts startnpm verb stack Exit status 1 npm verb stack at EventEmitter.(/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:304:16) npm verb stack at EventEmitter.emit (events.js:182:13) npm verb stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) npm verb stack at ChildProcess.emit (events.js:182:13) npm verb stack at maybeClose (internal/child_process.js:961:16) npm verb stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:5) npm verb pkgid bartendergame@0.1.0 npm verb cwd /usr/src/app npm verb Linux 4.9.80-hypriotos-v8 npm verb argv "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/bin/npm-cli.js" "run" "start-js" npm verb node v10.7.0 npm verb npm v6.1.0 npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! bartendergame@0.1.0 start-js: react-scripts startnpm ERR! Exit status 1 npm ERR! npm ERR! Failed at the bartendergame@0.1.0 start-js script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm verb exit [ 1, true ] npm timing npm Completed in 36063msnpm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2018-08-03T09_59_16_576Z-debug.log npm verb lifecycle bartendergame@0.1.0~watch-css: unsafe-perm in lifecycle true npm verb lifecycle bartendergame@0.1.0~watch-css: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/app/node_modules/.bin:/usr/src/app/node_modules/.bin:/usr/local/share/.config/yarn/link/node_modules/.bin:/usr/src/app/node_modules/.bin:/usr/local/share/.config/yarn/link/node_modules/.bin:/usr/local/libexec/lib/node_modules/npm/bin/node-gyp-bin:/usr/local/lib/node_modules/npm/bin/node-gyp-bin:/usr/local/bin/node_modules/npm/bin/node-gyp-bin:/usr/local/bin:/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/app/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin npm verb lifecycle bartendergame@0.1.0~watch-css: CWD: /usr/src/app npm info lifecycle bartendergame@0.1.0~postwatch-css: bartendergame@0.1.0 npm verb exit [ 0, true ] npm timing npm Completed in 36286ms npm info ok ERROR: "start-js" exited with 1. error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. npm verb lifecycle bartendergame@0.1.0~postinstall: unsafe-perm in lifecycle true npm verb lifecycle bartendergame@0.1.0~postinstall: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/app/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin npm verb lifecycle bartendergame@0.1.0~postinstall: CWD: /usr/src/app npm info lifecycle bartendergame@0.1.0~postinstall: Failed to exec postinstall script npm verb stack Error: bartendergame@0.1.0 postinstall:
yarn startnpm verb stack Exit status 1 npm verb stack at EventEmitter.(/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:304:16) npm verb stack at EventEmitter.emit (events.js:182:13) npm verb stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) npm verb stack at ChildProcess.emit (events.js:182:13) npm verb stack at maybeClose (internal/child_process.js:961:16) npm verb stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:5) npm verb pkgid bartendergame@0.1.0 npm verb cwd /usr/src/app npm verb Linux 4.9.80-hypriotos-v8 npm verb argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--unsafe-perm" "--verbose" npm verb node v10.7.0 npm verb npm v6.1.0 npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! bartendergame@0.1.0 postinstall: yarn startnpm ERR! Exit status 1 npm ERR! npm ERR! Failed at the bartendergame@0.1.0 postinstall script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm verb exit [ 1, true ] npm timing npm Completed in 185663msnpm ERR! A complete log of this run can be found in:
addaleax
commented
6 years ago Cannot read property 'compile' of undefined
@karneaud I’m not sure what to make of that … I suppose it’s also happening without my patch? Does it happen when HTTPS is turned off completely? :/
karneaud
commented
6 years ago @addaleax actually this is what is happening BECAUSE of your patch. I'm trying to debug it and will try to get a small repo worked up to let you know how far i have reached.
As for trying it without HTTPS....I have not thought of that. Thanks
amilajack
commented
6 years ago I am experiencing this issue with https as well
lundibundi
commented
6 years ago @amilajack could you provide a reproduce of your issue or at least a backtrace/log? Also, what makes you think that it is https-related in your case?
Currently, the issue is a misuse/replacing/modification of private node http-related apis therefore it may seem that this is an http/https error (based on a log from the first post) even though it most likely isn't. (For now we now of https://github.com/spdy-http2/node-spdy/issues/333 and therefore https://github.com/webpack/webpack-dev-server/issues/1449, also to me it seems this https://github.com/moll/node-mitm/issues/50 also has the same problem (based on a quick look at mitm/index.js)).
daniellavoie
commented
6 years ago Also experiencing this issue. If I deactivate https, I don't experience the issue. I'm under NDA for the project on which I experience the issue so providing sample code is hard. I'll see what I can do.
addaleax
commented
6 years ago @karneaud Did you figure out something re: what about my proposed patch was causing the issue?
bjornharvold
commented
6 years ago Happening on HTTPS for me as well.
pickardjoe
commented
6 years ago Same issue here. I'm running the node:10-alpine docker image with vue-webpack. I am using HTTPS.
TypeError: req.handle.writev is not a function at writevGeneric (internal/stream_base_commons.js:59:24) at Socket._writeGeneric (net.js:759:5) at Socket._writev (net.js:768: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:638:8) at process._tickCallback (internal/process/next_tick.js:63:19)
This issue does not occur if I switch to the node:8-alpine docker image as a base.
queejie
commented
6 years ago Also experiencing this issue, with https and node 10.9.
addaleax
commented
6 years ago Just to be clear, +1 comments here might be helpful for bumping the issue occasionally, but we know what the cause is.
If you want to help, try out the PR in https://github.com/webpack/webpack-dev-server/pull/1451 and, if you run into any issues with it, try to figure those out.
andrewdodd
commented
6 years ago Sorry that is a bit of +1 comment, but I thought it might help some people who find themselves here after getting this cryptic failure.
I am using "create-react-app / CRA", and absent-mindedly obeyed a "you should upgrade to latest yarn" prompt, which precipitated this error.
I can confirm:
brew upgrade yarn took me to v10)
nvm and could use that with the homebrew installed yarn to find that using Node v9 made this error go away.node_modules/webpack-dev-server/lib/Server.js file to have the same changes as at here"webpack-dev-server": "github:webpack/webpack-dev-server#pull/1451/head" to my package.json file it crashes with the same error. I am not really sure why this one should fail, but manually making the edits should succeed.
react-scripts use their vendored copy if the project defines a webpack-dev-server, but if it doesn't they use the "project" version, hence the manual edits get picked up? NB: I tried this back-and-forth many times to test I wasn't going mad.@addaleax thanks for the PR, hopefully this makes it to through the dependency chain to the CRA guys soon!
aaronrr
commented
6 years ago Also experiencing this issue after connecting to https://[DesktopIP]:8080 from a physical iPhone on the same network.
As an upside, simply running npm run build allowed it to start again, but connecting with the phone again crashes it.
lundibundi
commented
6 years ago addaleax
commented
6 years ago @lundibundi Thanks for the pointer, I didn’t realize all those downloads were coming from create-react-app :)
With that updated, I think this issue can be closed. If anybody runs into trouble – please try updating your dependencies first! :)
rmatrose
commented
5 years ago I was getting this error on Windows 10 x64 on NodeJS version 10.13.0. I simply removed NodeJS version 10.13.0 and installed version 8.11.3 and restarted my machine and it was gone!
nicholas-eden
commented
5 years ago Is there a fix or a workaround for this that doesn't require using node 8?
Using node 10.10 and angular 5 I get this error when I run the angular serve command. It only occurs when using the iOS simulator. It may have something to do with which version I'm emulating, definitely happens on iPad 9.2. I don't recall if it occurs in 12, or if I just haven't had it running long enough to trigger the error.
addaleax
commented
5 years ago @nicholas-eden https://github.com/spdy-http2/handle-thing/pull/5 should have fixed this on the spdy side, so updating your dependencies might help.
Otherwise, you may need to provide steps to reproduce in order for people to be able to help you.
nicholas-eden
commented
5 years ago I don't know how reproducible this is on other projects, but here's what's happening:
Strangely, this doesn't happen with an iPad 9 or 10 instance.
This is my error log:
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)
child_process.js:651
throw err;
^
boxfox619
commented
5 years ago I have same problem when open page on https with IPhone X. node version 10.6.0 -> occur 'req.writev is not a function' error But, It worked fine on a desktop browser.
And i solved this problem with change node version to 8.11.3
martinKindall
commented
5 years ago Same issue here Ubuntu 16.04 64 bits nodejs v10.15.0
Using create-react-script and it crashes when I use chrome on my cellphone. Chrome on my desktop doesn't produce this failure.
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:715:5) at Socket._writev (net.js:724: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)
alcmontejo
commented
4 years ago what is the resolution?
lundibundi
commented
4 years ago The resolution is to use webpack-dev-server of version >= 3.1.7 that fixed the bug.
Based on github milestones in create-react-app it should be shipped with the updated version starting with create-react-app@2.0+ (PR https://github.com/facebook/create-react-app/pull/5032)
This is a node internal crash that happens with
webpack-dev-server, likely with any config, only when running on node 10.6.0:The same
webpack-dev-serverwith the same config has no crash on node 10.4.1 and runs successfully.