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.
- eosio_eccA universal JavaScript ECC digital signature and key utility package for Antelope based blockchains
- enzastdlibenzastdlib is a set of TypeScript modules that follow a common design API philosophy aiming at sane defaults and ease-of-use targeting the Deno TypeScript runtime.
- enzEntryJS Project Parser & Transpiler to JS
- envyloads environment variables and .env file transparently
- envplusNo description
- envmodderA package (in beta) designed to make ReMapper environment statements more friendly
- envis10n_libA library of useful things for Deno projects.
- environment_decoderA decoder for environment variables.
- enviromodderMapLock is a module for remapper which is definitely not a nootils clone :)
- envioQuickly grab configuration from the environment!
- envhancedNo description
- envconfiggolang envconfig syntax for deno
- envconfNo description
- env_pathsGet paths for storing things like data, config, cache, etc with Deno.
- enummappingts enum object, 带typescript签名的多字段枚举关联对象映射
- enumEnum is a javascript module that introduces the Enum Type. It works for node.js, in the browser and for deno.
- entypeCLI tool and library which generates types for serialized data formats.
- entxReact framework for Deno, inspired by NextJS
- entsoe_api_clientENTSO-e transparency platform API Client built for Deno. Complete. Easy to use. Minimal.
- entry_live_variablesA Deno library to listen and change values of Entry real-time variables/lists.
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.