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.
- cities🦕 module provides information about cities on earth + mars
- citadelThe next version of the Citadel SDK
- circular_bufferEasy to use and high performance circular buffer
- ciniiNo description
- cidr2rangeConvert utilities for CIDR and IP address
- cidrWritten for Deno to determine whether CIDR contains a certain IP
- cicdDeno Module for CICD - which can e.g. be used in GitHub Actions
- cicada_modulesThe Cicada Module registry
- cicadaWrite CI/CD pipelines using TypeScript
- chunkSources for the chunk TypeScript library.
- chujkotek
- chuggerA tool for managing web assets...
- chronverVersioning for the rest of us
- chronosChronos Task Scheduler is a lightweight and easy-to-use task scheduling library for Deno, with support for both cron-based and interval-based scheduling. With Chronos, you can schedule and manage tasks in your Deno application with ease, ensuring that they run on time and as expected.
- chrono_uuidNo description
- chronark_timeTime utilities inspred by go's time standard library.
- chromatic_pipelineA ready-to-use CI/CD Pipeline and jobs for Chromatic projects.
- chromaTypeScript library for all kinds of color manipulation.
- chris_airbrake_error_notificationCreate Airbrake error notifications from Deno
- chostsUnder development
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.