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.
- httpcacheHTTP Caching for Deno - in memory and redis storage support. Inspired by the Service Worker Cache API.
- tunerService Configurator for Deno
- compare_versionsCompare semver version strings to find which is greater, equal or lesser.
- worker_typesDeno-compatible types for service workers and Cloudflare workers
- offgrid_engineView Engine for Offgrid Service Worker
- datadog_apiLightweight client for accessing several Datadog APIs
- workers_routerA router for Worker Runtimes such and Cloudflare Workers or Service Workers.
- workers_htmlHTML templating and streaming response library for Service Worker-like environments such as Cloudflare Workers.
- verseA lightweight tool for serving http built on top of the Deno standard library.
- valveSteamy is a library made to help interact with Valve's REST APIs for their various games and services by providing easy asynchronous functions to call them, along with a key manager, and type checking to boot.
- utilities🦕 module for several kinds of utilities 🛠 like random delays, shuffling array contents etc. Feel free to add stuff you find useful via PR. 🤓
- trypoxylusDeno based service engine
- timsTextual display of millisecond durations and in several languages.
- teleportDeno.Listener as a service
- swdevNo bundle frontend by service-worker
- strawmanA Deno-based service virtualization solution
- steamySteamy is a library made to help interact with Valve's REST APIs for their various games and services by providing easy asynchronous functions to call them, along with a key manager, and type checking to boot.
- statebacked_tokenUtilities to create end-user authentication tokens for the State Backed XState backend as a service
- statebacked_machine_defMachine definition helpers for the StateBacked.dev XState backend as a service
- statebacked_machineMachine definition helpers for the StateBacked.dev XState backend as a service
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.