When can it be used in deno

[ynwd]

When can it be used in deno?

[oshox]

We'd like to see "deno bundle" support to allow deployment to Netlify Edge and others.
Or should we wait for Deno to support Vite? denoland/deno#12577

it's time for cjs to go

[DylanPiercey]

@oshox the only way we could natively support deno is if their bundler supported registering custom extensions. IIRC it does not. Does any other non simple jsx framework support deno natively without nodejs tooling?

[oshox]

@DylanPiercey Thanks for the clarification/correction. The only SSR frameworks using the built-in bundler are indeed "simple." (AlephJS being a possible exception?)
After some more consideration, maybe there's two ways to interpret "Deno Support:"
A. Compiler output can be deployed to Deno
B. Compiler can be run on Deno

A would be the concern for everyone hyped about Netlify Edge. I doubt many people will be concerned about B unless Deno starts to seriously displace Node.

[DylanPiercey]

@oshox B is on our radar. I suspect that there are minimal if any actually changes to make for Marko to work with Netlify Edge (we already can deploy to eg cloudflare workers). We'll be investigating creating a starter project that uses Netlify Edge as well as Deno.

[oshox]

A is almost working in this example:
https://github.com/oshox/marko-deno-hono

The component isn't mounting correctly. I copied the vite.config.js from the Cloudflare example; maybe it needs to be changed?

[gitsemaphore]

A is almost working in this example: https://github.com/oshox/marko-deno-hono

@oshox just wonder if you had any luck? I can't seems to access your repo. I had some luck with esm.sh unpkg.