- Version: 1.19.0-1
- Platform: Linux
The new version (1.19.0-1) of libuv broke node on my Linux machine (ArchLinux). According to semver minor releases should not break dependant software. See https://github.com/npm/npm/issues/19634#issuecomment-358585641
Archcry
All 6 comments
We're aware. There's a reason we bundle libuv with node.js and it looks like arch users are finding that out the hard way today.
bnoordhuis
on 18 Jan 2018
Well, minor versions should not introduce breaking changes so blaming Arch users for it seems kind of odd in my opinion.
Archcry
on 18 Jan 2018
It's a bug, nothing more. We do integration testing on the node.js side and it caught the regression. If arch had stuck with the bundled version, you wouldn't be experiencing fallout right now.
bnoordhuis
on 18 Jan 2018
Ah my apologies, I though you meant that is was okay to introduce breaking changes in a minor version. Thanks for clarifying that it is a bug.
Archcry
on 18 Jan 2018
Oh, and to be clear, the real bug is most likely on the node.js side, the newest libuv release merely exposes it. But we'll be reverting the libuv change for now until things get fixed in node.js.
bnoordhuis
on 18 Jan 2018
Hmm ok, thanks for the quick responses :D
Archcry
on 18 Jan 2018
Related issues
imran-iq
路
7Comments
bnoordhuis
路
9Comments
cjihrig
路
12Comments
jorangreef
路
9Comments
bradking
路
9Comments
Most helpful comment
Oh, and to be clear, the real bug is most likely on the node.js side, the newest libuv release merely exposes it. But we'll be reverting the libuv change for now until things get fixed in node.js.