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.
- festA collection of essential TypeScript types
- uniqueA Typescript UUID v4 implementation
- mtkrutoCross-runtime JavaScript library for building Telegram clients
- discordwebhookA module to create/edit/delete webhook messages on Discord using their API | First TypeScript & Deno project
- js2xmlConvert JavaScript objects to XML
- deno_fmtProgrammatic code formatter for Deno and Deno Deploy, allowing you to format code on the fly. Supports all features and options of the `deno fmt` command.
- grammy_commandsEnhanced command managment for grammY.
- githooksAllows you to associate deno tasks with githooks by extending the native deno.json configuration file
- fathym_atomic_socialA set of atomic components for use with Preact/Tailwind based sites needing social UX.
- worker_ionicNo description
- acornA focused RESTful server framework for Deno 🌰🦕
- lume_initTool to init & upgrade Lume projects
- notranspile_saxesAn evented streaming XML parser in JavaScript
- postgresjs_patchedPostgres.js - The Fastest full featured PostgreSQL client for Node.js, Deno, Bun and CloudFlare
- diff_kitDeno lib that compares 2 strings and generates result like assertEquals(), also in HTML
- deno_slack_protocolsImplements the rules for communication between Slack CLI and any Slack app development SDKs
- swcThe SWC compiler for Deno.
- archDetect OS architecture
- fathym_open_biotech_atomicThe Atomic library used for building frontends for the Fathym OpenBioTech project.
- python🐍 Python interpreter bindings for Deno and Bun.
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.