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.
- indent_and_wrapFinds and replaces common indent, hard-wraps text, generates text tables and table-based complex text layouts. Can work on text that contains terminal escape sequences.
- htmlparserDeno port of `htmlparser2`
- g_aUtilities for server side processing of Google Analytics in Deno CLI and Deploy
- flattenFlatten or unflatten a nested Javascript object by delimiter keys.
- file_extension📁 Get the extension of a file
- duckdbblazing fast duckdb bindings for deno
- dotenv_cliMirror of https://gitlab.com/zookatron/dotenv_cli
- document_irIntermediate Representation for content
- distreeDirectory structure trees upon plain objects.
- directoriesa library that provides config/cache/data paths, following the respective conventions on Linux, macOS and Windows.
- denippet_vimA snippet plugin for Vim/Neovim, powered by TypeScript
- decode_formdataDecodes complex FormData into a JavaScript object
- corejsStandard Library
- changelogNode & Deno package to parse and generate changelogs
- andersNo description
- ziplandServe file server with single zip file as file system in Deno.
- wasmMonorepo for Javascript WebAssembly packages by Wasmer
- vite_deno_pluginA Vite plugin that can resolve Deno modules.
- resend_jsA JavaScript library for Resend that doesn't require Node.js
- npm_fetcherFetches npm packages and writes them to disk
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.