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.
- zstdZstd bindings for the Deno TypeScript/JavaScript runtime
- zsh_historyRead and parse your zsh history
- zrxAn unofficial 0x Protocol API client for Deno.
- zoraLightest, yet Fastest Javascript test runner for nodejs and browsers — 🦕 Deno port
- zoppityPippity poppity give me the zoppity
- zooNo description
- zonos_apiA simple integration with the Zonos REST API
- zonesNothing to see here, yet
- zonefileA DNS zone file generator and parser written in Javascript.
- zoicA REST API-caching middleware library for Oak/Deno
- zodenvNo description
- zodash_doreamonZero's Standard Lib or Doreamon
- zod_semverA simple deno module by @codemonument with a zod schema for validating semver. Uses official regex and is cross-posted to npm as zod-semver
- zod_ffValidate forms with ease using Zod and get user-friendly error messages or valid typed data, compatible with any framework on both server and client side.
- zod_endpointsZod Router
- zod_apiConfigure API clients and endpoints using Zod
- zoakDeno + Zod + Oak + OpenApi
- zlib.esECMAScript/Deno lightweight zlib implementation
- zipper_client_jsAn easy way to interact with Zipper Applets from anywhere that supports ESM, CommonJS, or TypeScript.
- zipfuseDeno module for accessing zip files as a filesystem
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.