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.
- i_ching_astrologyNo description
- i2pMake request on i2p network
- i18next_v4_format_converterThis package helps to convert old i18next translation resources to the new i18next v4 json format.
- i18next_pseudo_localizerA pseudolocalization plugin for i8next
- i18next_locize_backendA simple i18next backend for locize.com which can be used in Node.js, in the browser and for Deno.
- i18next_http_backendi18next-http-backend is a backend layer for i18next using in Node.js, in the browser and for Deno.
- i18next_chained_backendAn i18next backend to chain multiple backends (add fallbacks, caches, ...)
- i18ncsv2jsonNo description
- i18n_csv_to_jsonA script for converts i18n CSV file to JSON format with deno.
- i18nNo description
- i18extractextract i18next translation keys from your source code and translate using Google Translate APIs.
- hyurl_utilsUtility functions of HyURL collection.
- hypoNo description
- hypixelWith thorough IntelliSense support & 100% test coverage, this is an unopinionated async/await API wrapper for Hypixel's Public API. It is developed in TypeScript complete with documentation, typed interfaces for all API responses (and an OpenAPI 3.0 schema!), built-in rate-limit handling, flexible cache support, helper functions, and support for undocumented endpoints.
- hypf🤏 Small (2.3kB MINIFIED + GZIPPED & 0 dependencies) and strong-typed HTTP client for Deno, Bun, Node.js, Cloudflare Workers and Browsers.
- hypervitNo description
- hyperstaticStatic HyperScript/JSX for the DOM
- hyperserveFunctional HTTP server library for Deno, backed by Hyperactive
- hyperdxdenoNo description
- hyperchainhyperscript with chaining
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.