(It has been pointed out to me that this is specifically "nvm for Windows", not regular ol' NVM -- point still stands though that it sounds like this should be fixed on their end, not Node.js')
Comments
Log in with your Bluesky account to leave a comment
Just wanted to say thanks to everyone for such quick feedback. Really appreciate it! The bug appeared in a patch a few years ago, but was never detected because the code looked correct. It's already resolved, but I'm concerned for users who can't immediately upgrade.
That makes sense — we’re following the issue and have discussed it a bit in the OpenJSF Slack. I think the position for now is that we’d prefer to keep this new behavior, but we’ll keep an eye on how much trouble this is causing, and can always put a fix in on our end if needed.
Comments
https://bsky.app/profile/ruyadorno.com/post/3lbfdp6pgl22j