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.
- ./jszipA JSZip wrapper for handling zipfiles in deno
- ./jssmFast, easy Javascript finite state machines with visualizations; enjoy a one liner FSM instead of pages. MIT; Typescripted; 100% test coverage. Implements the FSL language.
- ./installDeno Binary Installer
- ./freshThe next-gen web framework.
- ./fnvAn implementation of the 64 bit FNV-1a algorithm, for deno.
- ./flatA collection of postprocessing utilities for flat
- ./event📆 Strictly typed event emitter with asynciterator support
- ./eszipA compact file format to losslessly serialize an ECMAScript module graph into a single file
- ./esbuildNo description
- ./eggs🥚 Nest.land's Multipurpose CLI - fixed for Deno 1.26
- ./dotenvDeprecated. Use std/dotenv instead.
- ./denoflateWebAssembly port of Rust's flate2, a Rust implementation of Deflate, Gzip, and Zlib compressions
- ./deno_slack_hooksHelper library implementing the contract between the Slack CLI and Slack application SDKs
- ./deno_domBrowser DOM & HTML parser in Deno
- ./dejsejs template engine for deno.
- ./base64base64 strings from/to Uint8Arrays
- ./aws_apiFrom-scratch Typescript client for accessing AWS APIs
- ./acceptsHigher level content negotiation for Deno.
- zhconvNo description
- xeoVariant of Lume Simple Blog theme
Q&A
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 on deno doc and 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?
Name squatting is not allowed on the deno.land/x/. If you feel that a module is not currently usable, has not been legitimately under development for more than 90 days, and you have a concrete proposal to publish a well-maintained module in its place, please contact support.