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
.
- choredChores, sorted.
- chordNo description
- chompyPowerful server fetch primitives for Deno
- chompuNo description
- chompLibrary of (arguably) useful Deno classes
- chokidarAn efficient wrapper around node.js fs.watch / fs.watchFile / FSEvents
- chockblainNo description
- chline_linkApi wrapper for simple, modern, free and privacy-friendly URL shortener.
- chimeraA fantastic configuration library for Deno
- child_processNo description
- chickenconfighandle json config in Deno
- chicAn easy to use server system for deno
- chibi_rpcNo description
- chiaNon production chai
- chess_typescriptA minimal Chess Engine fully written in typescript.
- chess_denoNo description
- chessA Typescript Chess engine.
- chenea good web framework
- chemin🥾 A type-safe pattern builder & route matching library written in TypeScript
- chefoven is toolkit for CookLang powered by Deno
Q&A
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?
Name squatting is not allowed on the deno.land/x/. If you feel that a module is not currently usable, has not been legitimately under development for more than 90 days, and you have a concrete proposal to publish a well-maintained module in its place, please contact support.