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.
- simple_storageIs a module to create simple storages with structures in memory. It uses TypeScript to check types at compile-time.
- simple_slackbotNo description
- simple_shellDeno simple shell
- simple_shape_math2D math operations, data types, and storage
- simple_serverSimple web server for Deno
- simple_sandboxProvides a simple sandbox environment to execute javascript code.
- simple_routerNo description
- simple_promise_lockeasy to use, object-orientated, promise-based locks
- simple_openaiSimple API connection compatible with OpenAI and AzureOpenAI.
- simple_linear_regressionSimple Linear Regression using OLS estimation
- simple_json_set_getA simple persistent json storage framework.
- simple_ipcA simple and lightweight IPC module for Deno.
- simple_html_elementSimple HTML element implementation for text rendering
- simple_expectA simple `expect` util to test functions
- simple_execA dead simple wrapper around the Deno.Command API for better stdout piping, by @codemonument
- simple_event_emitterNo description
- simple_embedEmbed files in Deno executables
- simple_coveragecollect test coverage with Deno's built-in test runner and lcov
- simple_corsCORS - as simple and unsecure as it gets :) - you should only use this if you are not using any authentication / authorization mechanisms.
- simple_aes_cbcA simple wrapper for WebCrypto which uses the AES-CBC algorithm
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.