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.
- react_icons_tfideno fresh react-icons for tfi
- react_icons_tbdeno fresh react-icons for tb
- react_icons_sldeno fresh react-icons for sl
- react_icons_sideno fresh react-icons for si
- react_icons_rxdeno fresh react-icons for lu
- react_icons_rideno fresh react-icons for ri
- react_icons_io5deno fresh react-icons for io5
- react_icons_iodeno fresh react-icons for io
- react_icons_imdeno fresh react-icons for im
- react_icons_hi2deno fresh react-icons for hi2
- react_icons_hideno fresh react-icons for hi
- react_icons_grdeno fresh react-icons for gr
- react_icons_godeno fresh react-icons for go
- react_icons_gideno fresh react-icons for gi
- react_icons_fideno fresh react-icons for fi
- react_icons_fcdeno fresh react-icons for fc
- react_icons_dideno fresh react-icons for di
- react_icons_cideno fresh react-icons for ci
- react_icons_cgdeno fresh react-icons for cg
- react_icons_bideno fresh react-icons for bi
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.