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.
- aloedbLight, Embeddable, NoSQL database for Deno 🦕
- kysely_deno_postgres_dialectKysely dialect for PostgreSQL using the deno-postgres client.
- elmishElm-like Maybe and Result types for Deno
- windmill_helpersA repository that contains utils functions used by windmill deno scripts
- blocksGit-based Visual CMS for Deno, </> htmx and Tailwind apps. Deploy on any Deno-compatible host.
- webgenWebGen is a UI Library. Layout and Design in one. No Custom Toolchain
- computed_types🦩 Joi like validations for TypeScript
- blake2bBLAKE2b implemented in WebAssembly
- ts_transpilerA standalone typescript transpiler based on deno, running in the browser
- sha256SHA2-256 4 Deno
- parsedownWASM code for parsing Markdown into HTML with light output tweaking
- little_cronyA CRON library for Deno by Mandarine.
- aquaA minimal and fast 🏃 web framework for Deno
- fresh_ga4A plugin for Fresh to add GA4 middleware.
- branch📠 Denosaurs pretty logger
- rutt🛣️ A tiny and fast http request router designed for use with deno and deno deploy
- fff🌟 The Flexible & Functional Frontmatter Solution.
- collectionsCollection data structures that are not standard built-in objects in JavaScript. This includes a vector (double-ended queue), binary heap (priority queue), binary search tree, and a red black tree.
- commit✍️ Parser for the conventional commits specification
- typeboxJSON Schema Type Builder with Static Type Resolution for TypeScript
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 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?
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.