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.
- easyutilA collection of useful utilities to make development with Deno even easier!
- easysecurityBasic security API for Typescript that optimizes for easy use
- easyrouteA simple and pragmatic approach to routing Deno web requests.
- easykvA lightweight and flexible library for working with Deno KV. It simplifies database interactions in Deno applications.
- easyioNo description
- easyemitAn easy-to-use event emitter for Deno & Node.js
- easy_keyvaluesParsing Valve KeyValues text formatting for easy use in nodejs and browsers
- easingsEasing functions for smooth motion in animation
- easeNo description
- eas_denoeas-deno is a TypeScript SDK that authenticates with the main EAS API through tokenization. Giving you the performance of Rust without having to learn FFI in Rust.
- earthstar_rich_threadsNo description
- earthstar_replica_serverAn always-online Earthstar peer for your shares.
- earthstar_cliA complete Earthstar toolbox in the console.
- earrayExtended array for deno
- eagleNo description
- dyrAccess Yr's weather API and Nominatim's API with Deno
- dyno🦕 A dependency management for Deno
- dynamodbdeno <3 dynamodb
- dynamoA useful configuration library for Deno applications
- dynamic_script_loader🐼 Tiny (~300B) library to dynamically load js files only when they're needed.
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.