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.
- pastedenoUniversal Pastebin client for Deno/Node
- parse5Ported from inikulin/parse5 but for Deno.
- fetchNo description
- fastest_levenshteinThe fastest implementation of Levenshtein distance algorithm in JavaScript.
- fast_forwardAn easy to use ffmpeg module for Deno. 🦕
- expectoAn assertion library with an "expect" style interface, inspired by Chai's and built for Deno.
- deno_libphonenumberNo description
- cmdCommander.js (command-line interfaces) for Deno.
- cache_dirReturns the path to the user's cache directory.
- typed_regexA typescript library for type-safe regex for named capture groups, deno fork
- tgsnake_loglogging library for tgsnake
- sweetidAlphanumeric IDs, powered by Nano ID
- oak_upload_middlewareThis middleware automatically organizes uploads to avoid file system problems and create dirs if not exists, perform validations and optimizes ram usage when uploading big files using Deno standard libraries!
- itertools🦕 A TypeScript port of Python's itertools and more-itertools for Deno
- denodashA utility library, similar to Underscore and Lodash, but written Typescript-First, designed for use in Deno
- denockerA Docker client library for Deno
- danielduel_ultra_stack_mesozoicA generic build system for Deno web apps
- utilsNo description
- test_suiteAn extension of Deno's built-in test runner to add setup/teardown hooks and make it easier to organize tests in a format similar to Jasmine, Jest, and Mocha.
- react_icons_fadeno fresh react-icons for fa
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.