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.
- doraDora is funny terminal spinner for deno.
- doppler_clientA doppler.com api client written for deno to be used in deno deploy
- doomfetchA quick and easy fetch utlity for deno and the web using classes.
- dongoose_extraDongoose is a simple ( but intelligent ), lightweight, and easy to use ORM for Deno KV. It is written in Typescript and is inspired by Mongoose.
- dongooseDongoose is a simple ( but intelligent ), lightweight, and easy to use ORM for Deno KV. It is written in Typescript and is inspired by Mongoose.
- donfigDeno module for configuration control for multiple environments deployments
- donemqSelf-hosted message queue for Deno Deploy
- domtypeNo description
- domino_defineNo description
- dominoDominoBots Runtime
- domdomThe proactive web framework for the unprofessional - Deno build
- domain_requestNo description
- domain_functionsTypes and functions to make composition easy and safe
- domain_eventsAMQP like domain events. This module allows you to implement domain events on your Deno applications.
- domainGet all the top-level domains, including gTLDs such as `.com`, and country-code TLDs such as `.uk`.
- dom_stdDOM reference implementation
- dom_diffThe real DOM diffing
- dollarbagFluent modular JavaScript utility library.
- dogecoinDeno Wrapper for https://dogechain.info/api/blockchain_api
- dogapitsDog API client for Deno.
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.