Deno Third Party Modules
deno.land/x is a hosting service for Deno scripts. It caches releases of open-source modules stored on GitHub and serves them at an easy-to-remember domain.
Deno can import modules from any location on the web, like GitHub, a personal webserver, or a CDN like esm.sh, Skypack, jspm.io or jsDelivr.
To make it easier to consume third party modules Deno provides some built in tooling like deno info and deno doc.
- transcriptorCLI tool for transcribing and summarizing audio data 📝
- trainjsAn express inspired web framework for Deno.
- trainA web app library for Deno.
- trailmixRepository of utilities for deno written in typescript for trailmix🌤🦕🍣😼
- traefikjamA tiny (zero dependency) Node.js CLI utility to convert Traefik Let's Encrypt certificates from acme.json to PEM files
- tracecontextBlazing fast w3c Trace Contexts for any JS runtime
- tqlA GraphQL query builder for TypeScript. Avoid the pain of codegen.
- tpy🔑 A strongly typed Pylon API client.
- toytoy eng API and tools
- towerNo description
- totp_wasmHOTP & TOTP & Steam Guard TOTP
- totallylazyDEPRECATED: Use bodar.deno/totallylazy
- toruk🦕 Deno router fast, lightweight, close to runtime best practices
- torrenta bittorrent library for Deno 🦕
- torma typesafe orm-like database tool built around writing raw sql queries
- torMake request on the Tor network with Deno 🕶
- topicsUse Deno KV queues with named topics.
- topherukDeno Playground
- topgg_denoDeno sdk for the top.gg api
- tools39No description
Q&A
Can I still publish to deno.land/x?
No. deno.land/x is now read-only. Existing modules and versions remain available and immutable, but no new modules or versions can be published here. New packages should be published to JSR, the modern registry for Deno and the broader JavaScript ecosystem.
How do I use modules on deno.land/x?
The basic format of code URLs is https://deno.land/x/IDENTIFIER@VERSION/FILE_PATH. If you leave out the version it will be defaulted to the most recent version released for the module.
Can I find functionality built-in to Deno here?
No, the built-in runtime is documented in the manual. See /std for the standard modules.
I am getting a warning when importing from deno.land/x!
deno.land/x warns you when you are implicitly importing the latest version of a module (when you do not explicitly specify a version). This is because it can be unsafe to not tag dependencies. To get rid of the warning, explicitly specify a version.
Can I edit or remove a module on deno.land/x?
Module versions are persistent and immutable. It is thus not possible to edit or delete a module (or version), to prevent breaking programs that rely on this module. Modules may be removed if there is a legal reason to do (for example copyright infringement).
A module is name-squatting or its just made as a joke, can I have it?
deno.land/x is now read-only, so module names can no longer be claimed or reassigned. To publish a new, well-maintained module, use JSR instead.