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.
- danielduel_ultra_stack_s3_lite_clientA lightweight but powerful S3 client for Deno
- danielduel_ultra_stack_pentagonPrisma-like ORM built on top of Deno KV. Allows you to write your database schemas and relations using Zod schemas, and run queries using familiar syntax from Prisma.
- danielduel_ultra_stackNo description
- danet_zodNo description
- danet_swaggerGenerate swagger/openapi spec for Danet projects
- danet_freshFresh module for Danet
- danet_databaseNo description
- danet_cliCLI tool for Danet applications
- dance🦕 Module for Dance Fans 💃🕺👯♀️. Providing Dance Events etc.
- damiAsterisk Manager Interface (AMI) Client for Deno
- damerau_levenshteinCalculate the Damerau–Levenshtein distance between strings.
- dallmo_yamldeno module for reading yaml file, based on deno standard library
- dallmo_util_yamla simple yaml file reader, based only on deno standard libraries
- dallmo_util_timestampdeno module, a collection of timestamp util under dallmo-util
- dallmo_util_timerdeno module, a collection of timer util under dallmo-util
- dallmo_util_stringdeno module, a collection of string util under dallmo-util
- dallmo_util_mathdeno module, a collection of math util under dallmo-util
- dallmo_util_arraydeno module, a collection of array util under dallmo-util
- dallmo_utila collection of utils in various categories
- dallmo_array_searcha simple function to search in array, return an array of strings
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.