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.
- singlylinkedlistSingly linked list for deno
- singletonsingleton deno module
- single_filez_coreNo description
- single_file_coreNo description
- sincoBrowser Automation and Testing Tool for Deno, written in full TypeScript
- simsimiSimSimi API for Deno
- simplestatisticsimple statistics for node & browser javascript
- simplertesta super simple test runner (in-browser)
- simplelogA simple logging middleware for Oak
- simplehooksA simple hook component for creating and calling hooks
- simpledbSimple JSON "database" for Deno.
- simplecorsAs https://deno.land/x/cors seems pretty complete now I do no longer maintain simplecors.
- simplebleBluetooth LE bindings for Node, Deno and Bun using SimpleBLE.
- simple_youtube_chapter_extractorCopy the text containing chapter information directly from YouTube and convert it into simple mkvmerge chapter format to embed in your downloaded YouTube video.
- simple_websocket_apiNo description
- simple_web_locksA single threaded implementation of Web Locks API. Works across runtimes (Browser, Deno, Node).
- simple_utilitySimplify processing for Deno.
- simple_type_assertSimple type assertion library for Deno
- simple_twitter_denoSimple Twitter API client using the new Deno framework sending authorized requests to the Twitter API.
- simple_timer_streamA simle timer as a webstream by @codemonument
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.