- Issue created by @tbadaczewski
niharika.s → changed the visibility of the branch 3501829- to hidden.
Are people actively maintaining this project? I don't mean maintainer open to PRs, but actually responding to issues?
This is a very important module for our web application, and not having it compatible with Drupal 11 is holding us back from upgrading.
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
@tbadaczewski hey I'm still here but I wear a lot of hats
My advice would be to look to move away from Gatsby in general - the health of the Drupal project isn't the issue - the health of the Javascript project is - e.g. see https://github.com/gatsbyjs/gatsby/issues/38696Drupal 10 is supported until mid/late 2026 so there's not as much urgency to get a D11 version out.
We have moved all our Drupal+Gatsby projects to something that isn't Gatsby so don't have any client projects where this update is pressing.
What this means is I'm happy to review MRs if things are ready but I'm unlikely to have time to dedicate to authoring them.
larowlan thanks for the strait talk info, I do appreciate it. We have been looking to shift from GatsbyJS to NextJS, but we were hoping to upgrade the Drupal 10 backend to Drupal 11 first. I'm hoping that this module already supports Drupal 11, but just needs a version bump in the info file. I'll do my own testing to see what problems arise. Once again, thanks for the response.
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
No worries, happy to merge stuff to unblock.