-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Gatsby v4 #25
Comments
If it does work correctly for gatsby 4 out of the box, yes we can just update the peer dependency. Does it work correctly so far? |
I can get it to run, but after the build, pages have this error:
the error is in the gatsby core file loader.js. Not sure why yet, maybe something different with how v4 renders and caches pages? |
@chrisschaub did you find a solution to this? it's exactly where i'm at. |
I did not. I think it's the plugin lagging behind Gatsby versions. I'll try to have a look in a bit. |
any update on this guys ? .. since I have npm <7 I get warnings that ipfs plugin(i have ver 2.0.2) is not cool with gatsby 4.11.1.. soooo.. site comes up BUT.. some links seem to not work.. especially file downloads is the workaround to back off the gatsby version back to 2. ? or did the ipfs plugin get upgraded so its cool with 4.11.1 ? thanks in advance UPDATE.. trying new ipfs dependency as on gatsby site.. gatsby-plugin-runtime-path-prefix. for ipfs/ swarm. v 2.0.1 |
you were running npm 7+ ? see I just got warnings because I am running npm < v7. .. BUT.. I still get a site that doesnt have all file download links working.. site comes up ok and compiles ok with warnings.. but misbehaves |
everything boots fine for me, no errors, link works fine using brave ipfs browser, but i cant get it to work on any public gateway. Link either removes the hash from the endpoint, or the page never loads. Even with @Odin94 pr. you guys have same issue? |
Hey - thanks for creating this plugin!
I just created a new (v4) Gatsby site. When I try to install this plugin I receive this error:
Seems we'll need to upgrade this plugin to work with v4?
The text was updated successfully, but these errors were encountered: