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.
- dyarnDyarn is a runner helper for Deno, thus avoiding having to run giant commands with permissions all the time.
- domainGet all the top-level domains, including gTLDs such as `.com`, and country-code TLDs such as `.uk`.
- disgroupdevjsThe official library from DisGroup Development with all managers and data.
- disgroupdev_jsThe official library from DisGroup Development with all managers and data.
- deploysbQuickly deploy all the Supabase functions in your directory
- denotoolsThis is where i keep all the "useful" tools I make for Deno!
- denoconfigA collection of utilities to allow for development with deno in emacs!
- deno_test_server_and_client_sidevery basic wrapper functions to be ablel to run deno test also in the client
- deno_correiobrComplete module to consult information about the zip code, calculate the price and delivery times of orders and also perform their tracking
- ddc_unprintableDevelopment ddc.vim helpers that allow you to paste word-kind sources gathering unprintable characters.
- curry_cacheA deno library by @codemonument which allows currying of a function to cache it's result. Has an interface to allow providing your own store!
- cross_dirnameNode.js + Gjs + Deno module that returns the current script dirname. Similar to __dirname but also works in CommonJs and ES modules.
- cronyManage all your cron jobs in one file
- countlinesA CLI to count all lines in a directory
- chromaTypeScript library for all kinds of color manipulation.
- carpenterbuilder-like pattern for all things Deno
- carcajada_artificial_test_moduleThis repository is my personal test site for all things Deno, Fresh, and JSR. I don't aim for this to be seen by others, don't expect clarity.
- bzfqueryJavaScript/TypeScript version of bzfquery for Deno with no external dependencies. It can also be used as a library or from the command line.
- brazilianTools for developers in Brazil, also available for Deno
- bindCompose one bond to rule them all and in darkness bind them
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.