You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Is Gatsby discontinued? Please upvote for clarification. #38696
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.
Reacted by schwiet, Szymon, David Saitta, Taylor MacDonald, Lee Rowlands, Cory Reed, Jordan Prescott Sleeper, Aaron Byrom, SublimeBoundary, Bradley Shellnut and 147 more
Reacted by Nico Schett, Kuba, Daniel Lee, Tomas Fülöpp, Chaofeng Wang, Rijk van Zanten, Mišo Stevović, Florian Gyger, Pau, Andrew Fridley and 22 more
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.
Reacted by Kuba, SmartLabel, Kaspar manz, Tomas Fülöpp, Nico Schett, Paul McClean, Matt Kane, Chuck , Prakash, Geoff Schwartz and 137 more
Reacted by Kuba, Goto Hayato, Tomas Fülöpp, Erik, Denis Rusanov, Kirill Groshkov, Zach Levine, Santhosh, Robert Soriano, Leslie Owusu-Appiah and 2 more
Reacted by Szymon, Sean McLeod, Logan Roush, Daniel Lee, Kaspar manz, Tomas Fülöpp, Paul McClean, Prakash, Geoff Schwartz, John Gerrard Holland and 77 more
Reacted by Nico Schett, Cory Reed, Goto Hayato, Daniel Lee, Tomas Fülöpp, chemicalkosek, Erik, Paweł Gościcki, Christian Ragnarsson, Andre The Giant and 54 more
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.
Reacted by Elad Rosenheim, Dan Barak, Jonathan Cipriano, Matt Kane, tinder-kyleboss, Paul McClean, Joe Ben Taylor, Eduardo Bouças, Florian Kleber, Michał Tęczyński and 62 more
Reacted by Cade, Hakim Mazouz, Joel Birch, cordial, eheu, dMe, Arpan Patel , Kuba, Jonathan Rutheiser, Chris and 1 more
Reacted by Javanie Campbell, Marc Littlemore, Kuba, Youval Vaknin, Doma, Cameron Braid, Roger, Pratyay Banerjee, Adailton Ribeiro, Mansi and 2 more
Reacted by eheu, Joonas Lehtisyrjä, Kuba, Jonathan Rutheiser and Psychic Power
Reacted by Paul McClean, steven-netlify, Goto Hayato, Eduardo Bouças, Claire, Javanie Campbell, Marc Littlemore, Erik, 鲮鱼罐头, Peter and 15 more
Reacted by Nathanael Dewhurst, Andrew Fridley, Goto Hayato, Clay Giffin, Nicholas de Paola , Patricia Schneider, Atte Juvonen and Jonathan Rutheiser
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.
Reacted by Rajendra, Joel Birch, paolo-zattara-vulcano, Paul Abrams, Tim, Psychic Power and Alexander
Reacted by John Gerrard Holland, Tomas Fülöpp, Nico Schett, 鲮鱼罐头, Kuba, Hillary, Arman Nisch, eheu, Rob, Cameron Braid and 15 more
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?
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?
Reacted by Goto Hayato, Rajendra, Bruce Denham, cordial, Derek Foster, Mišo Stevović, Apolo Pena, Atte Juvonen, Jonathan Rutheiser, Alexander and 1 more
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.
Reacted by Goto Hayato, Maximilian Berkmann, paolo-zattara-vulcano and Alexander
@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.
Reacted by Nico Schett, Eiko Wagenknecht, Kirill Groshkov, Mišo Stevović, Junyoung/"Clare" Jang, georgesunnytHDS, Atte Juvonen and Alexander
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.
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.
Reacted by Nico Schett, Florian Gyger, Maximilian Berkmann, Daniel Mouritsen, Joonas Lehtisyrjä, eheu, Mišo Stevović, nick hulea, Jonathan Rutheiser and Alexander
Hi @biilmann , do you have an update on the Gatsby roadmap?
Reacted by Miguel, Monknow, David Sanderson, jbambauer, Cade, Joonas Lehtisyrjä, Marco Biedermann, Robin Bühler, TX-admin20, Mohamed Aymen Hammemi and 10 more
Reacted by Goto Hayato, David Sanderson, Joshua Ellis, Alex Gabites, Derek Foster, Clay Giffin, Mišo Stevović, nick hulea, Jonathan Rutheiser and Alexander
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.
Reacted by Goto Hayato, Auu, Julien, Joonas Lehtisyrjä, David Saitta, Nathan Tlaseca, eheu, cordial, Matthew Rumery, Marco Biedermann and 9 more
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.
Reacted by Goto Hayato, Laurenz Sommerlad, Auu, Matthew Rumery, Edward, Joonas Lehtisyrjä, Aidan Marshall, Jerome Dahdah, Alexander Malitsky, nick hulea and 9 more
Reacted by Kirill Groshkov, Lennart, Laurenz Sommerlad, Taylor MacDonald, 鲮鱼罐头, Denis Rusanov, nick hulea, Andrew Fridley, Owais and Eliaz Bobadilla
Reacted by Tomas Fülöpp, Zach Levine, Mišo Stevović, Laurenz Sommerlad, kengimai, nick hulea and Owais
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! 💪💜
Reacted by ゆうやみ(yu-yami), Leonhardt Koepsell, igarren, Eliaz Bobadilla, Chris and Jordan Refaeli
I'm going to reply to this stupid bot every time because fuck netlify and their hostile takeover and lies.
Reacted by Tomas Fülöpp, ゆうやみ(yu-yami), Mišo Stevović, Julien, Tamim Arafat, Leonhardt Koepsell, Boris Burkov, Jerome Dahdah, Psychic Power, Kai and 1 more
Reacted by Kirill Groshkov, ゆうやみ(yu-yami), Clay Giffin, Julien, georgesunnytHDS, Leonhardt Koepsell, Tom Radford, Psychic Power and Andrea Nicolai
Activity
Nasirahamad88 commentedon Nov 13, 2023
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.
schwiet commentedon Nov 13, 2023
thanks ChatGPT... err @Nasirahamad88
Vacilando commentedon Nov 17, 2023
The silence about this question is deafening.
biilmann commentedon Nov 17, 2023
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:
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.
DuneArchitect commentedon Nov 20, 2023
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 neededtag is getting overwhelming.wutangpaul commentedon Dec 5, 2023
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?
shibco commentedon Dec 7, 2023
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?
njbmartin commentedon Dec 11, 2023
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.
Berkmann18 commentedon Dec 17, 2023
@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.
laurogripa commentedon Dec 27, 2023
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.
cordial commentedon Dec 27, 2023
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.
ricky-harrys commentedon Feb 21, 2024
Hi @biilmann , do you have an update on the Gatsby roadmap?
robclancy commentedon Mar 26, 2024
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.
claygiffin commentedon Apr 22, 2024
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.
34 remaining items
schettn commentedon Apr 1, 2025
9e78ce8
@LekoArts works at @clerk by day, side projects by night xD
nyrzeff commentedon Apr 4, 2025
Honestly, part of the documentation is quite outdated.
emileond commentedon Apr 30, 2025
F
github-actions commentedon May 21, 2025
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! 💪💜
igarren commentedon May 21, 2025
What update? 🤔
robclancy commentedon May 23, 2025
I'm going to reply to this stupid bot every time because fuck netlify and their hostile takeover and lies.
mateicanavra commentedon May 31, 2025
This poor bot.
JulienDefrance commentedon Jul 15, 2025
Where are we regarding the support of React 19?
claygiffin commentedon Jul 16, 2025
@JulienDefrance Bless your heart.
blopa commentedon Jul 16, 2025
u83ism commentedon Sep 6, 2025
Apparently he's not dead. 🧟
#39180 (comment)
Christopher96u commentedon Mar 6, 2026
So... are we pretending this framework is not dead? I will never forget you Kyle