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.
- bwenoDeno client library for Bitwarden CLI's local REST API.
- busadBuild and serve your app with Deno - Busad
- burmesefontNo description
- buno⚙️ Cross-Platform JavaScript/TypeScript Runtime Adapter.
- bunnynet_stream_clientOpenAPI-generated client for bunny.net Stream API
- bunny🐇 A JavaScript SDK for bunny.net
- bunicorn_utilsFast and type safe Bun, Deno and Edge backend and client framework!
- bunicorn_serverFast and type safe Bun, Deno and Edge backend and client framework!
- bundyA drop-in replacement for `deno bundle`
- bundleeBundle static assets to a single JSON-file.
- bun_teaFast, Bun-powered, and Bun-only(for now) Web API framework with full Typescript support.
- bun_pipelineA ready-to-use CI/CD Pipeline and jobs for Bun projects.
- bunDear bun users...
- bump_workspacesA tool for releasing workspaces with Deno project
- bump_versionVersion bump tool for deno that matches npm version closesly
- bumpProject versioning tool for Deno
- bumblebeeCLI for migrating blog post images.
- buildsystemBuild System for C/C++ projects using Deno and TypeScript
- builderpgSQL builder for deno
- build_denobuild-deno is a Node.js package that helps you build your Deno source code from your Node source code. It can copy files, change import paths, and skip files during the build process.
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.