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.
- stable_stringifyDeterministic JSON.stringify() for Deno
- cookiesNo description
- authenticusThe simplest all-in-one authentication library for JavaScript.
- postcss_autoprefixerNo description
- pkce_denoPKCE code verifier and challenge generator for Deno.
- named_placeholderscompiles "select foo where foo.id = :bar and foo.baz < :baz" into "select foo where foo.id = ? and foo.baz < ?" + ["bar", "baz"]
- is_propertyTests if a property of a JavaScript object can be accessed using the dot (.) notation or if it must be enclosed in brackets, (ie use x[" ... "])
- event📆 Strictly typed event emitter with asynciterator support
- lol_htmlThe Low Output Latency streaming HTML rewriter/parser with CSS-selector based API, in Webassembly.
- keygripA keygrip implementation in Deno
- dpp_vimDark powered plugin manager for Vim/neovim
- status🗿 HTTP status utility for Deno. Based on Java Apache HttpStatus
- slugifyA string slugifier
- jsonlinesWeb stream based jsonlines decoder/encoder
- fcgiFastCGI implementation for Deno. Allows to use Deno as web requests handler behind nginx or apache2.
- vipps_mobilepay_sdkSDK for integrating Vipps MobilePay APIs. Built with Deno
- v8_serde[WIP] Pure-JavaScript implementation of the V8 value serializer
- resinLightweight css-in-js library for Fresh
- ogoneAdvanced Web Composition for Future
- mustache_tsA Typescript Deno-first refactoring of Mustache.js
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 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?
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.