Help me out, Deno devs. Which of the following URLs should I go with when I live with the new Deno support I'm adding to SimpleWebAuthn? The project will become available via https://deno.land/x.
(Without something like this you end up with a massive URL like https://deno.land/x/simplewebauthn/packages/server/src/index.ts since I have to publish the entire monorepo because deno.land is powered by per-repo webhooks.)
The NPM packages that get published already have ESM and CJS support for Node projects in either configuration. And with Cloudflare Workers and Bun both being Node-compatible you can just use the NPM packages like a normal Node project.
My vote is for the first option because these specific paths are specifically for Deno projects. Someone else is championing the second option because other projects looking to use the ESM version might want to use the same URL, and it'd be confusing to have /deno/ in it. But I'm not aware of any other runtimes now or coming up that do anything like Deno does with import {...} from 'https://example.com/x/modulename/src/index.ts. Maybe I'm missing something?
Anyway thanks for helping me out with this. This'll be the first module I've ever published to Deno after three years of the project being Node-only and naming things is hard 🙃
#deno #node #typescript #javascript #webauthn #simplewebauthn