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.
- effectionStructured concurrency and effects for JavaScript
- discord_api_typesUp to date Discord API Typings, versioned by the API version
- fluentciSet up and run your CI locally or in any CI Provider in a consistent way
- patched_alephThe Full-stack Framework in Deno.
- momentjsDeno-compatible version of momentjs
- dntDeno to npm package build tool.
- jszipA JSZip wrapper for handling zipfiles in deno
- cronerTrigger functions or evaluate cron expressions in JavaScript or TypeScript. No dependencies. Most features. Node. Deno. Bun. Browser.
- kd_clientsVarious HTTP clients for miscellaneous use.
- mqttMQTT in TypeScript for Deno, Node.js, and browsers
- cache🥌 Deno cache library
- deno_imageDeno module for resizing images.
- zod_utilzFramework agnostic utilities for Zod
- xmlpXML Parser for Deno
- hexAn ecosystem delivering practices, philosophy and portability. Powered By Deno and JavaScript.
- velociraptorThe npm-style script runner for Deno
- value_schemasimple, easy-to-use, and declarative input validator; supports Node.js, TypeScript, Deno, and Bun
- microlemonA collection of Microservice implementations with a common interface. By Mandarine for Deno.
- dnitdnit: typescript (deno) task executor
- graphql_transport_wsThe WebSocket graphql-transport-ws sub-protocol implementation
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.