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.
- monaA layer that runs on top of Harmony for command handling and stuff.
- momentumMomentum is an open-source framework for building server-side Deno applications in TypeScript. It provides the paradigms and design patterns to guide developers to create robust, scalable, and enterprise-grade applications.
- momento_httpOfficial JavaScript/TypeScript wrapper for Momento HTTP API
- momentNo description
- molu_p1Prototype #1
- moltUpdate dependencies the Deno way
- mojangSimple and lightweight Mojang API wrapper.
- moiraSimple API set for managing dotfile
- modupA CLI tool by @codemonument named `modup` to upgrade deno module binaries installed from deno.land/x via `deno install`
- moduloThe mathematical modulo operation in TypeScript for Deno.
- modulesA set of modules for basic routing and template rendering
- module_urlExtract version number, module name, and more from ESM or TypeScript module URLs.
- module_upgradeA CLI tool by @codemonument named `modup` to upgrade deno module binaries installed from deno.land/x via `deno install`
- module_specifier_resolverThis tool transforms your local TypeScript code that gives you to rewrite file extension of module specifier automatically.
- module_infoGet module info
- modsdeno modules
- modpowmodpow
- modlyteModlyte is a simple to use wrapper for acolytefight modding.
- modify_via_queryNatural and type-safe query to mutate a copy of data without changing the original source
- modern_installer📦 You can now create installers for your Deno 🦕 apps!
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.