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.
- axink_cliNo description
- axinkNo description
- axilNo description
- aws_switcherCLI tool to quickly switch configured AWS profiles
- aws_smssm into ec2 machines via sso sessions
- awaitiumPut your await on fire and chain together async functions, promises and syncronous code in one line.
- awaited_surrealdbWait for completed connection before running queries :D
- await_toA Deno utility module that allows awaiting on promises - Go style
- await_mutexDeno module for blocking execution of a section of code to one at a time
- avsUnit testing framework.
- avialaea simple dev server build with deno
- avatarGenerates a random avatar for any given identifier. Always generates the same avatar for the same identifier.
- autopilot🚀 Cross-platform desktop automation module for Deno.
- automonthNo description
- autometricsEasily add metrics to your system – and actually understand them using automatically customized Prometheus queries
- automerge_wasmA JSON-like data structure (a CRDT) that can be modified concurrently by different users, and merged again automatically.
- automerge_repo_network_supabaseA Supabase network adapter for automerge-repo
- automergeA JSON-like data structure (a CRDT) that can be modified concurrently by different users, and merged again automatically.
- automationNo description
- automated_omusubiNo 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 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.