deno w/ svelte kit
hey all, so deno mostly works with svelte kit~! its
dev
and build
commands work (so long as youre not prerendering @ build), but the main blocker right now is actually that Deno doesn't pick up the types that SK generates on the fly. Any ideas or suggestions to get that working?6 Replies
this is the error given, for example:
additionally, SK's internal aliases (eg,
$app/...
and $env/...
) arent picked upI wasn't able to find the answer to your question in the official Deno documentation. However, based on the information you've provided, it seems that the issue is related to Deno not picking up the types that SvelteKit generates on the fly.
While I cannot provide a solution based on the Deno documentation, one common issue with TypeScript in various environments is ensuring that the generated types are available and correctly referenced in your project. You might want to check that the paths to the generated types are correctly specified in your
tsconfig.json
or that the types are being generated in a location that Deno is aware of.
Please note that this advice is not based on the Deno documentation, and I would recommend double-checking the accuracy of this advice and exploring SvelteKit's community resources or forums for more specific guidance on integration with Deno.When does it happen? During build?
This PR will fix a few sveltekit related issues, so I'll help reassess the situation when it's in https://github.com/denoland/deno/pull/23634
GitHub
fix(node): seperate worker module cache by littledivy · Pull Reques...
Construct a new module graph container for workers instead of sharing it with the main worker.
Fixes #17248
Fixes #23461
no, build is fine actually as long as youre not using prerendering. thats when SK needs the module cache
its issues during development & specifically w/ deno's LSP. it doesnt understand all the type aliases and stuff that SK is generating behind the scenes
@lukeed Can you file an issue for that? Divy is actively working on getting SvelteKit fully working, but since he isn't a primary SvelteKit user any bug report is incredible useful