nlf
Yes! I'm so happy there's a standard that I can point to for this. Definitely going to do this, thank you for bringing this to my attention!
Yeah, I'll read through the spec first, but I'm super excited if this will work. All the ambiguity in this module is a huge annoyance.
While I'd like to do this, I think this module isn't the right place for it. There are so many wild edge cases that this module already caters to that...
first off, i'd like to thank the folks who exercised restraint when expressing their frustration here. i know it's difficult, but your efforts to help us understand this bug as...
@gthb your reproduction isn't working for me in npm@9, i actually get an unrelated error having to do with resolving the override in your example. i've fixed the unrelated error...
i'm going to close this as npm@9 no longer attempts to change the ownership of any files. if there are aspects of this that are still broken for folks after...
this is fixed in npm@9
here's another known bug - https://github.com/npm/cli/issues/6125
if all of you who are experiencing this error are proxy users, then i have a good idea of what's going on. is anyone seeing this _not_ using a proxy?
whoa, this is an interesting one. you're absolutely right, we're totally failing to install that dependency despite it being a requirement of `[email protected]`. even worse, `npm ls` doesn't even identify...