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.
- githubGithub API wrapper for Deno
- githooked[Tool/Deno] Manage git-hooks across your team with cross-platform support and mobility. Comfortably integrates with git to allow custom scripting.
- gitfingerNo description
- git_timeclockA timeclock solution for freelance developers to track billable hours.
- git_modified_fileshttps://deno.land/x/git_modified_files
- git_hub_file_requestsRest-Api-Calls for Uploading and Getting File Values from GitHub files via Deno
- git_gogglesWIP Web UI to browse a git repo.
- git_deployA cli tool by @codemonument, upgraded from and cross posted to npm's push-to-git
- git_bumpA tool that automatically bumps your project's version and generates a changelog from your commits. Based on SemVer and Conventional Commits.
- git_browse🦕 Deno library and CLI to browse hosting service webpages of the repository
- gitlibgit2 bindings for Deno
- gistcafegist.cafe utils for Deno
- girlfriendNo description
- giraphqlPothos (formerly GiraphQL) is library for creating GraphQL schemas in typescript using a strongly typed code first approach
- giniA small and quick INI parser(and stringifier) for Deno
- gingerWeb Scraping library for Deno
- gimme_nekoI just want a neko using nekos.best api~
- gimkitNo description
- gifNo description
- gidw_event_emitterJavaScript EventEmitter
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.