RFC: Deprecate @faustwp/experimental-app-router

[moonmeister]

Idea

The deprecation of the @faustwp/experimental-app-router package.

Reasoning

While Next's App Router is rightfully growing in popularity, Faust's reliance on Apollo means this package is never likely to lose its beta tag. For context, Apollo has stated that to fully support the Next.js App Router, upstream APIs would need to be added. APIs that are unlikely to be added.

This, combined with active work towards a more modular "Faust" that doesn't necessarily rely on Apollo, means this particular package should be deprecated in favor of any future solution but not be presented to new users as a "coming soon" solution.

Steps

• Final release with any pending PRs (Version Packages #1999) and other dependency updates
• Archive Relevant Docs from the site into this repository. docs: App Router Docs from website #2026
  • https://faustjs.org/tutorial/getting-started-with-the-experimental-app-router
  • https://faustjs.org/reference/getclient
  • https://faustjs.org/reference/getauthclient
  • https://faustjs.org/reference/faustroutehandler
  • https://faustjs.org/reference/onlogout-server-action
  • https://faustjs.org/reference/onlogin-server-action
• Archive docs and code on their own branch -
• Remove package from working canary branch - chore: remove app router from canary branch #2032
• Publish a Blog post announcing the deprecation and relevant information - New blog post, who dis? Learn all about

https://faustjs.org/a-retrospective-on-4-years-of-faust-js

• Deprecate the package with links to relevant docs in case anyone still using the package wants to reference them
• Close out any related issues or PRs as "Won't Fix"

Please let us know if you have any concerns about this proposal.

[CesarBenavides777]

Permission to fork and remake without apollo? @moonmeister

[moonmeister]

@CesarBenavides777 The team is in the early phases of reworking most of Faust. This action is a step towards reducing the maintenance of "experimental" features so we can focus on the new things we'll be building. I can promise you App router support will be part of this new future. We also intend to be neutral to the GraphQL client. Meaning, Apollo will not be required or default.

Our other goal moving forward is to make our work much more public and actively engage with the community in building and inviting them into the process. So, you're welcome to fork this, especially if you want to tweak/update it for something you're currently building. But you're also welcome to join with us in building something new.