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.
- uwu_template⚡ Blazingly fast template engine for Deno/JS - 6x faster than Handlebars, 1.5x faster than Pug. Features Handlebars-like syntax, block helpers with options, layouts, and compile-time optimization. Battle-tested performance.
- uwufyAn NPM/ Deno package which allows you to uwufy a given string.
- uwuifierThis repository contains the Uwuifier package! It's written in Deno with TypeScript and compiled into JavaScript for NPM, makes use of Jest for testing the code and is deployed on NPM and https://deno.land.
- vadeSimple class validator for Deno using TypeScript Decorators with built-in class transformer.
- valaFramework for DenoJS
- vale📝 Documentation Generator built with Deno
- validateValidate is a standard Deno module for validating string.
- validate_patouiValidate is a standard Deno module for validating string.
- validatorusA class-based validator for Deno.
- validifyValidate your Deno application's incoming data
- vatsim_wrapperVATSIM API wrapper in TypeScript (Deno)
- vcaA visitor count API written in TypeScript for Deno.
- vectorartqvectorartq is a deno cli vectorartai query tool
- velocsframeworkThin Typescript web framework on top of Deno HTTP Default Library
- verify_paddle_webhook🔑 Deno module for verifying signatures from Paddle webhooks.
- verseA lightweight tool for serving http built on top of the Deno standard library.
- versionA simple semantic versioning tool for Deno; a lightweight replacement for `npm version`
- version_bumpA pluggable version bumping software (akin to standard-version) written in Deno + TS
- version_infoGet version info of Deno module
- vertexHTTP microframework for Deno
Q&A
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?
Name squatting is not allowed on the deno.land/x/. If you feel that a module is not currently usable, has not been legitimately under development for more than 90 days, and you have a concrete proposal to publish a well-maintained module in its place, please contact support.