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.
- jsphereJavaScript Application Server
- jsonrpcA JsonRPC library for Deno - client and server
- jsdocserverA Geminispace server for serving JSDoc documentation.
- jossJOSS can serialize almost every JavaScript data type and data structure, so data can be seamlessly exchanged between browsers and servers (Deno or Node.js).
- ion⚛ A comprehensive framework for server-side applications. Being built on top of TypeScript, it surprisingly supports native Web APIs. It can also be used for REST/GraphQL and many others.
- inspirusTiny web server for Deno with routing included.
- inertia_oak_middleware@inertiajs inertia server-side adapter for the @denoland Deno web-framework @oakserver oak
- hyperserveFunctional HTTP server library for Deno, backed by Hyperactive
- hyper_httpEnhanced and lightweight Deno HTTP web server.
- httpservTiny and fast http server for Deno
- http_fnsA bunch of functions for building HTTP servers
- http4tsServer as a Function http toolkit for TypeScript & JavaScript
- htmx_headersEnvironment-agnostic server backend for HTMX
- hono_middleware_error_handlerCatch server error middleware for Hono.
- hiphopsUser runtime server and libraries for Hiphops
- guardenoqlSimple and customizable security middleware for GraphQL servers in Deno
- graphismQuickly create GraphQL servers in Deno & Deno Deploy
- funnyA simple functional web server for Deno
- fundispatchera top level server registry and discovery for dispatching request between servers (to implement micro-service architecture)
- ftlFTL is a fast WebRTC based server for Deno.
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.