Skip to content

feat(core): support Apollo Client 4 - #2694

Open
josephfusco wants to merge 13 commits into
canaryfrom
feat/2192-apollo-client-4
Open

josephfusco wants to merge 13 commits into
canaryfrom
feat/2192-apollo-client-4

Conversation

@josephfusco

@josephfusco josephfusco commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

Fixes #2192

A new CI job runs the core and blocks builds and tests with Apollo Client 4, and I ran the getting-started example on 4.3.5 against the example WordPress site in a browser: pages render, client-side navigation works, and GraphQL requests have no extensions param, though on Next.js 16's default Turbopack build that also needs #2696, without which pages rendered on demand return 500 on Apollo Client 3 too.

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Assisting with finding what breaks on Apollo Client 4, making the code and types work with 3 and 4, and testing both.

@josephfusco josephfusco added [Type] Feature A new feature within an existing module [Area] Compatibility WordPress, Next.js, Node.js, and third-party compatibility [Area] Core Issues for the @faustwp/core package [Area] Blocks Issues for the @faustwp/blocks package labels Oct 22, 2026
@josephfusco
josephfusco marked this pull request as ready for review October 23, 2026 15:09
@josephfusco
josephfusco requested review from a team and colinmurphy as code owners October 23, 2026 15:09

This branch has not been deployed

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

Labels

[Area] Blocks Issues for the @faustwp/blocks package [Area] Compatibility WordPress, Next.js, Node.js, and third-party compatibility [Area] Core Issues for the @faustwp/core package [Type] Feature A new feature within an existing module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Apollo Client 4 SPIKE

1 participant