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.
- caught_object_report_jsonJS Error JSON representation
- caturCatur Core Engine
- catppuccin_toolbox🧰 Soothing pastel tools for development
- catppuccin🎨 Soothing pastel theme to use within your projects!
- catch📦 Blazing fast, light-weight package manager
- catalystCatalyst is a set of patterns and techniques for developing components within a complex application.
- cat_on_oak(Deno) Template engine for Deno
- catCat is an API wrapper that allows you to easily generate pictures of cats (Powered by TheCatAPI).
- casualdbSimple JSON "database" for Deno with type-safety! ⚡️
- cassysDNS in Deno. Made to protect private Network & load balancer of ip. Made for the good people who need to see source code
- cashA shell tool for Deno.
- cases_of_testRun test locally with only/skip flag similar to jest/vitest but with the condition that it can detect there are tests flagged with only and it will fail on CI/CD environment, or fail on any condition defined by developer
- casecrusherNo description
- case_styleA string validator and formater for case Style
- cascadeA bot framework for discord using discordeno
- carriageway🦥 Run async functions with limited concurrency and optional rate limiting
- carpenterbuilder-like pattern for all things Deno
- carolA Deno port of carlo
- cargo_throttleRate limit your cargo applications
- cargo_parcel_twindNo description
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.