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.
- cafCaf is a light framework for developing RESTful Apps in a quick and convenient manner.
- caesar_ciphercaesar cipher implementation in deno.
- caesarThe Deno Framework for Software Craftsmen
- cactodbA simple JSON based line by line database written in Deno.
- cache_mapsetMaps and Sets with cache replacement policies, TC39 proposal-policy-map-set implementation
- cache_injectorNo description
- cache_forkA fork of "🥌 Deno cache library"
- cabinetCabinet, the easier way to manage files in Deno
- cabbagedeno native http helper
- c3_4_denoA simple transformation of c3 for use within a deno workflow
- c07d7016f4f94f1cb9c502269ad23d44No description
- bzfqueryJavaScript/TypeScript version of bzfquery for Deno with no external dependencies. It can also be used as a library or from the command line.
- bytsNo description
- bytesByteArray module for deno for convenient work with bytes and bits.
- bytebufA byte buffer for encoding and decoding binary data in JavaScript.
- bytearrayThis project has been discontinued, I highly recommend checking https://deno.land/x/net/mod.ts?s=Packet
- byte_codec_tsa schema based serializer for primitive javascript types with no external dependencies.
- byteA disk unit conversion library for JavaScript.
- byond_clientbyond_client is a Deno implementation of the byond topic protocol used for communicating between byond servers
- bwtBetter Web Token - an iteration of web tokens with a bunch of improvements
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.