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_correiobrComplete module to consult information about the zip code, calculate the price and delivery times of orders and also perform their tracking
- deno_cordNo description
- deno_cookie_parserNo description
- deno_context_finderExtract context blocks from a configuration file
- deno_configUtility to streamline deno app configuration management through cli, .env and json files
- deno_collectionsA library which adds a Collection data type.
- deno_coinbase_proCoinbase Pro API written in TypeScript and covered by tests.
- deno_code_generatorGenerates unique random codes using a pattern. Useful for generating voucher numbers, tokens and similar.
- deno_cockatielThis is a deno port for https://github.com/connor4312/cockatiel for use until they provide proper deno support themselves
- deno_cli_helpPrint help CLI-option in specific format
- deno_cli_formatA simple CLI formatting utility
- deno_check_updates:mag: Automatically checks deno dependencies versions from import maps file
- deno_check_thai_pidNo description
- deno_chatA basic framework for working with Open AI's Chat API and storing context of previous conversation "turns".
- deno_chartA graph library for deno. Inspired by Chart.js. A simpler implementation for basic bar graphs that save to an image.
- deno_changesetsA Deno native way to manage versioning and changelogs.
- deno_cefThe Chromium Embedded Framework for Deno.
- deno_cache_patchA TypeScript implementation of Deno CLI's module cache
- deno_bunyan_replacereplace for bunyan
- deno_bundlerA Bundler with the web in mind.
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.