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.
- polysqlQueries generator for MySQL, PostgreSQL, SQLite and Microsoft SQL Server
- lesanNew way to create web server and NoSQL data model
- google_jwt_saGet Google Auth Token for OAuth 2.0 for Server to Server Applications/Google APIs
- littleA minimalistic connect-like web framework. Automatically works out of the box with Deno Deploy, Deno's Native HTTP and Deno's Standard HTTP server.
- oak_rate_limitRate-limiting middleware for Oak server on Deno
- fido2A node.js library for performing FIDO 2.0 / WebAuthn server functionality
- netA networking framework that aims to enable the development of complex multi-port servers and clients.
- fresh_validationEasy server-side and client-side validation for FormData, URLSearchParams and JSON data in your Fresh app 🍋
- mandarinetsMandarine.TS is a typescript, decorator-driven framework that allows you to create server-side applications. Mandarine.TS provides a range of built-in solutions such as Dependency Injection, Components, ORM and more. Under its umbrella, Mandarine.TS has 4 modules: Core, Data, Security and MVC, these modules will offer you the requirements to build a Mandarine-powered application.
- g_aUtilities for server side processing of Google Analytics in Deno CLI and Deploy
- ziplandServe file server with single zip file as file system in Deno.
- obsidianGraphQL, built for Deno - a native GraphQL caching client and server module
- googlejwtsaGet Google Auth Token for OAuth 2.0 for Server to Server Applications/Google APIs
- denoliverA simple, dependency free static file server for Deno with possibly the worst name ever.
- http🌐 Light-weight http server
- funqlNew way to create web server
- ua_parser_jsThe most comprehensive, compact, and up-to-date JavaScript library to detect user's browser, OS, CPU, and device type/model. Also detect bots, apps, and more. Runs seamlessly in the browser (client-side) or Node.js (server-side).
- superfetch🐕 HTTP Server testing library inspired by node-supertest-fetch.
- ssxFast and simple JSX library for server side only
- sshBindings to libssh2 for interacting with SSH servers and executing remote commands, forwarding local ports, etc.
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.