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.
- html_entitiesFast html entities decode & encode library for Deno.
- semverThe semver parser for Deno (a fork of node-semver using TypeScript)
- crc32No description
- veloA high-performance caching library for Deno. Supports LRU, LFU, ARC, and TinyLFU.
- time.tsTime.ts - A straightforward Deno timezone manipulation
- charmdA simple, extendable markdown renderer for your terminal.
- ws_handlerWebSocket handler implementation and other utilities for working with status codes.
- notranspile_xmlcharsUtilities for determining if characters belong to character classes defined by the XML specs.
- lz4🗜 lz4 wasm module for deno
- gptDeno(TypeScript) BPE Encoder Decoder for GPT-2 / GPT-3
- denoA modern runtime for JavaScript and TypeScript.
- qrcode📇 Generate QR code images in Deno
- disposable🦕 Ensure a disposable resource is disposed in Deno
- graphql_tools[DEPRECATED] 🦕 Useful tools to create and manipulate GraphQL schemas. Deno port of `graphql-tools` library
- fathym_eac_runtimeNo description
- globberInclude and excludes files and directories from a deep search of the provided root directory
- deployCommand line tool for Deno Deploy
- downloadDeno fetch api based module to download file from a URL.
- axiomMinimal deno library for sending events and logs to Axiom
- updateKeep the dependencies of your Deno project up-to-date.
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.