feat(faustwp-core): add typed GraphQL client (fetchGraphQL<T>) and FaustClient

[ArjunSaluja]

Adds a typed GraphQL client and helper to packages/faustwp-core.
.fetchGraphQL — a generic typed fetch wrapper for GraphQL. .FaustClient — lightweight client for queries and mutations. . Shared GraphQL response types (types.ts`).
. Includes a small Jest test for typed usage.

.Improves developer experience and ensures GraphQL responses are strongly typed.

Example

type Result = { post: { id: string; title: string } };
const client = new FaustClient(process.env.FAUST_GRAPHQL_URL!);
const { post } = await client.query<Result>(`query { post(id: "1") { id title } }`);

[headless-platform-by-wp-engine]

Currently, we do not support the creation of preview deployments based on changes coming from forked repositories.
Learn more about preview environments in our documentation.

[changeset-bot]

⚠️ No Changeset found

Latest commit: b4955a8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[theodesp]

Hi @ArjunSaluja
Thank you for your effort.
This appears to be a breaking change, as it removes the Apollo Client implementation in favor of a custom FaustClient and direct fetch-based GraphQL requests.

We do not aim to remove Apollo Client support from Faust at this time.

Can you share more about your use case? Is there something you’re trying to achieve that the current Apollo Client integration does not support?
We’d love to understand your requirements and see if there’s a way to address your needs without removing existing features.

Thanks!

[ArjunSaluja]

Hey, thanks for the feedback! My intention wasn’t to remove Apollo Client or introduce any breaking change. I was mainly trying to add a lightweight, type-safe helper ( fetchGraphQL<T> and FaustClient) as an *optional utility*, not as a replacement. The idea was to make it easier to: - Run quick GraphQL queries in scripts or tests without setting up Apollo - Provide a simpler example for people exploring Faust.js - Have a smaller, generic option for cases like CLI tools or build-time fetching Totally understand that Apollo is core to Faust — I can definitely adjust this PR so it keeps Apollo intact. Maybe this could live under something like utils/fetchGraphQL.ts or be marked experimental if that’s better. Let me know what you think — happy to update it to fit within the existing setup.

…

On Mon, 6 Oct 2025 at 3:03 PM, Theofanis Despoudis ***@***.***> wrote: *theodesp* left a comment (wpengine/faustjs#2188) <#2188 (comment)> Hi @ArjunSaluja <https://github.com/ArjunSaluja> Thank you for your effort. This appears to be a breaking change, as it removes the Apollo Client implementation in favor of a custom FaustClient and direct fetch-based GraphQL requests. We do not aim to remove Apollo Client support from Faust at this time. Can you share more about your use case? Is there something you’re trying to achieve that the current Apollo Client integration does not support? We’d love to understand your requirements and see if there’s a way to address your needs without removing existing features. Thanks! — Reply to this email directly, view it on GitHub <#2188 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4G3TAMIEN7FBZC3ZSMVFRD3WIZQJAVCNFSM6AAAAACIENEO32VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNZQG4YTINZZGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>