Adapter static but with Deno support?

[janosh]

Feel free to close if this is considered off-topic.

Can you offer any guidance on how to setup SvelteKit in such a way as to run builds with Deno but get the output produced by adapter-static? Instead of a Deno server, I'd like to end up with static HTML files but built with TypeScript end to end.

[jpaquim]

So you mean using Deno to run SvelteKit itself, right? From what I understand, this would be non-trivial, as it would require Deno-based alternatives to SvelteKit's dependencies, in particular vite (see the upstream issue for Deno support: vitejs/vite#109).

It might be possible to do it with Deno's Node compatibility library (https://deno.land/[email protected]/node/README.md), but I'm not sure I want to go down that route.

I'll leave the issue open, this is something that may be interesting to pursue, but broader in scope when compared to this adapter.

[janosh]

So you mean using Deno to run SvelteKit itself, right?

Correct. Should have been clearer.

From what I understand, this would be non-trivial...

I was afraid you'd say that. 😅

I'll leave the issue open, this is something that may be interesting to pursue, but broader in scope when compared to this adapter.

Thanks for linking the upstream repo. Like Evan said, probably too early days right now but I'll be keeping an eye on this space.

[DefinitelyMaybe]

So you mean using Deno to run SvelteKit itself, right?

Correct. Should have been clearer.

I've thought of this but I'm in no rush to do so. Should everyone start to move more towards deno and doing so supported something cool that you'd like to have, then go for gold.

[jpaquim]

Saw this one today, seems to be pretty much in the same space: https://github.com/NOVASland/NOVAS