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_doc_html_testhttps://gitlab.com/bdelseny/deno_doc_html_test
- deno_doc_components_cnA set of components for rendering deno_doc doc nodes
- deno_discordNo description
- deno_dequeA modern double-ended queue for TypeScript/JavaScript.
- deno_deploy_serverNo description
- deno_denoNo description
- deno_demoNo description
- deno_dbA Simple Deno JSON DB
- deno_databaseA database package to use in deno
- deno_dash_docNo description
- deno_csvNo description
- 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
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.