Closed kobe-ra closed 2 months ago
Are you able to reproduce on other Node.js versions, or just 20.12.2? https://github.com/nodejs/node/commit/69ffc6d50d is the only Windows-related change in 20.12.2, although it doesn't seem related to your problem, but we can easily verify that by simply trying with another version.
Node versions I tried and had the same problem: v20.12.0
, v21.7.3
, v20.11.1
.
Which probably means there was a Windows change? I don't recall installing updates in the past two days, but maybe microsoft can install minor updates on the background.
Are you using using ESET(Nod32) antivirus? https://github.com/nodejs/help/issues/4375
ESET Endpoint Security v. 11.0.2044.0
.
I think that will be it. Except I cannot test because only admin can pause the protection.
Thank you for pointing me this way, I'll close this issue tomorrow if it is the ESET.
👋 Hello! Please see also the ESET forum discussion here: https://forum.eset.com/topic/40702-eset-ssl-protection-produces-an-invalid-certificate-chain-for-nodejs-apps/.
It includes a workaround, which is to specifically disable HTTPS traffic scanning rather than entirely disabling protection, which I've tried and it did work for me. You did mention that your ESET install is administrator managed so you might not have any luck with that, but others might.
Tomorrow is going to be a fun day.
It indeed was the ESET AV causing this issue.
Version
v20.12.2
Platform
Microsoft Windows NT 10.0.19045.0 x64
Subsystem
No response
What steps will reproduce the bug?
Including a private git repo as a dependency stopped working. I've had this entry
"ratrakcn-ui": "https://github.com/kobe-ra/ratrakcn-ui.git",
in mypackage.json
for months and i could usenpm install
normally. For the last two days npm commands won't run if the dependency is included. Well, it runs, it takes up to 10 minutes (normally less than 10 seconds) and results in an error im posting below. I have not made any significant changes to either app using the package or the package itself in this time window. Weird thing is that it runs properly on mac. So I went and tested it on another windows (3rd device being tested) and it doesn't work on that windows too.git+https://...
Can it be a certificate issue if npm itself works when the one package is not included? I'm the only maintainer of the package, so I know there werent any changes.
Npm is really crucial for my work and I haven't been able to work for two days now. I'm willing to pay if someone helped me via discord call or something, since I'm desperate at this point.
I'd like to note that I also tried asking on the stackoverflow, then to
npm/cli
where they said it looks like node-windows issue.How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
No response
What do you see instead?
Additional information
No response