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.
- oak_uploadThis 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!
- numeralNumeral is a standard Deno module for formatting and manipulating numbers.
- notranspile_loggerFlushing wrapper for Deno std/log
- nonstdA library for useful features that aren't currently in the std library.
- node_commandThis denojs module spawns a child process. It effectively writes the specified Node.js function directly to the standard input (stdin) of this process. This unique approach, while introducing some overhead, maintains practical usability for a variety of applications, particularly those where ultra-high speed is not a critical factor.
- mwdenoWIP module for instrumenting Deno programs with OpenTelemetry, transmitting traces and metrics in a standard way.
- middlewareioWIP module for instrumenting Deno programs with OpenTelemetry, transmitting traces and metrics in a standard way.
- mei_longREST Framework for Deno Standard Library Http
- mcresponseStandard return responses for system functional tasks
- mailermailer is a standard module for Deno applications to allow easy as cake email sending.
- jsonalizeA CLI tool that interprets stdin as a JavaScript literal and applies JSON stringify to it.
- jsonThe standard Deno module for accessing JSON easily.
- iter_funcsUtility functions for iterators. Inspired by Rust's `std::iter::Iterator` trait.
- hugoalh_command_line_parserA Deno module to parse command line with better standard.
- http_websocketHTTP request for websocket with standard Request and Response
- http_routerHTTP request router for standard Request and Response
- http_graphql_playgroundHTTP request for graphql-playground with standard Request and Response
- http_etagETag middleware for standard Request and Response
- http_corsCORS middleware for standard Request and Response
- http_content_minifyHTTP message content minification middleware for standard request and response
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.