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.
- mongoose_history_tracePlugin mongoose for history logs schemas
- migraineSimple Postgres schema management
- microcms_sdk_generatormicrocms_sdk_generator is a Deno tool designed to automatically generate TypeScript SDKs from your microCMS API schema.
- jtd_codegen_cliA CLI tool that generates code from JSON Typedef schemas
- jsonschemageneratorConvert JSON examples into JSON schema (supports Swagger 2, OpenAPI 3 and 3.1)
- jemaJSON Schema handling / validator
- hypixelWith thorough IntelliSense support & 100% test coverage, this is an unopinionated async/await API wrapper for Hypixel's Public API. It is developed in TypeScript complete with documentation, typed interfaces for all API responses (and an OpenAPI 3.0 schema!), built-in rate-limit handling, flexible cache support, helper functions, and support for undocumented endpoints.
- graphql_model_generatorGenerate a GraphQL Schema and Document from a JSON model
- giraphqlPothos (formerly GiraphQL) is library for creating GraphQL schemas in typescript using a strongly typed code first approach
- geojsontoolsIs a project when you only go to find types and models from all diferents geoJSON schemas
- gen_graphqlGenerates GraphQL client types, based on the schema introspection
- fetch_graphqlA lightweight client for creating and sending GraphQL requests over Fetch API (without Schema/GQL Types validation)
- dozDeno-supporting branch of Zod, a TypeScript-first schema validation library with static type inference.
- 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.
- byte_codec_tsa schema based serializer for primitive javascript types with no external dependencies.
- breakdownDevelopment prompt&schema tool for automated AI development, using TypeScript and JSON.
- json_hashJCS (JSON Canonicalization Scheme), JSON digests, and JSON Merkle hashes
- validenoValidate your values and schemes with this extendable validator
- shamirs_secret_sharingPerformant secret sharing scheme implementation based on polynomial interpolation over finite fields
- datauriDeno module to generate Data URI schemes
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.