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.
- esbuild_loaderA utility module for loading esbuild wasm into Deno runtime from the disk
- esbuild_env_parsingparse environment variable for esbuild API, or just parse any environment variable into the data type you expect it to be
- esbuild_deno_readerResolve files using Deno.readFile
- esbuild_deno_pluginNo description
- esbuild_denohttps://deno.land/x/esbuild_deno
- esbuild_cache_pluginesbuild plugin for Deno that resolves HTTP/HTTPS and npm imports using its cache system
- esbuild_bookmarkletAn esbuild plugin to generate bookmarklets!
- es_utilsVarious small JavaScript utility functions
- es_packageA template for creating and publishing an ES module
- erwin_testtest repo with deno serwer
- ertylib-erty
- errordactylDeno CLI tool for parsing and batching endpoint requests.
- errgoBetter error handling
- errsimple payload wrapper around Error
- erc20_balance💎 Get 2000+ ERC-20 token balances with JavaScript. Supports Node.js and Deno
- eratosthenes_sieveNo description
- equEvaluates Math equations with variables
- epubgenThis is a deno module based on https://github.com/cpiber/epub-gen-memory to generate epub files
- epic_totpKent's Epic Stack TOTP implementation but for deno.
- eosio_wasm_jsA utility tool that serialises EOSIO based blockchain types to WebAssembly hex string.
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.