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.
- decoGit-based Visual CMS for Deno, </> htmx and Tailwind apps. Deploy on any Deno-compatible host.
- colorlogDeno library for printing colored logs
- mrmimeA tiny (2.8kB) and fast utility for getting a MIME type from an extension or filename
- kia🦕 Simple terminal spinners for Deno
- tgsnake_corecore library for tgsnake for connecting to telegram api
- media_typerSimple RFC 6838 media type parser and formatter for Deno.
- basejumpfunctionsDeno packages for Supabase edge functions
- kviewA web app for Deno KV
- deno_pluraldeno-plural module helps you to pluralize or singularize a given word.
- disposePolyfills for the DisposableStack and AsyncDisposableStack interfaces from the TC39 Proposal for Explicit Resource Management.
- monads👻 Option, Result, and Either types for TypeScript; Inspired by Rust
- url_parseA simple url builder based on the URL object for Deno with typescript
- grammy_filesHandle and download received media files.
- slugDeno library for converting arbitrary strings into valid slugs
- razela command executor with caching for data processing pipelines
- tree_fnsSimple utility functions for tree structure
- dsddbA "Dead Simple Deno DataBase".
- composableGit-based Visual CMS for Deno, </> htmx and Tailwind apps. Deploy on any Deno-compatible host.
- promise_poolNo description
- deno_mock_fetchDeno mock fetch implementation
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.