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.
- runtsFilesystem-based subcommand dispatcher for Deno.
- runtime_compatAbstraction layer for compatibility of common operations between Node.js and Deno
- runtimeNo description
- runrcConfigurable per-directory command aliases and scripts
- runner_apiVim plugin to run the current file with custom (typescript) scripts
- runnerrun deno scripts with deno easily
- runmeA JavaScript module to use Runme in Node.js.
- rune[WIP] The soon-to-be home of Capi's fluent API toolkit
- run_with_limitRun promise-returning & async functions with limited concurrency
- rules_storeNo description
- rulesA simple Deno 🦕 TypeScript runtime validator with good performance, zero dependencies and developer friendly UX
- ruhukaA REST API Client
- rubylizeA CLI tool that append ruby to kanji characters from passed stdin.
- ruby_pipelineA ready-to-use CI/CD Pipeline for Ruby projects
- rubiksRubiks is a 0 dependency extendable logging library for modern applications.
- rubico🏞 [a]synchronous functional programming
- ruaRandom user-agent generator module for Deno.
- rtriExponentially retry a function in JavaScript
- rtrA fast HTTP router and type-safe middleware library for Fetch compliant runtimes
- rtcv_scraper_clientA client / helper program for CV scraper to send it's data easily to RT-CV
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.