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.
- postcss_jsInterconversion between JavaScript Object(CSS-in-JS) and PostCSS AST
- postcss_font_format_keywordsSpecify font formats as keywords in CSS — ❌ Deprecated: use `@csstools/postcss-font-format-keywords` instead
- postcss_convert_unitspostcss util to convert custom units to standard units
- postcss_combine_duplicated_selectorsautomatically keep css selectors unique. — 🦕 Deno port
- postcss_color_imageUse a solid color as an image in CSS — ❌ Deprecated: use the `npm:` specifier instead
- postal_codePostal Code API
- postThe Post-Front-End Framework with React.
- portscannerPort Scanner with Javascript (NodeJs)
- portraitAn Open Graph image generator for images that you can embed in your meta tags. Written in Deno.
- portaudioA low-level cross-platform FFI module for playing and recording audio for Deno.
- portalRouting framework with the URLPattern interface for Deno
- portable_vscode_managerA CLI tool by @codemonument named "codeup" to manage Portable VSCode installations (currently for windows only)
- popupGUI for javascript standard popup's in deno.
- poolifierFast and small web worker pool
- poolGeneric pool for Deno
- ponderSimple ORM for PostGRES
- pomoDeno pomo(doro) module
- polyscale_httpHTTP Proxy Client Libraries
- polyline_decoderNo description
- polygonio_clientNo description
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.