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.
- markdown_koDeno Markdown Module with korean support
- markdown_it_mindmapA markdown-it plugin for markmap.
- markdown_it_ibUse <i> and <b> along with <em> and <strong> with Markdown syntax — ❌ Deprecated: use the `npm:` specifier instead
- markdenoMarkDeno is a way to generate documentation in markdown files.
- marikaAn API 📦 for the the unofficial MyAnimeList API jikan.moe v4 ported for deno
- maria2Modern & Simple RPC Library for aria2c
- mararadoe_make_tableNo description
- mapkeyA typescript library of functions and classes designed to extend ReMapper
- mapcssTiny, composable Atomic CSS engine
- mapBox of tools for handling map
- manual_tag_bumperDeprecated, please see link below
- mangadlDownload mangas from official manga website tool made in Deno
- mangadex_at_cloudThis is a Deno based reference implementation of the MangaDex@Home client.
- manga_solverSolves encryption of mangas.
- mandatory_envA deno module for handling mandatory environment variables
- mandarine_postgresMandarine.TS is a typescript, decorator-driven framework that allows you to create server-side applications. Mandarine.TS provides a range of built-in solutions such as Dependency Injection, Components, ORM and more. Under its umbrella, Mandarine.TS has 4 modules: Core, Data, Security and MVC, these modules will offer you the requirements to build a Mandarine-powered application.
- mandarina🍊 A web visual novel engine for JavaScript
- makudaunMarkdown to HTML tool
- makehelpMake nice help for deno Makefiles
- makedataNo 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.