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.
- kwikKwik is a deno database using messagepack files.
- kvxA simple wrapper around Deno KV
- kvviewerKV 📺 - A simple tool for inspecting your DenoKV database
- kvtoolCLI utility for Cloudflare Workers KV
- kvstorageAn implementation of the StorageArea interface for Deno.
- kvp🚀 Transactions that commit without overwriting one another, for Deno KV.
- kvmqLibrary inspired by BullMQ for Deno
- kvfsLibrary for saving bigger files in Deno KV
- kvdexA high-level abstraction layer for Deno KV with zero third-party dependencies by default 🦕🗝️
- kvdbDatabase wrapper for Deno KV
- kvcacheNo description
- kv_utilsCollection of utilities for working with Deno KV
- kv_storageAn implementation of the StorageArea interface for Deno.
- kv_sqliteKey-Value storage backed by SQLite
- kv_sessionNo description
- kv_memoizeNo description
- kv_entityTyped library for specifying and storing entities in a Deno.Kv database.
- kv_cronUse Deno Kv API to register cronjobs.
- kv_connect_kitMinimal Typescript client implementing the KV Connect protocol. Access Deno KV remotely from any Javascript environment like Node, Cloudflare Workers, Bun, Deno, and the browser.
- kv_apiWORK IN PROGRESS: Attach a flexible REST API to your Deno web app to manage data in Deno KV
Q&A
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?
Name squatting is not allowed on the deno.land/x/. If you feel that a module is not currently usable, has not been legitimately under development for more than 90 days, and you have a concrete proposal to publish a well-maintained module in its place, please contact support.