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.
- afrAlways FResh: Deno library for serving files, with optional client integration for CSS injection and page reload. Simpler, better alternative to tools like Browsersync and Livereload
- affiliateAdd affiliation tags to links automatically in the browser
- aexprA safe javascript expression interpreter, support operators / context accessing / property accessing / lodash functions.
- aetherA Deno library to interface with the Discord API
- aes_gcm_crypto_streamA streaming AES-GCM encryption and decryption library that uses Web API, has zero dependencies, and offers high customizability. The library is theoretically compatible with browsers, Deno, and Node (not yet tested).
- aes_gcmModern Web Browser and Deno compatible AES-GCM library written in TypeScript
- aes_cbc_crypto_streamNo description
- aeonyx_mdNo description
- adventure_timeAdventure Time! Transcript - Deno ready library
- adventjsAdventjs Console Edition
- advent_of_codeA CLI tool built with Deno to help solve Advent of Code puzzles.
- adoublefPrelude
- adong主要是一些通用工具库
- adllang_tsdenoA deno typescript wrapper of the adl command line compiler
- adllang_localsetupDeno code to support installing locally scoped development tools
- adllang_genvisitorFor a given decl generates visitor interfaces and base visitor implementation.
- adllang_genmermaidNo description
- adlad_plugin_wgplaygroundAdLad plugin for the WGPlayGround sdk.
- adlad_plugin_wgplayerAdLad plugin for the WGPlayer sdk.
- adlad_plugin_pokiAdLad plugin for the Poki sdk.
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.