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.
- ttestModtest deno module
- ttappTTApp api gereversed engineered en opnieuw gemplementeerd in TS (deno)
- ttak0422_text_utilsNo description
- tszeugVarious stuff/zeug for typescript for deno, node and the web
- tsx_staticA minimal Deno library for tsx prerender/SSG
- tsworkersNo description
- tstlTypeScript-STL (Standard Template Library, migrated from C++)
- tspegPEG Parser Generator for TypeScript
- tspastePública y obtén datos de jspaste en Deno.
- tsoa_runtimeBuild OpenAPI-compliant REST APIs using TypeScript and Deno
- tsmservershellSmall Deno module for easy management and creation of HTTP servers
- tsluxonTypescript based Luxon: ⏱ A library for working with dates and times in TS and JS (immutable)
- tsignal_tsA topological order respecting signals library inspired by SolidJS. What's topological ordering you ask? Check out the readme to understand the problem with most signal libraries.
- tsfontsUtils to uses fonts weights with Typescript
- tservefile_server + deno_emit
- tsdsTypeScript Data Structures that you need!
- tsaTypescript source code analysis and documentation tool
- ts_serveTranspile TypeScript on the fly and deliver it from your server as ES Modules.
- ts_serializeA zero dependency library for serializing data
- ts_resultNo description
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.