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.
- lume_theme_simple_meLume theme to create a link in bio page
- keydbSimple Key-value storage module with support for multiple database backends.
- jazziJuan's Algebraic Data Structures
- ip_locationa simple Deno 🦕 Module for fetching IP location details
- grpc_basicVery basic gRPC implementation for Deno
- form_data_to_objectConverts the FormData object into a complex object model.
- fluent_aws_codepipelineGenerate AWS CodePipeline YAML config from a simple declarative syntax in TypeScript 🛠️ 💻 ✨
- eventual_resultA `Result` and `Option` implementation that works with `Promise`
- durationjsParse, modify, and format time durations.
- deno_csv_stringA version of npm's csv-string package that works in the browser and in Deno
- debuglogDebugging utility for deno. Ported from https://npmjs.com/debug
- dayjs⏰ Day.js 2kB immutable date-time library alternative to Moment.js with the same modern API
- colorsColor conversion and stuff in TypeScript
- chalkin🦕 Simple colour for @denoland, inspired by @chalk 🦕
- cashify💸 Lightweight currency conversion library, successor of money.js
- cargo_assembleDependency management for your cargo application
- aws_s3_presignDeno module to create presigned URLs for AWS S3
- ansiANSI escape codes for manipulating the terminal
- abortableAbortable promises for Deno
- xmlparsernaive xml parser 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 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.