Enables Gatsby websites to be deployed on IPFS by converting asset paths to relative URLs.
gatsby-plugin-ipfs is a Gatsby plugin that enables static websites built with Gatsby to be deployed and served from the InterPlanetary File System (IPFS). It solves the problem of Gatsby's default absolute paths, which break when hosted on IPFS gateways, by converting them to relative paths. This allows developers to publish decentralized, censorship-resistant websites.
Gatsby developers who want to deploy their static sites on IPFS or other decentralized hosting platforms that require relative asset paths.
It provides a simple, configuration-light solution to a specific Gatsby limitation, enabling IPFS compatibility without requiring major changes to the build process or site structure.
Adds support for deploying Gatsby to IPFS by ensuring that assets are relative
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Requires minimal setup—just set pathPrefix in gatsby-config.js and add the plugin, as shown in the README, with no complex options.
Post-build processing transforms all path prefixes to relative URLs, fixing Gatsby's absolute path issue for IPFS gateways, per the README.
Injects a small script into HTML pages to detect and set the path prefix based on the visitor's gateway URL, enhancing compatibility across IPFS nodes.
Solves a key Gatsby limitation, allowing static sites to be deployed on decentralized IPFS networks without broken asset links, as stated in the description.
The README admits using 'smart and ugly hacks' for path conversion, which may break with future Gatsby updates or require maintenance.
Specifically designed for IPFS deployment; it adds no value for other hosting methods, making it a niche dependency.
The injected script for browser detection adds extra JavaScript to every page, potentially increasing load times for minimal sites.