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.
- harmonyAn easy to use Discord API Library for Deno.
- resvg_wasmMinimal resvg WASM bindings for Deno
- ddu_vimDark deno-powered UI framework for neovim/Vim
- async🦕 Asynchronous primitive modules for Deno.
- lambdaA deno runtime for AWS Lambda. Deploy deno via docker, SAM, serverless, or bundle it yourself.
- transformThis package provides wrappers for Deno.Reader that transform the bytes passing through as well as multiple built-in transformers.
- semaphorehttps://deno.land/x/semaphore@v1.1.1
- denodbMySQL, SQLite, MariaDB, PostgreSQL and MongoDB ORM for Deno
- gamlaNo description
- snelmSnelm: improved security middleware for deno web frameworks, derived from helmet for Node.
- denosassDenoSass is a complete nearly fully featured Sass compiler for Deno and Browser
- loggerlogger for deno
- inspect_vscodeClick in your components and open VSCode in the correct file and line number.
- threejs_4_denoA simple transformation of three.js for use within a Deno workflow
- notion_sdkUnofficial Notion Deno Client, port of the official Node.JS Client
- s3Amazon S3 for Deno
- importmapResolve specifiers with import maps.
- csvStreaming API for reading and writing CSV for https://deno.land/
- ciGet environment variables exposed by CI services
- smtpSMTP implements for deno
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.
