-
Notifications
You must be signed in to change notification settings - Fork 29
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
Install fails with [email protected] #31
Comments
I'm not actually sure! Having a quick look at the migration docs there's nothing that strikes me likely to be a breaking change for this plugin, so I suspect I just need to wrangle the peer deps to resolve the installation issue. In the meantime, the bit of that document about updating community plugins suggests you may be able to pass the |
I can confirm it works with Gatsby 3.14.2 |
Yeah, so it works with Gatsby 5 too, but we've got some cache invalidation issues as outlined in #46. I'm going to work on fixing those, and then we'll cut a release and push to npm. |
Can you try one of the new beta versions and report back? |
@darthsteven I had no problem installing v. 2.0.0-beta.0 with Gatsby v. 5.11.0 |
Seems like that beta has been working for a while - any chance of a stable tag in the near future? |
Is this package compatible with Gatsby V3? I searched around but couldn't find anything. I'm super new to gatsby, node, and all of this.
Upon running:
npm install --save gatsby-source-git
I get:
The text was updated successfully, but these errors were encountered: