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.
- deno_kv_oauthHigh-level OAuth 2.0 powered by Deno KV.
- opticA powerful logging framework for Deno
- wait🌀 Minimal terminal spinner
- isxCollection of validation functions for JavaScript data
- superdenoSuper-agent driven library for testing Deno HTTP servers.
- xml2jsParse XML into JavaScript objects
- openOpen is a package for opening URLs, files and executables with Deno. Inspired by sindresorhus' open.
- microdiffA fast, zero dependency object and array comparison library. Significantly faster than most other deep comparison libraries and has full TypeScript support.
- sendgridNo description
- murmurhashAn incremental implementation of MurmurHash3 for JavaScript
- acceptsHigher level content negotiation for Deno.
- dosOs info for deno
- cliuieasily create complex multi-column command-line-interfaces.
- y18n📒 the bare-bones i18n library used by yargs
- fathym_atomic_design_kitNo description
- observabilityWIP module for instrumenting Deno programs with OpenTelemetry, transmitting traces and metrics in a standard way.
- evt💧EventEmitter's typesafe replacement
- sax_tsSAX-style (Simple API for XML) in TypeScript
- uddUpdate Deno Dependencies - update dependency urls to their latest published versions
- sleep🦕 module for sleep. You can sleep for a specific amount of time or you can sleep for a random amount of time with this.
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.