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.
- pakoRepublished for Deno. Original: https://www.npmjs.com/package/pako
- packup📦 Zero-config web application packager for Deno
- oak_static_filesNo description
- oak_exceptionA global exception filter middleware by oak.
- npm_ethereumjs_utilNo description
- notifierSend desktop notifications with Deno
- multipartOpine middleware that provides a easy interface to form data and files from multipart requests.
- moulding_tinStruct serialisation for typescript and javascript using Deno
- mooOptimised tokenizer/lexer generator! 🐄 Uses /y for performance. Moo.
- mongodbNo description
- minifierMinify HTML, JS, CSS, and JSON with this WASM-powered module for Deno!
- markdown_recordsA minimalistic library for converting markdown into structured records
- livereloadAutomatic browser reloads when files change for Deno ✨
- latrexA small library for running LaTeX child processes in Deno.
- imageModule for works with images. Decode, encode, resize and etc.
- http🌐 Light-weight http server
- grammy_routerRouter middleware for grammY
- funqlNew way to create web server
- functional_ioIO methods as valid Task monads perfect to write great point-free software in JavaScript that is compatible with most modern browsers and Deno.
- fluent_circleciGenerate CircleCI YAML config from a simple declarative syntax in TypeScript 🛠️ 💻 ✨
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.