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.
- multiparsermultipart/form-data parser for Deno servers
- is_whatJS type check (TypeScript supported) functions like `isPlainObject() isArray()` etc. A simple & small integration.
- checksumSha1、MD5 algorithms for Deno
- slack_edgeSlack app development framework for edge functions with streamlined TypeScript support
- msgpack_rpc🦕 Deno module to support msgpack-rpc
- og_edgeGenerate Open Graph images with Deno and Netlify Edge Functions, no framework needed.
- deno_docDocumentation generator for Deno
- reflect_metadataA Deno-compatible copy of the TypeScript Metadata Reflection API my Microsoft
- mimetypesDeno Mime types module
- slack_web_apiSlack Developer Kit for Node.js
- deno_slack_hooksHelper library implementing the contract between the Slack CLI and Slack application SDKs
- deep_eqlImproved deep equality testing for Node.js and the browser.
- json_hashJCS (JSON Canonicalization Scheme), JSON digests, and JSON Merkle hashes
- kv_toolboxUtilities for working with Deno KV 🦕🗝️
- htmlrewriterNo description
- hmachash-based message authentication code
- yargs_parser💪 the mighty option parser used by yargs
- html_parserPort of fb55/htmlparser2 for Deno
- zipStreaming cross-platform zip tool written for Deno 🦕.
- vixalien_deno_blogModified version of deno_blog just for me!
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.