Long term use of Gatsby?

Contributors
1

Considering that Gatsby appears to be in maintenance mode with limited active development,* has there been any discussion among the freeCodeCamp maintainers about the long-term use of Gatsby by the freeCodeCamp client app?

I’m not bringing this up to hate on Gatsby, or suggest freeCodeCamp should immediately migrate the client application to Astro or Next.

I’m just wondering if the maintainers have any concerns about Gatsby going forward?

*See, for example, complaints in Is GatsbyJS Officially Dead? · gatsbyjs/gatsby · Discussion #39062 · GitHub

2

Hello there,

Yes, we often discuss the use of the tooling/packages in the main repository. A substantial amount of that time has focused on migrating the client.

This has little to do with the linked “Is GatsbyJS Officially Dead?” discussion, and more to do with being on version 3.

Our main blockers with immediately migrating (other than time) has been:

  • Higher priorities
  • Spending more time investigating the alternatives
    • Doing little experiments to evaluate the complexities of the migration
  • Performing adjacent migrations to help with the client migration
    • Removing dependencies where possible
    • Decoupling tooling and infrastructure between client, curriculum, and api

I suspect, once we nail down what we are moving to, we will have far more clear discussion about this on the issue tracker.

I hope this clarifies some.

3

Thank you very much for the detailed response.

Yeah, migrating a framework on a substantial project like freeCodeCamp isn’t to be done lightly.