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
.
- natA server side rendering framework for Deno CLI and Deploy. 🦟 🦕
- nanotsdbTiny JSON based database in Typescript for Deno
- nanostoresA simple in-memory key-value store for Deno 🦕
- nanojsx_hooksExperimental hooks with nanojsx
- nanojs🦉NanoJs
- nanocolors2x times faster than chalk and use 5x less space in node_modules
- nanobusconfigNanoBus is a lightweight framework for building secure and scalable software services.
- nanobus_templatesFunctional, reactive WebAssembly with a twist
- nanobus_configNanoBus is a lightweight microservice runtime that reduces developer responsibility so that teams can focus on core application logic.
- nanoOld-fashioned (eval-free) template engine for Deno Deploy
- nametagNo description
- namemcA NameMC API/scraper for Deno
- nameableCross-check whether it can be used as a package name or domain name
- name_parserDeno module for parsing human names
- nadderan opinionated web server framework for Deno
- nabularDeno Script Manager
- naberiusWebAssembly bits processing utilities 🏎️ (unpack, pack, xor)
- myneA CLI tool for migrating Nostr events.
- myanmatimberCalculation of Myanmar Timber Tons
- my_mongoNo description
Q&A
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 on deno doc and 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?
Name squatting is not allowed on the deno.land/x/. If you feel that a module is not currently usable, has not been legitimately under development for more than 90 days, and you have a concrete proposal to publish a well-maintained module in its place, please contact support.