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.
- esbuild_plugin_sass_denoMade for the poor souls trying to use SASS/SCSS on Deno using ESBuild as bundler who did not know `esbuild-sass-plugin` was not compatible with Deno due to Dart-SASS being a pain.
- esbuild_plugin_sassA SASS Plugin Module for the Deno version of ESBuild.
- esbuild_plugin_resultPlugin for esbuild on Deno that shows build result
- esbuild_plugin_lit_sassA Lit Web Components Plugin Module for the Deno version of ESBuild.
- esbuild_plugin_http_importsNo description
- esbuild_plugin_http_fetchAn esbuild plugin that resolves http(s) modules
- esbuild_plugin_evalAn esbuild plugin that evaluates a module before importing it
- esbuild_plugin_envAn esbuild plugin that exports the current environment as a module
- esbuild_plugin_dts🔌 Build Typescript declarations with ESBuild
- esbuild_plugin_deno_resolvePlugin to resolve deno import maps and URLs
- esbuild_plugin_deno_remote_importesbuild plugin to fetch remote imports for Deno.
- esbuild_plugin_deno_httpAn esbuild plugin that uses Deno to resolve and cache HTTP modules
- esbuild_plugin_cssImport CSS files in your javascript, and have them bundled by esbuild. compatible with Web Browsers and Deno.
- esbuild_plugin_copyA plugin for esbuild on Deno that copies files
- esbuild_plugin_cache_denoesbuild plugin for Deno that resolves HTTP/HTTPS and npm imports using its cache system
- esbuild_plugin_cacheNo description
- esbuild_plugin_bundleAn esbuild plugin that bundles modules before importing them
- esbuild_plugin_brotliesbuild brotli plugin
- esbuild_plugin_bookmarkletAn esbuild plugin to generate bookmarklets!
- esbuild_npm_import_pluginESBuildでDeno-likeなnpm importを実現する
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.