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.
- decordecor is a Markdown transformer for single page, which uses a standalone HTML file as a template
- corfuTypesafe HTML templates using JSX 🚀🛡️🔥
- cat_on_oak(Deno) Template engine for Deno
- beakoWeb component tools with Data Binding, Template Engine and Virtual Dom for ESM.
- aftaft automates docker compose templates and enables compose packages.
- ./dejsejs template engine for deno.
- jmlJinja-flavoured html template strings
- honostackA fullstack template for building web apps with Deno, Hono, and JSX — styled with Tailwind CSS and powered by Docker for both development and production.
- nunjucksA powerful templating engine with inheritance, asynchronous control, and more (Jinja 2 inspired) — ❌ Deprecated: use the `npm:` specifier instead
- denjucksDeno templating engine
- macromaniaMacro-based string templating.
- workers_htmlHTML templating and streaming response library for Service Worker-like environments such as Cloudflare Workers.
- voks_web_elementshtml element tags implemented in the voks templating language
- twigJS implementation of the Twig Templating Language
- tmplxAn integrated templating engine and tool for your upcoming projects.
- poggiesA simple HTML templating engine
- contemplatingFreakishly small templating ~language~ script
- bq_denjucksDeno templating engine
- azpipeThe azpipe CLI tool for local templating of Azure Pipelines files
- upsertMaps for emplace, TC39 proposal-upsert implementation
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.