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.
- cookie_sessionOpine cookie middleware similar to express cookie_session.
- cookie_driverA fast and correct cookiedb driver for esm platforms
- convoConvo SDK
- conveyorIt's easy to handle and multiplex nested asynchronous iterators.
- convertibleAutomatic conversion
- convert_sizea library to convert file size like MB, GB, ...etc
- convert_proa js library to convert between units that works on browser, node & deno
- convertThe smallest & fastest library for really easy, totally type-safe unit conversions in TypeScript & JavaScript.
- convCLI for currency conversion
- control_socketauto-reconnecting TCP Socket for control applications
- context_finderSearch a given file for specific sections/context data, collect this and write to a new file. For Node and Deno.
- context🦕【Deno】Propagate deadlines, a cancellation and other request-scoped values to multiple promise.
- contemplatingFreakishly small templating ~language~ script
- containerSuper slim DI(Depdency Injection) container.
- consulConsul is tool for service discovery, healthcheck , and key value store for your serivces. But deno is new , so Help us to build consul api for deno
- constructsDefine composable configuration models through code
- console_writeA simple additional function to write to the stdout of the current process with console.write() for Deno.
- console_logNo description
- console_colorsDeno Console Colors
- console_candlestick_chartJapanese candlesticks charts in the console for TypeScript/JavaScript projects.
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.