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.
- league_dataA Deno (and Node) library which provides official League of Legends game data and static content links.
- json_patch[WIP] A useful tool to generate and apply json patch (rfc6902) in deno.
- fresh_storiesFresh storybook alternative
- envalidEnvironment variable validation for Deno.
- iniAn ini parser/serializer in TypeScript for the Deno runtime
- google_jwt_saGet Google Auth Token for OAuth 2.0 for Server to Server Applications/Google APIs
- deno_slack_hubConnectors used to build coded workflows for Run on Slack apps using Deno
- context_injectNo description
- color_utilA powerful module which provides util for converting and generating colors in deno.
- yaml_loaderA yaml file loader & parser module for Deno
- uuid7Generate UUIDv7 identifiers in JavaScript (or TypeScript)
- slack_socket_modeRecieve events from Slack's Events API over a WebSocket connection. Deno port of @slack/socket-mode
- remapperA framework for Beat Saber map scripting.
- oi_lume_vizLume Plugin that enables charting
- markdownDeno Markdown module forked from https://github.com/ts-stack/markdown/tree/bb47aa8e625e89e6aa84f49a98536a3089dee831
- iroFast and clean terminal coloring and styling utility for Deno and Node.js.
- dwmDeno Window Manager: Cross-platform window creation and management
- drizzleDeno port of the drizzle-orm library
- dfetchPromise based HTTP client for Deno inspired by axios.
- dash_compilerNo 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 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.