-
Notifications
You must be signed in to change notification settings - Fork 4
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
Search for new Maintainer #20
Comments
Hi @danbruegge! We are using this package. Might be interested in maintaining it. Do you know what's needed to support Gatsby v. 3 and 4? Huge rewrites or just some small modifications? 🙂 |
Hi, sadly not. I've used Gatsby last with v2, but it should be small modifications. So in order to maintain I've checked what have to been done. You should fork this repo and also create a new package on npm. Because on npm this one is scoped to my username. If this is done, I will archive this repo and deprecate the npm package with a link to the new package. Sounds like a plan? |
@danbruegge sound like a plan indeed. It's more a question about time for us. Currently, this package actually works for our sites running both Gatsby 3 and 4, so I think the only thing one would need to do is to update the dependencies, but I'm not 100% sure... Since this package is still working for our sites, we have prioritized other things up until now. But let's keep in touch :) |
Hi, i no longer use Gatsby and have no time to maintain this package.
Someone wants to take over and maintain it? Otherwise, I will archive this repo.
The text was updated successfully, but these errors were encountered: