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.
- searchconfigNo description
- search_params_kitSet of functions for the URLSearchParams object.
- sdl_tsSDL TypeScript bindings.
- sdkcommercetools deno sdk
- sdenockerA Docker client library for Deno with extra commands
- sdenoSteno on Deno. Specialized fast async file writer.
- scuttlesaurusNo description
- sculptrCLI that builds project scaffolding
- scryptoAn async JavaScript Scrypt implementation using Web Cryptography APIs for PBKDF2.
- scrypt_basic_authBasic HTTP auth with scrypt verification for Deno
- scrollcatI want to catch the best scene of my life. The browser wants to, too.
- scriptzSqript is an npm package that helps code and execute scripts with Typescript. Its goal is to make development workflows descriptive, composable, and maintainable.
- scriptserverA minecraft server wrapper built in Node
- scriptsAutomated installation and execution of locally scoped scripts
- scriptorSimple and easy to use module for basic scripting, used as a replacement for basic bash scripts to improve the display output
- scriptkitTool belt with functionality for our internal Backoffice automations
- scriptingA collection of scripting utilities.
- scriptedNo description
- script_nopA framework for notification-oriented programming paradigm (NOP) implemented in TypeScript.
- scriptSmall framework for making scripts in Deno
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.