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.
- fmopsNo description
- fly_pipelineA ready-to-use CI/CD Pipeline for deploying your applications to fly.io
- fluxyA simple flux like store written for Deno Fresh to share state between islands using hooks.
- flux_standard_actionPort of flux-standard-action npm package for Deno.
- flux_annotated_csv_parserParser for Flux annotated CSV data https://v2.docs.influxdata.com/v2.0/reference/syntax/annotated-csv/
- fluxA powerful state library in TypeScript for Deno
- flutter_pipelineA ready-to-use CI/CD Pipeline for Flutter projects.
- fluffcordDiscord API Wrapper for deno
- fluentdockerGenerate dockerfiles from a simple declarative syntax in typescript and build them with ease 🐋 🚀 ✨
- flowtsRust Inspired Type-Safe Errors and Missing Values for JS & TypeScript.
- flowscripter_template_deno_libraryProject template for a Deno library.
- flowscripter_example_plugin_apiExample plugin API for the dynamic-plugin-framework.
- flowscripter_example_pluginExample plugin for the deno-dynamic-plugin-framework.
- flowscripter_example_host_applicationExample host application executable for the deno-dynamic-plugin-framework.
- flowscripter_example_cliSimple example CLI using https://github.com/flowscripter/dynamic-cli-framework
- flowscripter_dynamic_plugin_frameworkDynamic plugin framework for Bun based on Javascript Modules and import() function.
- flowscripter_dynamic_cli_frameworkA framework for developing CLI applications which support dynamic discovery and installation of new commands.
- flowedA fast and reliable flow engine for orchestration and more uses in Node.js, Deno and the browser
- flow_builder_js_helpersNo description
- floreadNo 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.