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.
- deno_cli_helpPrint help CLI-option in specific format
- deno_check_updates:mag: Automatically checks deno dependencies versions from import maps file
- deno_check_thai_pidNo description
- deno_chatA basic framework for working with Open AI's Chat API and storing context of previous conversation "turns".
- deno_changesetsA Deno native way to manage versioning and changelogs.
- deno_cefThe Chromium Embedded Framework for Deno.
- deno_cache_patchA TypeScript implementation of Deno CLI's module cache
- deno_bunyan_replacereplace for bunyan
- deno_bundlerA Bundler with the web in mind.
- deno_bundle💾 📦 ♻️ The 'just works' bundler, in memory of `deno bundle`
- deno_build_wasmBuild Rust functions for Deno.
- deno_bug_test111No description
- deno_bsonForked from npm package bson, now support for Deno
- deno_booksAPI client for OpenLibrary's API for searching books, authors etc.
- deno_blog_forkNo description
- deno_blogMinimal boilerplate blogging.
- deno_bindgenSimplified glue code generation for Deno FFI libraries written in Rust.
- deno_bincodeA deno binding of servo/bincode
- deno_bill_apiNo description
- deno_aws_s3_clientNo description
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.