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.
- deno_shotDeno WebCapture module
- deno_minimist💾 Parses command line arguments. Port & rewrite of the node library minimist
- deno_graphqlGraphQL HTTP middlewares for Deno server frameworks.
- deno_cli_formatA simple CLI formatting utility
- deno_chartA graph library for deno. Inspired by Chart.js. A simpler implementation for basic bar graphs that save to an image.
- deno_bencodeBencode decoder/encode for Deno
- denashbash interpreter
- ddu_kind_wordWord kind for ddu.vim
- dbjsondbjson gonna help you to write and read json files easily 🦕
- date_functionsNo description
- datadog_apiLightweight client for accessing several Datadog APIs
- csv_parserThe standard Deno module for streaming CSV files.
- create_react_appCreate React App with Deno
- crayon_chalk_aliases👐 Extension package for crayon.js which aims to make its API fully compatible with chalk one
- cors_proxyThis CORS proxy fetches remote URLs and adds CORS headers so that blocked Cross-Origin requests belong to the past.
- common_mime_typesCommon mime type mapping generate from mdn
- codemodCodemod module for making deterministic code modifications.
- cloudflare_worker_jwtA lightweight JWT implementation with ZERO dependencies for Cloudflare Workers.
- classcharts_apiA Node.js and Deno library for requesting information from the ClassCharts API
- churchcalendarthe Calendar of the Church implemented as a deno library
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.