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.
- ./lambdaA deno runtime for AWS Lambda. Deploy deno via docker, SAM, serverless, or bundle it yourself.
- xebecA lightweight, modern HTTP server for Deno with built-in routing, middleware support, and TypeScript integration.
- rex_ormA modern TypeScript ORM for Deno with PostgreSQL/SQLite support(more coming), real-time sync, GraphQL generation, and seamless serverless deployment. Built for type-safety and developer productivity.
- dhpDeno PHP - Meet the simplicity of PHP's server side rendering with modern JavaScript toolchain.
- semverThe semver parser for Deno (a fork of node-semver using TypeScript)
- v8_serde[WIP] Pure-JavaScript implementation of the V8 value serializer
- windows_serviceDeno library to seamlessly integrate your application as a Windows service without any external tools.
- zod_semverA simple deno module by @codemonument with a zod schema for validating semver. Uses official regex and is cross-posted to npm as zod-semver
- servirA Deno HTTP wrapper with flavour! https://deno.land/x/servir@v0.0.1
- serviceInstall a Deno application as a system service
- servaThe zero setup web framework for Deno.
- sereaCharts, diagrams and graphs for markdown
- semver_sortDeno module and cli tool for semantically sorting a set of version strings.
- semver_compare_cliCLI wrapper of the semver-compare library
- semver_cliA technology agnostic cli for common semantic versioning operations.
- rsa_serviceRSA Service for Deno
- nhttp_servicesNo description
- make_serviceNo description
- ethereum_attestation_service🦕 module utilizing the Ethereum Attestation Service
- ciGet environment variables exposed by CI services
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.