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_mockA simulation data generator
- deno_mochaAn intuitive implementation of a BDD-style Deno.test wrapper
- deno_midiA Deno wrapper for the RtMidi C++ library that provides realtime MIDI I/O
- deno_mecab🇯🇵 Analyze Japanese from Deno with MeCab
- deno_maylilyA changed copy of Maylily a distributable, serverless, and customizable unique ID generator based on Snowflake.
- deno_lysutilVarious small utilities by Lyssieth, for Deno.
- deno_lp_apiDeno Liveperson API
- deno_loki_handlerLoki logger for deno!
- deno_logLightweight logger with an extensible configuration 🦕
- deno_lodashProvides lodash for Deno
- deno_kv_http🦕 Deno KV HTTP wrapper.
- deno_kv_fsDeno KV file system, compatible with Deno deploy. Saves files in 64kb chunks. You can organize files into directories. You can control the KB/s rate for saving and reading files, rate limit, user space limit and limit concurrent operations, useful for controlling uploads/downloads. Makes use of Web Streams API.
- deno_kv_collectionsTurn Deno KV into your own document database!
- deno_kv_authHigh-level OAuth 2.0 powered by Deno KV.
- deno_kv_adminAbout A web interface for Deno KV
- deno_koishiNo description
- deno_koaA middleware framework for Deno's http serve🦕. Transplanted from Koa with ❤️
- deno_jsonrpc2_cbsA JSON-RPC 2.0 library for Deno
- deno_json_rpcDeno implemenation of JSON-RPC
- deno_json_dbA Simple Deno JSON DB
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.