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.
- upstash_redisHTTP based Redis Client for Serverless and Edge Functions
- socket_ioSocket.IO server for Deno
- lambdaA deno runtime for AWS Lambda. Deploy deno via docker, SAM, serverless, or bundle it yourself.
- multiparsermultipart/form-data parser for Deno servers
- superdenoSuper-agent driven library for testing Deno HTTP servers.
- xserverX-Server a Deno server module with middleware
- kubernetes_clientTypescript library for accessing a Kubernetes API server
- fasterA fast and optimized middleware server with an absurdly small amount of code (300 lines) built on top of native HTTP APIs with no dependencies. It also has a collection of useful middlewares: log file, serve static, CORS, session, rate limit, token, body parsers, redirect, proxy and handle upload. For Deno Deploy and other enviroments!
- danetThe most mature backend framework for Deno. Create awesome HTTP and WebSocket server as well as KVQueue workers !
- opineHttpProxyProxy middleware for Deno Opine HTTP servers.
- gfmServer-side GitHub Flavored Markdown rendering for Deno
- oak_http_proxyProxy middleware for Deno Oak HTTP servers. 🐿 🦕
- static_filesServe Static for Deno.
- realtimeAn isomorphic Javascript client for Supabase Realtime server.
- acornA focused RESTful server framework for Deno 🌰🦕
- megaloDeno HTTP server framework focused on speed
- fresh_chartsA server-side-rendered charting library for Fresh
- apilandThe API server for deno.land
- cargo_parcelServer side rendering for Cargo applications
- upstash_qstashMessage queue for serverless
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.