getServerData Support about javascript HOT 3 CLOSED

Hello @graysonhicks 👋🏻

Great to hear that you liked the auth experience, even if this plugin is mainly focused on CSR until now :) Happy to say that updating this plugin to fully leverage the SSR capabilities of Clerk v3 that was released two weeks ago was on our roadmap already; the actual implementation would be starting next week.

I think you're correct; the final solution could look very similar to @clerk/nextjs, but I'd like to explore how we can handle the "interstitial" page. When we detect that a JWT is expired (among other edge cases), we use this interstitial page to refresh the JWT and then reload the page. In the @clerk/nextjs to ensure no user logic runs before we get a fresh JWT, the interstitial page is thrown by middleware (withServerSideAuth or withAuth in _middleware functions) before the application does any processing. (Please note that we have plans to replace this logic soon.)

It'd be great if you could give me a couple of days to run some tests internally and get back to you once I can share more details about the above.

We always aim to provide the best possible DX, so could you please share the kind of public API (HOC vs. callback, and possible naming) you think would feel more natural to a Gatsby user? I believe you are just the right person to ask :)

Gatsby is fantastic and we're more than happy to work on this plugin again

from javascript.

@nikosdouvlis Awesome to hear! I'm going to share this with the OSS team and will get you some feedback.

from javascript.

I think a minimal gatsby site using the Clerk plugin would be a good first step. Maybe this could be a good place to do that on a branch. That would make npm link easy to use for testing. @pieh

from javascript.