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.
- atomic_ui_reactTiny, Unstyled, Accessible React components/hooks, designed to integrate with Atomic CSS.
- atomNo description
- atmpAdd a safe layer to your functions and catch errors without try/catch blocks. Inspired by domain-functions.
- atletNo description
- atlas_sdk3TypeSafe MongoDB Atlas Data API SDK for Deno & Deno Deploy
- atlas_packπΊοΈ Aseprite sprite sheet parser, animator, and toolset for the browser and Deno.
- atlasA web application framework for Deno π¦
- atenas_testNo description
- atenas_cliThe Deno CLI Tool for Atenas
- atenasThe Deno framework for building server-side applications
- atcoderNo description
- at_testNo description
- asyncqueueNo description
- asyncableNo description
- async_queueAn Asynchronous Queue implementation for JS/TS (Deno)
- async_lockA simple lock to synchronize async code
- async_generator_callbackConverts callbacks to asyncGenerators
- async_functionA simple Deno module for accessing the `AsyncFunction` class and type.
- async_contextNo description
- async_channelsInspired by Go & Clojure Channels, async_channels provides channels as an asynchronous communication method between asynchronous functions.
Q&A
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?
Name squatting is not allowed on the deno.land/x/. If you feel that a module is not currently usable, has not been legitimately under development for more than 90 days, and you have a concrete proposal to publish a well-maintained module in its place, please contact support.