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.
- runtypesDeno runtime validation for static types
- pgPostgreSQL client for Deno
- pagicA static site generator powered by Deno + React
- mustacheTemplate render
- mock_fileSynchronous file system API polyfill for deno deploy.
- jmespathA query language for JSON, implemented in Typescript for Deno.
- import_mapAn implementation of WICG Import Maps specification
- hpkeA Hybrid Public Key Encryption (HPKE) module built on top of Web Cryptography API.
- dingtalk_callback_crypto钉钉回调加解密类库 for deno
- better_fluentFluent for Deno. Port of @the-moebius/fluent.
- zcliA framework for building type-safe command-line tools using Zod validators in Deno
- littleA minimalistic connect-like web framework. Automatically works out of the box with Deno Deploy, Deno's Native HTTP and Deno's Standard HTTP server.
- lcov_coberturaMirror of https://gitlab.com/zookatron/lcov_cobertura
- hono_validatorValidator Middleware for Hono
- grammy_autoquotegrammY plugin that forces all sent messages to quote the last received one
- ed25519Fastest 5KB JS implementation of ed25519 signatures
- xdg_portableDetermine XDG Base Directory paths (OS/platform portable)
- sodium🧂 Sodium is a modern, easy-to-use library for encryption, decryption, signatures, password hashing and more
- php_worldExtend Deno world with PHP, by running commandline PHP interpreter in the background, to use both languages in single application.
- oak_rate_limitRate-limiting middleware for Oak server on Deno
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.