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_rconAn RCON client for Source RCON Protocol (e.g. for CS:GO server)
- deno_qrcodeNo description
- deno_pty_ffideno wrapper over rust protable-pty that exposes a simple interface
- deno_proxyNo description
- deno_promptpayGenerate Thai PromptPay QR code string and Base64-encoded images in Deno.
- deno_project_managerA project manager for Deno.
- deno_power_doctestNo description
- deno_pixabaysearch image and video from pixabay in deno
- deno_pipelineA ready-to-use CI/CD Pipeline and jobs for Deno projects.
- deno_pipeSimple generic middleware for Deno
- deno_permessage_deflate_qpNo description
- deno_pastebinTiny Pastebin API wrapper for Deno
- deno_outdatedFind outdated dependencies in your deno project
- deno_openOpen is a package for opening URLs, files and executables with Deno. Inspired by sindresorhus' open.
- deno_nrepl_clientNo description
- deno_nestRefer to nestjs to realize some common functions for Deno, support hono and oak
- deno_msj_controllersTratamento de request em cadeia
- deno_mongo_schemaExtend from deno_mongo, support Schema and extend some API
- deno_module_playgrounda playground
- deno_modA collection of modules written in TypeScript for common Deno programming tasks.
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.