SPA and API synchronization сhallenges

[monolithed]

Hi there!

I've noticed that the API for this package and @workos-inc/node are somewhat inconsistent, even though they essentially implement the same functionality. A lot of the logic in the session file is already implemented in @workos-inc/node.

I don't know the reasons behind this, but it makes it harder to understand the architecture of WorkOS. The reason I decided to open this issue is that I got stuck trying to integrate Magic Auth. It seemed like a simple authentication method, but there are no examples in the documentation on how to set up a session, how to manage that session on the client side, or how to redirect the user to another route smoothly without reloading the page.
It's not hard for me to figure it out, but there aren't any ready-made templates, guides, or clean APIs to save time

In the end, we have 5 packages: @workos-inc/node, @workos-inc/authkit-nextjs, @workos-inc/authkit-react, @workos-inc/authkit-js, and a 3rd party next-auth with an adapter for SSO only — all with different APIs, code duplication, and no examples for custom authentication in a SPA.

I wanted to check if there are any plans to synchronize the APIs or add examples specifically for SPAs.