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.
- isIPIP address detector for Deno.
- yocto_queueNo description
- workerio🦕 Deno module to translate Worker's system of messages into Reader and Writer
- papyrusLightweight, modular JSON logger for `Deno` with support for external formatters and transports.
- oauth4webapiLow-Level OAuth 2 / OpenID Connect Client API for JavaScript Runtimes
- fresh_chartsA server-side-rendered charting library for Fresh
- faunaJavascript driver for FaunaDB
- airtableUnofficial Airtable client for Deno 🦕
- danielduel_ultra_stack_ultraZero-Legacy Deno/React Suspense SSR Framework
- clippycross-platform Deno module for writing and reading clipboard.
- htmCreate `text/html` response with JSX.
- simplewebauthnWebAuthn, Simplified. A collection of TypeScript-first libraries for simpler WebAuthn integration. Supports modern browsers, Node, Deno, and more.
- puppeteer_plusDeno port of puppeteer base on latest TypeScript source.
- colorA simple, fast, and comprehensive color library for Deno.
- loadenvNo description
- liveGit-based Visual CMS for Deno, </> htmx and Tailwind apps. Deploy on any Deno-compatible host.
- pretty_benching:sauropod: A small lib to make your Deno benchmarking progress and results look pretty
- minify_htmlNo description
- hextoolsConvert from ArrayBuffer to hexadecimal and viceversa in Deno.
- grammy_storagesStorage adapters for grammY sessions.
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 on deno doc and 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.