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.
- bimbaA lightweight middleware framework for Deno's native HTTP server.
- billboardjs📊 Re-usable, easy interface JavaScript chart library based on D3.js, with SVG and Canvas rendering support
- bijective_base_nConverts numbers to bijective base-n notation using the give alphabet
- bijective_baseTools for converting to and from bijective base numbers.
- bigintegerDeno first BigInt wrapper based on peterolson/BigInteger.js
- bigTurn a number, string or big integer into a big integer.
- bidbuild IME dictionary
- bic"Libreria" totalmente inutil para frontend
- bhttpA BHTTP (Binary Representation of HTTP Messages) Encoder and Decoder written in TypeScript.
- bgpviewLightweight BGPView API wrapper.
- bfsx_stdbfsa standard
- bfnNo description
- bfex_pluginsbfs kernel。distributed network|Application Portal
- bfex_cliffyCommand line framework for deno 🦕 Including Commandline-Interfaces, Prompts, CLI-Table, Arguments Parser and more...
- bf_rconBattlefield remote console implementation in Deno
- beyondjsNo description
- betterwebsocketsA fork of deno-websocket to make sending and receiving JSON objects easier.
- bettermapAn extension of the Map class with more Array-like features.
- betterfetchMakes fetching data with HTTP Easier
- better_switch_denoA simple alternative to the switch statement for matching strings and returning values
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.