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.
- pgbA simple Deno module helps you to make progress bar in text
- pg_tsPostgreSQL introspection into TypeScript types
- pg_memAn in memory postgres DB instance for your unit tests
- pg_deltakitPostgreSQL Schema Management - Define, Diff & Sync
- pfpelixir-fying ts
- pfmtA strongly-typed Deno module for formatting strings and printing to the console.
- pexels_denoA simple Deno library for accessing Pexels api
- persistonSimple persistent store with database-like API.
- persistentPersistent object with proxy features. Every mutation synced to storage.
- persistenceWith this module you can use GitHub as a database. I guess this is only recommendable for small projects.
- permissions_policy_middlewareHTTP permissions policy middleware
- permissions_manager[Library/Deno] Permission Management for Deno Applications. Apply granular permission control to Deno applications.
- periskope_maytapi_denoNo description
- peridotSimple dependency injection library with module support
- percentencodePercent encode string following Twitter's spec from RFC 3986
- peraPera is a minimal web framework for Deno.
- 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.
- pekommunityCommunity-made external dependency/service modules for Peko
- pekoeNo description
- peershNo 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.