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.
- youtube_srA dead-simple youtube metadata scraper
- supabase_edge_serveSupabase edge runtime helper function
- shellgptUpgrade your terminal with GPT-4. Ask questions, automate commands, pipe I/O, etc. Made with Deno.
- sail_sqlstringSimple SQL escape and format for MySQL
- readlineReadline implementation for Deno
- inkTerminal string color for Deno
- denoflowConfiguration as Code, use YAML to write automated workflows that run on Deno, with any Deno modules, Typescript/Javascript codes
- stream_observablesA collection of observables built with ReadableStreams & friends.
- netsaurPowerful Powerful Machine Learning library with GPU, CPU and WASM backends
- metapagesDeno scripts for managing build/test/deploy/publish commands
- deno2nodeCompile your Deno project to run on Node.js.
- dendron_exportsExport your Dendron vault into SSG compatible markdown
- object_cloneDeno module for deep object clone
- hammurabiNo description
- fresh_turnstileCloudflare Turnstile plugin for Deno Fresh
- deno_figletA Deno 🦕 Figlet from text generator
- denorestLightweight, Minimalist Framework For REST API 🦕 🚀
- deno_machine_idUnique machine (desktop) id (no admin privileges required)
- which_runtimeDeno module for checking which runtime the code is running in.
- vectorizerMachine Learning utilities for TypeScript
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.