dnt VS denoify

We are going to use dnt - Deno to Node Transform tool to build the npm package.

As already mentioned dnt might help you if you are willing to have deno as your primary development environment. I work in a project like this and the deno tooling is great. I don't even need a package.json since dnt will generate it for me.

Build it in Deno and then use dnt to create an npm package. That way you support both JS runtimes: https://github.com/denoland/dnt

Specifically, make my codebase be for Deno, use Deno built-in formatter, linter and testing, and use dnt (Deno to Node Transform) to generate an npm package containing ESM code and to test generated code. For testing in the browser, deploy the test content linked to the generated ESM code to Github Pages and use playwright/test. For Cloudflare Workers, use wrangler to set up a worker locally for testing. A schematic diagram is shown below.

I ended up building the library with Deno and compiling to Node.js CJS and ESM using https://github.com/denoland/dnt

Yes, TS code is compiled to run in browsers. You can compile and bundle using `deno bundle` if your project is developed in Deno. Since I'm using Deno for library development, I use the `dnt`[1] tool to compile them into ESM modules later consumed by esbuild in my Node-based projects/toolchains.

[1] https://github.com/denoland/dnt

Maybe this could help? https://github.com/denoland/dnt

If you’re building packages/libraries for the community to use you can take a look at Denoify. It’s a project that aims to change some of your files automatically when migrating and make it easier to maintain the project for both npm and deno.land/x.

I do Node-first packages and use https://github.com/garronej/denoify to produce deno-compatible code. (example: https://github.com/mxxii/leac )

You can use https://github.com/garronej/denoify for Node-first packages.

Or use ts-patten it's comming to Deno soon (thanks to Denoify).

So, if you tried Denoify in the past and it didn't work for you, maybe it will now. If you need a hand, I'm happy to help. Just ask anything on the newly opened discussion section of the github repo.

It has zero dependencies so was very easy to dual publish on both npm and deno.land using denoify. Literally just needed to add the .ts extension to imports.