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.
- wecuA library for building composable, reactive web components.
- wechatNo description
- webusbWebUSB API implementation in Rust (and Deno)
- webtransportWebtransport FFI bindings for deno
- websocketserverSimple WebSocketServer implemented in Deno
- websocket_serverA WebSocket server library for Deno 🔌
- websocket_broadcastchannelHost-wide BroadcastChannel for Deno CLI, backed by WebSockets.
- websocket_bridgeNo description
- websiWeb Server Interface: Universal TypeScript HTTP abstraction for the Web Platform
- webshareNo description
- websersocketThis is a lightweight, easy-to-use module for Deno that streamlines the creation and management of web, file, and WebSocket servers. Leveraging Deno's built-in serve function, this module simplifies the process of setting up servers, making it accessible even to beginners, while providing enough flexibility for more advanced users.
- webscraperClass Library for Scraper on Deno
- webscrapeA deno library of tools useful to writing scripts scraping websites by @codemonument
- webrpcPerfect RPC Module for both Deno and Browser. 一个为双向调用而创造的RPC模块
- webpodNo description
- webos_client📺 TypeScript module for control WebOS-based LG TVs
- webnoNo description
- webnativeAn SDK for building apps with decentralized identity and storage.
- webmentionA webmention library for deno.
- webhooks_managerA webhook manager for Deno with guaranteed delivery and retry policy. You can even restart the server, it is persistent.
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.