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.
- server_timingOak middleware to generate server-timing header with tracing functions
- server_denoserver-deno
- serve_with_supabaseNo description
- serve_spaNo description
- serve_modulesSimple HTTP handler to serve pre-cached Deno modules (including ts/tsx/jsx -> js)
- react_dev_servera simple dev server build with deno
- rcon_serverA Deno implementation for a lightweight RCON server
- oauth2_serverA standards compliant implementation of an OAuth 2.0 authorization server with PKCE support.
- oak_serverlessRun Oak applications with AWS Lambda and Amazon API Gateway.
- native_serverNative Deno HTTP client and server implementations
- komodo_serverSimple and lightweight middleware web framework for Deno
- json_serverZero code fake backend for development
- iterable_file_serverServe items from `AsyncIterable<File>`
- http_server🌐 Light-weight http server
- game_serveNo description
- functional_http_serverA simple HTTP server inspired by Express and in tune with Functional Programming principles in JavaScript for Deno.
- fox_serverNo description
- file_server_plus`deno` static file webserver, clone of `file_server.ts`, PLUS an additional final "404 handler" to run arbitrary JS/TS
- emit_esm_serverEmits ESM from TypeScript URLs via Deno.emit(...)
- earthstar_replica_serverAn always-online Earthstar peer for your shares.
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.