Support Deno

[zadeviggers]

It would be cool if Astro supported Deno.
Supporting Deno would make Astro accessible to a wider audience (and also make Astro seem even cooler!).

If we support Deno, then when server-side rendering comes out it would help enable hosting on Deno deploy.

[okikio]

This is something we could do in theory, but it will require a lot more work before it's ready. We could use browser-vite together with Deno service-workers, but before all that happens we need to try testing browser-vite with Astro, which is currently a WIP.

[FredKSchott]

cc @matthewp -- I believe Matthew wants Deno + Deno Deploy to be a supported target for our SSR support!

As for the tool itself, we are tied to Vite at the moment, and I believe Vite has a thread where they are not currently interested in supporting Deno. This would make it very hard (impossible) for us to support Deno without them. If they ever do consider revisiting, we should too!

[matthewp]

I think this RFC wants Deno as the dev environment, which would indeed be very hard if not impossible given our coupling to Vite. If Vite were to work in Deno, then maybe.

[zadeviggers]

After poking through some old Vite issues, I found this which claims to allow the vite server to run on Deno, although it seems quite hacky.

[mxdvl]

Worth noting that Deno Deploy is supported with @astro/deno already.

For previewing locally through Deno, I would recommend Elian Van Custem’s tutorial on their blog, published last week.

[ben-laird]

I'd really like to revisit this in an upcoming Astro release. I came from this issue where I encountered Astro throwing errors about reading import.meta.env, and I thought it was a genuine bug, not a lack of a feature. It's a bit surprising to me since Vite is ok running in a Deno environment in development (ie running deno task dev), so I figured Astro would follow suit.

It just seems really odd to support Deno in production through @astrojs/deno but not in development. I don't think an adapter should be required either, Astro should run in static mode in a Deno env in dev without throwing any errors, especially ones about a Vite feature.