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.
- parse_roblox_errorsNo description
- parse_modePlugin for hydrating ctx with familiar reply variants and for setting default parse_mode
- parse_envNo description
- parse_dont_validateA zero-dependencies package to verify the integrity of the data and return it in expected shape, otherwise throw error or return a specified value
- parse_decimalParseDecimal utility
- parse_aws_session_tokenNo description
- parry👷🏽♂️ Run deno functions in WebWorkers
- parlexaParlexa is an integrated Lexer and Parser
- parjsJavaScript parser-combinator library
- pargsPort of https://github.com/RazrFalcon/pico-args to Deno
- parea_aiTypeScript SDK for experimenting, testing, evaluating & monitoring LLM-powered applications - Parea AI (YC S23)
- paranoiaNo description
- paradiseSmart and smooth Dynamic Path Parser
- papyrus_prettyA prettifier for Papyrus
- papyrus_fileTransport for the Papyrus logger
- paperplaneLighter-than-air node.js server framework
- panoptesA simple array and object watcher function for Deno. Written in TypeScript.
- panic_fnFunctional way of throwing errors in JS/TS
- panicFunctional way of throwing errors in Deno
- pamplemoussehierarchical config for deno with support for layering and environment variables
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.
