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.
- fp_tsFunctional programming in TypeScript
- memoizyPowerful memoization library for deno
- escaladeA tiny (183B to 210B) and fast utility to ascend parent directories
- p_retriedRetry a promise-returning or async function. Abstraction for exponential and custom retry strategies for failed operations
- uniloggerLogger utility module for Deno
- argsExtensible CLI arguments parser for Deno with intelligent TypeScript inference
- validation🦕 Validation functions for Deno
- sitemapDeno CLI to create a sitemap from build output
- mailgunThis simple and lightweight Deno package allows you to easily send emails using the Mailgun API!
- eventsourceEventSource in Deno
- d3nodatachart component library for fresh
- varyManipulate the HTTP Vary header for Deno
- debug📝 Tiny debugging utility
- lume_theme_simple_blogLume theme to create a simple blog
- deno_api_serverAPI Server for deno for functional programmed endpoints
- is_urlsimple URL validator with Typescript for Deno 🦕
- fresh_sessionDead simple cookie-based session for Deno Fresh.
- encodeurlEncode a URL to a percent-encoded form, excluding already-encoded sequences. Build for Deno
- i18next_fs_backendi18next-fs-backend is a backend layer for i18next using in Node.js and for Deno to load translations from the filesystem.
- react_iconsreact-icons ported for deno / preact
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.