"404 /@npm/@npm/object-assign - npm registry lookup failed for "@npm/object-assign": Package doesn't exist."

[ruifortes]

Hi.
I'm getting this error message with no apparent cause.
Is this some issue with cdn itself?

I'm using windows 10.

Anything I can do to isolate the problem?

[ruifortes]

Nevermind, something got "locked" in the node_modules folder, probably by vscode

[mdcanham]

Hey, I'm struggling with this. I'm not seeing any locked files — do you remember how you resolved this?

[rejhgadellaa]

Having the same problem but not just object-assign, I also get it for react-is:

/@npm/@npm/react-is - npm registry lookup failed for "@npm/react-is": Package doesn't exist.

Everything works fine, and then at some point it doesn't and I get this error ?

[mdcanham]

Yeah I'm getting this with @npm/filter-obj so a different package too.

404 /@npm/@npm/[email protected] - npm registry lookup failed for "@npm/filter-obj": Package doesn't exist.

[rejhgadellaa]

Restarting the vscode window for the project seems to fix it, at least for a while. That would confirm @ruifortes' comment that vscode locks something?

[rejhgadellaa]

Just ran int the issue again and while I was trying to get it back to work, I noticed Windows Terminal (Powershell) was complaining that it couldn't delete the node_modules folder without forcing the deletion:

node_modules\rgui-preact-core is an NTFS junction point

This may be related?

Update: NVM, the NTFS junction point is just a symlink npm created for a local package. I don't think this is related.

[rejhgadellaa]

Since this ticket is closed, I've created a new ticket with additional info: #903