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.
- deno_siftUse Mongodb queries in JavaScript
- ddenodbMySQL, SQLite, MariaDB, PostgreSQL and MongoDB ORM for Deno
- atlas_sdk3TypeSafe MongoDB Atlas Data API SDK for Deno & Deno Deploy
- monoutilsVarious utility functions, objects and types for Deno projects
- monopoleA powerful and flexible dependency injection container for TypeScript/JavaScript applications. Monopole provides a modern, module-based approach to dependency injection with support for async resolution, property injection using TC39 Stage 3 decorators, and comprehensive lifecycle management.
- monoovaMoonova API scripts
- mononykusSvelte and partial hydration with Deno
- monodenocreate a monodeno app using dpx
- monocypherWebAssembly port and JS wrapper library for Monocypher (https://monocypher.org)
- compyMinimalist (yet powerful) monorepo manager for Deno
- wasmMonorepo for Javascript WebAssembly packages by Wasmer
- rexjsRex: A Monorepo Tool designed with Deno for use in multiple runtimes for efficient project maintenance.
- rex_cliRex: A Monorepo Tool designed with Deno for use in multiple runtimes for efficient project maintenance.
- mem🤖 Proportional and monospaced sans light pixel font family.
- callsitesMonorepo for various utility modules for the Deno ecosystem.
- bodarMono repo for deno versions of TotallyLazy, LazyRecords, Yadic, UtterlyIdle
- barrelBarrel CLI 🛢 - Mono-Repos for the Multi-Repo teams.
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.