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.
- offgrid_handlebarsHandlebars template Engine for Offgrid Service Worker
- offgrid_diebartdie_bart Template Engine for Offgrid
- odds_converterDeno project to convert betting odds
- octorgThe best way to organize the repos with Octocat help
- octono🍂 GitHub REST API for Deno projects
- octoherdcliCLI leveraging Deno to run an octoherd script on one or multiple repositories. Supports Typescript natively.
- octavia_deno🎻 Event-driven multi-standard MIDI tool chain. State tracking, parsing, serializing.
- ocr_by_pythonocr by ddddocr.
- obsidianlangThe easy one.
- obsidian2astroA small repo to organise my scripts related to publishing to my blog, abitbetterthanyesterday
- observe_sdk_datadogContinuous runtime observablity SDKs to monitor WebAssembly code.
- obplOBPL is the CLI runtime for Obsidian, bundled with Obsidian!
- objfmtFormat JavaScript objects with control of keys order and indentation style
- objexData handling module for EvolveJS!
- objectpathNo description
- objectid64The fastest way to convert UUID, MongoDB ObjectID, and serial ids into shorter, URL-friendly base64 and vice versa.
- object_validatorSuper lean and simple object validation with TypeScript support.
- obj🌊 A simple wavefront obj and mtl parser and loader module for deno
- obiObi is a programming language inspired by koka and lua.
- oauthsignatureOAuth1.0 base string generation
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.