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.
- my_grammyNo description
- my_dummy_npm_and_deno_moduleExample/tutorial on how to setup denoify
- my_diviner_atomic_design_kitThe Atomic Design Kit for My Diviner
- my_deno_utilsSome personal deno utils.
- mxxNo description
- mwdenoWIP module for instrumenting Deno programs with OpenTelemetry, transmitting traces and metrics in a standard way.
- mvola_cliA command-line tool for MVola API
- mvolaDeno library for the MVola API
- mvcNo description
- mux_async_iterableMultiplexer of async iterables for JavaScript, written in TypeScript
- muxMux is a small routing library for Deno
- mutilmUtil : Multi minimum Util
- museumjsWiki-Framework on Deno
- museYoutube Music API (InnerTube) client for Deno, Node and the browser
- murmur_hash_3TypeScript implementation of Murmur Hash 3.
- munoA Deno microframework for building http services.
- munkresA lightweight and efficient implementation of the Munkres (Hungarian) algorithm for optimal assignment.
- munatcomponentsComponent library for deno fresh.
- multisocketWebSockets but with channels, for Deno and the browser
- multipart_streamCreate ReadableStreams from multipart forms without allocating the entire form on the heap
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.