#caching NPM deps broken on VS Code

19 messages · Page 1 of 1 (latest)

small stratus
#

hi
basically, it keeps showing the same error, specifically on NPM deps, that the dependency is "uncached"
but... it is cached, I can swear it is, it even runs, it's just the code editor/the LSP
i even tried specifying a specific version, instead of just "@^4" for example, but nope, same fricking issue
it's driving me nuts catbob

EDIT: i wanna add that i'm using GitHub Codespaces, but I remember having the same issue on my local environment

#

sometimes i can temporarily make it disappear, but then i will do my coding as usual, and poof, it magically reappears

#

it fricking runs, so why does it keep showing the uncached deps error pourquoi

sturdy yarrow
#

Can't reproduce, hit code actions > cache dependency and it works out of the box. What deno version are you on?

small stratus
#

and now on my local repo (on my computer) i don't have this issue pourquoi
it's so weird

sturdy yarrow
#

Try to cache deps and then control/cmd + shift + p > reload window

#

see if that helps

small stratus
#

it doesn't cache deps, as they are already cached :/

#

but i'll try

sturdy yarrow
#

the lsp says that they are not cached, apart from a restart there's not a lot you can do

small stratus
#

uh

#

it's gone?

#

wtf

#

thank you 🙏

#

(although i've already made it go away, and it came back several times CatCry)

sturdy yarrow
#

you're welcome and good luck haha

glass ibex
#

I'm seeing this too... It's not just vscode, deno run also complains with the same error. No idea how this all works under the hood, but there's definitely something that's flakey.

small stratus