[svelte template] .svelte modules are not recognized in ts files: "Cannot find module './App.svelte' or its corresponding type declarations"

[bnn1]

hi guys. i created a wxt project with svelte template. typescript doesn't recognize .svelte file import in ts files

can't reproduce this in other environments (i.e. stackblitz has no issues). any ideas what might be wrong with my setup?

[aklinker1]

Make sure the wxt-env.d.ts file is included in your typescript project. It's what adds the types for .svelte files.

Can you share your tsconfig.json? Maybe you change the include or exclude fields, and now TS is ignoring that file.

[bnn1]

I actually did run pnpm install in the video, but I accidentally cut this moment out when editing the video, sorry for the confusion 😅. It's super weird; I just created a new WXT project and there are no errors 🤔. I guess we can call it one of the quirks of VSCode. Or TypeScript. Or maybe the simulated universe glitched. Or perhaps I'm still in a coma and this is all just a dream.

[bnn1]

I just tried to create a project using npm, yarn and bun - no issues, no module resolution errors. I try to create a project with pnpm - bam, resolution errors. I guess it has something to do with how pnpm resolves and installs packages. Will try to investigate further a bit later.

[aklinker1]

Huh, weird. Maybe you have a different version of PNPM installed on that computer and it has a bug in it?

[bnn1]

I uninstalled pnpm and installed it via npm i -g. Still get the cannot find module error. Tried using the stable build of VSCode - same error.
pnpm check:

I'm on the LTS version of Node (v20.10)
typescript 5.3.3

Maybe this is related

[aklinker1]

If uninstalling and reinstalling didn;t work, did you try deleting your virtual store like mentioned in this comment? pnpm/pnpm#5716 (comment)

# Check the store path. For me:  /Users/aklinker1/Library/pnpm/store/v3
pnpm store path

# Remove the whole pnpm folder
rm -rf "/Users/aklinker1/Library/pnpm"

That seems a likely solution to me. You could also run pnpm store status before deleting it to see if there are any modified dependencies that might be causing this issue.