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.
- cargo_loadNo description
- cargo_inspectNo description
- cargo_guardNo description
- carefulSafe containerization of values for TypeScript
- cardsDeno playing cards
- cardinalA Deno module to get compass direction (16 directions) from degree.
- cardcheckrThis repository provides a collection of functions for validating credit card numbers in JavaScript/TypeScript. The functions perform various checks to ensure that a credit card number is valid based on different criteria.
- carcajada_artificial_test_moduleThis repository is my personal test site for all things Deno, Fresh, and JSR. I don't aim for this to be seen by others, don't expect clarity.
- captchaCreate captcha using canvas module.
- captainSubtitle library
- capsule💊 UI component as a bundle of local event handlers
- capsid💊 Declarative DOM programming library. Lightweight (1.79 kb).
- caproverapiDeno API Wrapper around Caprover API
- capi[WIP] A framework for crafting interactions with Substrate chains
- capSimple cli arguments parser written in typescript for node/Deno
- canvyCanvas interface for Deno
- canvasenoCanvas API for deno
- canvas_formYou can choose some forms by canvas-form
- canvacordSimple & easy to use image manipulation module for beginners.
- canonifyA tiny JSON canonicalize function written in Typescript. Creates crypto safe predictable canonicalization of JSON as defined by RFC8785 and is usable in Deno, Node.js, and browsers.
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.