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.
- graphmanQuikly scaffold a postman collection for a GraphQL API. Compatible with Postman & Insomnia.
- get_stdinGet stdin as a string or buffer
- generate_passwordGenerate Password is a generating random and unique passwords.
- freshwindDeno Fresh plugin for working with Twind v1
- ffmpegffmpeg module for Deno
- fathym_atomic_reportsNo description
- extractutil for extract text
- expressAn Express port for Deno.
- exiumLexer to parse multiple languages
- epub_metadataGet a subset of ePub metadata.
- ensure_versionSimple version ensurer for Deno that check {deno, typescript, v8} version for users of your module and prevent them from incompatibylities error
- easytsjs library written with ts, use select and chan like golang in js.
- dropserver_lib_supportInterfaces dropserver_app uses to interact with Dropserver within Deno sandbox
- dnsDNS in Deno. Made to protect private Network & load balancer of ip. Made for the good people who need to see source code
- dndbA Deno 🦕 persistent, embeddable and optimized NoSQL database for JS & TS
- discord_hookAn easy way to use Discord webhook with Deno.
- die_bartA template engine similar to mustache and handlebars, but slightly different
- deps🕴deps.ts manager for Deno (highly WIP)
- denocheerioCheerio - Porting Cheerio Node Module To Deno using esm.sh
- deno_usbhidapi🦕 Deno FFI bindings for the HIDAPI library to access USB devices.
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.