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_slack_protocolsImplements the rules for communication between Slack CLI and any Slack app development SDKs
- deno_api_serverAPI Server for deno for functional programmed endpoints
- google_deno_integrationGoogle Integration and Authentication for Deno.
- properties_denoRead and write .properties files.
- deno_pluraldeno-plural module helps you to pluralize or singularize a given word.
- deno_mock_fetchDeno mock fetch implementation
- deno_slack_runtimeHelper library for running a Run on Slack Deno function
- deno_doc_componentsA set of components for rendering deno_doc doc nodes
- deno_markdownGenerate markdown files with ease 🦕
- chalk_deno🖍 Terminal string styling done right
- xmlhttprequest_denoA polyfill of XMLHttpRequest for Deno (and other browser and browser-like environments) by browserifying @driverdan/node-XMLHttpRequest
- kysely_deno_postgres_dialectKysely dialect for PostgreSQL using the deno-postgres client.
- denopendabotDependabot for Deno projects (deprecated)
- deno_socksDeno port of https://github.com/JoshGlazebrook/socks
- deno_utilA collection of util libraries for Deno like logger [supports color, format, level], prompts [password]
- pkce_denoPKCE code verifier and challenge generator for Deno.
- kysely_deno_postgresConnector for Kysely with deno-postgres.
- deno_slack_builderLibrary for building a Run on Slack Deno project.
- denoflowConfiguration as Code, use YAML to write automated workflows that run on Deno, with any Deno modules, Typescript/Javascript codes
- deno2nodeCompile your Deno project to run on Node.js.
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.