denoland/dnt
Deno to npm package build tool. observed · 2026-10-12
Health v2 · maintenance only
94/100
- Activity 97
- Release rhythm 86
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-10-21. Adoption (stars, forks) is never an input.
- gap_med: 59
- age_days: 1858
- days_rel: 19
- days_push: 19
- n_releases_24m: 6
Adoption not part of the score
1336 stars · 50 forks observed · 2026-10-12
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
dnt (Deno to Node Transform) is a build tool that converts Deno modules into publishable npm packages for Node.js. It rewrites module specifiers, injects Deno shims, emits ESM/CommonJS/TypeScript declarations, and runs the output tests in Node.
Use cases
- publish a Deno library as an npm package
- convert Deno code to run on Node.js
- generate ESM and CommonJS builds from one codebase
- emit TypeScript declaration files for an npm package
- run Deno tests against the Node.js build output
- map esm.sh or remote imports to npm dependencies
When to choose
- you maintain a Deno module and want npm users to consume it
- you need dual ESM/CJS output with type declarations from a single source
- you want automated shimming of Deno-specific APIs for Node
When to avoid
- your project is Node-only with no Deno source
- you need a general-purpose bundler rather than a Deno-to-Node converter
- your code depends heavily on Deno APIs with no npm equivalents
Facets
cli-tool · maturity active
build-tool compiler developer-tools testing developer-tools cross-platform cli cross-platform deno npm nodejs package-publishing esm commonjs typescript transpilation command-line
1 source
- readme: https://github.com/denoland/dnt · fetched 2026-10-12 · 7ff09e9cf2bf
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| denoland/dnt | main | 94 |
For agents
Data as of 2026-10-19T08:05:51.212177+00:00 · Report a problem