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.
- buildNo description
- bugsplatDeprecated! Please use bugsplat from esm.sh
- buffer_crc32crc32 that works with binary data and fancy character sets, outputs buffer, signed or unsigned data and has tests. Derived from the sample CRC implementation in the PNG specification: http://www.w3.org/TR/PNG/#D-CRCAppendix
- bufferQueue backed by a linked list with Iterable interface
- buf_connectHelpers for Buf Connect, type-safe protobufs & gRPC for the web. (Includes Oak middleware.)
- bucketsDEPRECATED - Bundle assets and scripts in a single executable file. Deno
- btreemapBTreeMap is a library that implements Map based on a B-Tree.
- btcboxUniversal BTCBOX API client
- btcGet the current BTC price in deno
- bsv_wasmBSV stdlib written in Rust and runs in WASM environments
- bson_denoport of js-bson to deno
- bsonBson for deno
- bsmapGeneral-purpose scripting library for Beat Saber map using TypeScript with Deno.
- brunnerNo description
- bruhThe thinnest possible layer between development and production for the modern web.
- browserstorageNo description
- browser_storageAn abstracted storage library for browser applications that interfaces with localStorage, sessionStorage, in-memory storage, or any custom serializer. It provides serialization capabilities with optional key prefixing for better storage management.
- browser_notifierNo description
- brontoroutusNo description
- brokersNo description
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.