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.
- trino_clientJavascript client for Trino
- trimmerValidation library for deno
- triesTries and PATRICIA Tries Data Structures
- triceratopNo description
- triblesA simple immutable distributed knowledge base for tribles (binary triples).
- trellisWrite Dockerfiles and CI pipelines in TypeScript.
- treesapNo description
- treehouseNo description
- treebottreebot is a framework to create decision trees in deno/node
- tree_lint🌴 ✅ A command-line tool designed to analyze and enforce a specific hierarchical folder structure within TypeScript projects.
- treeDeno's library to traverse filesystem tree.
- treblecross_solverA treblecross solver written in Deno
- traverse_astNo description
- transposearrayPerform the matrix operation transpose on an array respecting type information.
- transmTranslation assistant tool for Markdown document :us: :jp:
- translite🌎 A light, flexible, and dynamic translation library in Typescript
- translatorsNo description
- translatorGoogle Translation API for Deno and ESM
- transform_accentsTypescript function to transform accents
- transferablesUtility library that lists out all transferable objects (https://developer.mozilla.org/en-US/docs/Glossary/Transferable_objects) that can be transfered between Workers and the main thread
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.