Skip to content

Is Gatsby discontinued? Please upvote for clarification. #38696

Open

Description

@schettn

Hi @pieh!

Could you please share your thoughts on this issue and provide insights into the current state of Gatsby? It seems like your are one of the few people still contribution / work of the pull requests.

Do not get me wrong but its actually a bit scary that a repository near to 55k stars feels that discontinued.

I know Gatsby was acquired due to its innovative Data Layer, but many people including me depend on the Gatsby framework as whole.

I would be happy to hear that there are plans for further framework development, although this seems unrealistic to me since Netlify fired nearly every contributor of this repository.

Originally posted by @schettn in #38483 (comment)

Activity

  1. added
    status: triage neededIssue or pull request that need to be triaged and assigned to a reviewer
    on Nov 11, 2023
  2. Nasirahamad88 commented on Nov 13, 2023

    @Nasirahamad88

    However, it's common for open-source projects to have fluctuations in activity and contributors over time. The concerns you've raised about the apparent decrease in contributions and the impact of changes in contributors are valid. Open-source projects can sometimes face challenges, including shifts in maintainer resources, changes in project priorities, or adjustments due to acquisitions.

    If you're concerned about the state of Gatsby, I recommend checking the official communication channels for the latest updates. This could include the project's GitHub repository, official blog posts, or community forums. Developers and maintainers often provide insights into the project's direction and address concerns raised by the community.

    If there are any recent developments or changes in the project's status, you're likely to find relevant information from official sources. If you have specific questions or issues, reaching out to the Gatsby community directly might provide more detailed and up-to-date information.

    Remember that the open-source landscape can be dynamic, and projects may evolve based on community contributions, maintainers' efforts, and overall project goals.

  3. schwiet commented on Nov 13, 2023

    @schwiet

    thanks ChatGPT... err @Nasirahamad88

  4. Vacilando commented on Nov 17, 2023

    @Vacilando
    Contributor

    The silence about this question is deafening.

  5. biilmann commented on Nov 17, 2023

    @biilmann

    Hey all,

    Gatsby is here to stay and we’re not sunsetting it. We’re committed to not only maintain it but also to building a forward-looking roadmap for it as we go into 2024, which I’ll share with you all as soon as we can.

    A large part of our enterprise customer base depends on Gatsby for their core properties, as it’s a battle-tested framework used for lots of large, real-world, high performing websites. We’re here to support that, as well as to work with the larger community around Gatsby.

    It is no secret that Gatsby is no longer the hip new framework on the block. Our core focus for it now is three-fold:

    • First, ensure stability, predictability and good performance.
    • Second, give it new powers by strong integration with all new tooling that we add to our Composable Web Platform (for more on what’s all that, you can check out our homepage).
    • Third, make Gatsby more open by decoupling some parts of it that were closely tied to proprietary cloud infrastructure. The already-released Adapters feature is part of that effort.

    Note: the above focus does mean that Gatsby isn’t going to be the first mover in new rendering paradigms. When it comes to features like React Server Components, Server Actions, etc., we would wait till the best practices have emerged and actual value is clear before making implementation plans.

    While we don’t plan for Gatsby to be where the main innovation in the framework ecosystem takes place, it will be a safe, robust and reliable choice to build production quality websites and e-commerce stores, and will gain new powers by ways of great complementary tools.

    Over the last few years, Gatsby’s static-first approach guaranteed high performance and uptime for customers, while allowing teams to build compelling front-end experiences.

    Our aim to make sure that this is still the case over the next few years.

  6. DuneArchitect commented on Nov 20, 2023

    @DuneArchitect

    That's great to hear. In the meantime, perhaps opening up to some of the community who wants to contribute would also be helpful. I wouldn't mind starting to put together some moderation for the Discord: which has become 100% spam, drowning out any real discussion or concerns.

    Furthermore there are people (including myself) opening up tickets and pull requests to improve Gatsby that are not getting any attention or feedback. The number of tickets with the triage needed tag is getting overwhelming.

  7. wutangpaul commented on Dec 5, 2023

    @wutangpaul

    it will be a safe, robust and reliable choice to build production quality websites and e-commerce stores, and will gain new powers by ways of great complementary tools

    Hi @biilmann,
    Thanks for the update. Our main source of anxiety is something like gatsby-source-shopify. Will plugins like this actively track and be updated to reflect API changes in Shopify itself, or would now be a good time to start looking at alternative ways of sourcing that data?

    Edit: would it be in Shopify's interest to maintain this plugin themselves, similar to how Sanity maintain theirs?

  8. shibco commented on Dec 7, 2023

    @shibco

    That's great to hear. In the meantime, perhaps opening up to some of the community who wants to contribute would also be helpful. I wouldn't mind starting to put together some moderation for the Discord: which has become 100% spam, drowning out any real discussion or concerns.

    Furthermore there are people (including myself) opening up tickets and pull requests to improve Gatsby that are not getting any attention or feedback. The number of tickets with the triage needed tag is getting overwhelming.

    This is what shocked me, too.

    The state of the Gatsby Discord is so bad it should be shut down. Dozens of inactive channels, whose last posts are crypto scams, predatory junior developer job hunting scams or other spam. If the Discord is full of content that goes against the Code of Conduct, why even continue running it at all?

  9. njbmartin commented on Dec 11, 2023

    @njbmartin
    Contributor

    It is no secret that Gatsby is no longer the hip new framework on the block.

    It's a real shame because I was an avid fan of Gatsby, but I imagine the main contributing factor of this is mainly the result of the acquisition of Gatsby for Valhalla, which led to downsizing of the entire core team and poor communication around the Gatsby open-source future.

    The other important factor, as others have pointed out, is that the open-source nature of the project is pretty dead if no one can contribute, and the only things being contributed seem to be Netlify specific. Plugin maintainers will give up and move on, leaving the eco-system dead in the water.

  10. Berkmann18 commented on Dec 17, 2023

    @Berkmann18

    @biilmann You mentioned stability, but a fresh install and setup with Gatsby has broken dependencies, some around Netlify CMS (which is worse given that Netlify owns Gatsby).

    It certainly doesn't inspire confidence in what seemed to be the go-to choice for SSG with React.

  11. laurogripa commented on Dec 27, 2023

    @laurogripa

    I'm glad to hear that Gatsby still kicking. Unfortunately I'm having a hard time right now with this issue, to the point that it gets very frustrating to develop. Coding with Gatsby used to be such a breeze :(

    Nevertheless, it's an awesome framework, it deserves some love, and I hope it overcome this challenging period.

  12. cordial commented on Dec 27, 2023

    @cordial

    I'm glad to hear that Gatsby still kicking. Unfortunately I'm having a hard time right now with this issue, to the point that it gets very frustrating to develop. Coding with Gatsby used to be such a breeze :(

    Nevertheless, it's an awesome framework, it deserves some love, and I hope it overcome this challenging period.

    im getting this also intermittently. And loads of other various / random / spurious issues (most of which you can see listed as issues but without any resolutions, or even comments in most cases). It seems no matter what Netlify are claiming above, Gatsby is not in a good place.

  13. ricky-harrys commented on Feb 21, 2024

    @ricky-harrys

    Hi @biilmann , do you have an update on the Gatsby roadmap?

  14. robclancy commented on Mar 26, 2024

    @robclancy

    Having to decide on what to use for our next project and even though I love gatsby it has seen a sharp decline in trust and activity since the netlify takeover. I don't believe a word that was said above about "new powers". Bunch of corporate bullshit.

  15. claygiffin commented on Apr 22, 2024

    @claygiffin

    Going into Q2 of 2024 with zero updates since Q4 last year, I think we can safely assume that Gatsby has been abandoned. It's really a shame, as I have been a huge fan and advocate for years now. But after such a long gap in updates, I can't in good conscience start another project on this framework.

    Goodbye Gatsby, and thank you to all the developers who dedicated their time to building something that was wonderful while it lasted.

  16. 34 remaining items

  17. schettn commented on Apr 1, 2025

    @schettn
    Author

    I wonder where the person who configured this bot works now.

    9e78ce8

    @LekoArts works at @clerk by day, side projects by night xD

  18. removed
    stale?Issue that may be closed soon due to the original author not responding any more.
    on Apr 2, 2025
  19. nyrzeff commented on Apr 4, 2025

    @nyrzeff

    Honestly, part of the documentation is quite outdated.

  20. emileond commented on Apr 30, 2025

    @emileond

    F

  21. github-actions commented on May 21, 2025

    @github-actions

    Hiya!

    This issue has gone quiet. Spooky quiet. 👻

    We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
    If we missed this issue or if you want to keep it open, please reply here.
    As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

    Thanks for being a part of the Gatsby community! 💪💜

  22. added
    stale?Issue that may be closed soon due to the original author not responding any more.
    on May 21, 2025
  23. igarren commented on May 21, 2025

    @igarren

    It’s been at least 20 days since the last update here.

    What update? 🤔

  24. removed
    stale?Issue that may be closed soon due to the original author not responding any more.
    on May 21, 2025
  25. robclancy commented on May 23, 2025

    @robclancy

    I'm going to reply to this stupid bot every time because fuck netlify and their hostile takeover and lies.

  26. mateicanavra commented on May 31, 2025

    @mateicanavra

    This poor bot.

  27. JulienDefrance commented on Jul 15, 2025

    @JulienDefrance

    Where are we regarding the support of React 19?

  28. claygiffin commented on Jul 16, 2025

    @claygiffin

    @JulienDefrance Bless your heart.

  29. blopa commented on Jul 16, 2025

    @blopa
    Image
  30. u83ism commented on Sep 6, 2025

    @u83ism

    Apparently he's not dead. 🧟
    #39180 (comment)

  31. Christopher96u commented on Mar 6, 2026

    @Christopher96u

    So... are we pretending this framework is not dead? I will never forget you Kyle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions