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.
- messagepack_rpc🦕 Deno module that allows for the implementation of MessagePack-RPC using MessagePack as the message schema.
- alephThe Full-stack Framework in Deno.
- endofunctor🌐 Vixeny: At the forefront of modern web development, Vixeny stands as a runtime-independent, efficiency-driven library dedicated to upholding the principles of functional purity. It's crafted to empower developers with a robust foundation for creating scalable, maintainable, and high-performance web applications.
- caller_metadataNo description
- os_pathsDetermine common OS/platform paths (home, temp, ...)
- opineHttpProxyProxy middleware for Deno Opine HTTP servers.
- docxmlTypeScript (component) library for building and parsing a DOCX file
- whichFinds the path to the specified command in Deno.
- getportGet an available TCP port
- neo4j_driver_liteNeo4j Bolt driver for JavaScript
- streamtools🦕 This is a TypeScript module that provides utilities for handling Streams API.
- eventsEventEmitter for deno
- bureauBureau Double CMS
- validatteA Savory Class validator for Deno
- fathym_commonThe Fathym Reference Architecture provides the common foundation for applications built in Typescript.
- nunjucksA powerful templating engine with inheritance, asynchronous control, and more (Jinja 2 inspired) — ❌ Deprecated: use the `npm:` specifier instead
- gfmServer-side GitHub Flavored Markdown rendering for Deno
- basejumpTeams, personal accounts, permissions and billing for your Supabase app
- siftSift is a routing and utility library for Deno Deploy.
- nhttpAn Simple web-framework for Deno and Friends.
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 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?
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.