Gatsby Head API and client-only routes

[aaronadamsCA]

I have a client-only route with param.id. This ID is used to fetch client-only data using Apollo Client.

Now I want to implement the Gatsby Head API; but the head function executes outside the root element, so my graph provider (and hence my Apollo Client) are unavailable.

How might I safely work around this gap? Initializing Apollo Client all over again is not a good solution, but I'm hoping there might be some other way.

[marvinjude]

Hi, @aaronadamsCA,

In the future WrapRootElement will make this possible out of the box so you can consume context from Head. Asides from reinitializing the Apollo Client, I can't really think of a workaround for this.

Related comment

#35841 (comment)

[aaronadamsCA]

Thanks @marvinjude. I thought about grabbing an additional ApolloClient, but as soon as I realized this would also need to consume site config, I realized the size of the change would get rough pretty quickly.

Is this improvement imminent? I am not looking for a guarantee, but I need to weigh the impact of waiting for this vs. switching to react-helmet-async.

[marvinjude]

Is this improvement imminent?

We have this planned for v5. So it's soonish.

[JustFly1984]

@marvinjude I do not see any @5-Alpha versions in npm, nor any v5 branches in gatsby repository. Can we expect to get build fixed by this month?
Can you provide any workaround?

I need to deploy to QA asap.

[LekoArts]

We can't give any timelines on releases for v5 yet, you'll see the announcements on all relevant channels when v5 is ready to try and it includes the feature. Please use react-helmet-async so long then if you need this functionality.