"Could not set npm package requirements" when lock:false in deno.json about deno HOT 7 CLOSED

Are you talking about in the LSP? This is probably a duplicate of #23659

It is probably fixed in deno upgrade --canary and will be released later today.

from deno.

indeed

from deno.

Actually, having deleted the deno.lock, seems the problem is still there ( just changed to lock:false before and forgot to delete deno.lock)

from deno.

What happens after you cache the dependencies by running "Deno: Cache dependencies" from the vscode command pallete?

By the way, I wouldn't recommend using lock: false with npm packages. It causes everything to be much slower because it doesn't cache the npm resolution in the lockfile.

from deno.

What happens after you cache the dependencies by running "Deno: Cache dependencies" from the vscode command pallete?

By the way, I wouldn't recommend using lock: false with npm packages. It causes everything to be much slower because it doesn't cache the npm resolution in the lockfile.

from deno.

What happens when you go to https://registry.npmjs.org/@types/node? Sometimes the npm registry is flaky. It looks like it's attempting to download then the connection is closed (the error on the last line is just what occurs after caching was attempted). You may need to try caching a few times.

If that doesn't work, do you have a repo that we could try reproducing in?

from deno.

What happens when you go to https://registry.npmjs.org/@types/node? Sometimes the npm registry is flaky. It looks like it's attempting to download then the connection is closed (the error on the last line is just what occurs after caching was attempted). You may need to try caching a few times.

If that doesn't work, do you have a repo that we could try reproducing

I tried that, the url always works.

from deno.