John Spurlock

Hmm, did you check out your repo as the first step of your gh action? Doesn't look like it is finding your worker at `./supabase/functions/cloudflare/worker.ts` for whatever the cwd happens...

That's strange. Maybe add the `--verbose` flag to your `denoflare push` [command](https://denoflare.dev/cli/push) and see if there are any clues? The fact that it says your bundled module JS is zero...

Yes this is tricky. Denoflare bundles (and rebundles) your code and runs it in a permissionless worker by defaule, and the last time I looked into it (a while ago)...

Yep, Deno's `npm:` specifiers are not supported, as they are not supported by `deno bundle` - and we need to bundle into a single js for Cloudflare

Yes, `deno_emit` has never worked well, experimented in denoflare using `--bundle backend=module` I imagine esbuild + esbuild_deno_loader will be the most full-featured solution. I miss `Deno.emit`, and soon `deno bundle`...

Denoflare supports Cloudflare wasm/text/binary imports with their non-standard syntax using some post-bundling transformations - these would be tricky to do in general, but sure an escape hatch where you could...

Looks like an error in your bundle output (denoflare uses `deno bundle` under the hood). Try running `serve` without local isolation: ```sh $ denoflare serve --local-isolation none ``` You'll lose...

Do you have bare imports in your script? Denoflare supports `./` and `https://...` old school Deno imports, nothing that requires import map config or npm deps etc.

yea you are in uncharted territory there - are you wanting to use in `denoflare serve`, `denoflare push`, both? Shouldn't be too difficult, just would need to config or pass...

@JustinGrote mind sending me or posting an example project including your import maps?