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.
- cobrasmall library to create Deno cli tools
- virtualstorageAn _observable_ polyfill for local storage :sauropod:
- json5JSON5 for Deno
- catjazzCataclysm: Bright Nights JSON manipulation powertools
- terA tiny wiki-style site generator with Zettelkasten flavor.
- mockUtilities to help mock behavior, spy on function calls, stub methods, and fake time for tests.
- graphql_tag🦕 Create a GraphQL schema AST from template literal. Deno port of `graphql-tag` library
- view_engine🚀A Template View Engine for Deno frameworks
- codemirror_esmFork of https://github.com/codemirror/dev with ESM-compatible build
- google_datastoreA set of APIs that allow interfacing to Google Datastore on GCP from Deno.
- seq_queueSeq-queue is simple tool to keep requests to be executed in order.
- pathbetter path handling for Deno
- oak_corsForked from the nodejs package expressjs cors. Now it is just a simple and opinionated cors middleware for Deno oak.
- namedpipeAsynchronous Named Pipes support for Deno, built on WinAPI using FFI.
- generate_functionModule that helps you write generated functions in Deno
- typed_numericTyped numeric for Deno.
- sail_lru_cacheNo description
- renoA thin, testable routing library designed to sit on top of Deno's standard HTTP module
- kubernetes_apisREST focused Typescript classes for Kubernetes APIs, and tools for generating API interfaces
- grammy_menuInteractive menus for grammY.
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.