First of all, great package.
Secondly, I'd like to ask if this package allows us to call Clerk server-side.
From this section on Readme, first of all I believe locals in reality gives you the userId in session, not the entire Clerk user object, right?
Secondly, let's say I want to programatically create an organization for a user, after he signs up. Can I do it using this package? I noticed that you expose Clerk on the window object, which I can use on client Svelte components. What about server side? Is what I'm getting in locals the only thing I can get from Clerk? And no ability to make calls?
And if so, would I have to use their JS SDK?
Update: Looking deeper into the package code, it seems like on initializeClerkClient you're making clerk available only on the window object. So that means there's no way the package intends to allow use of clerk server side, right?
I was looking for the same scenario. Protected routes loado in server side only gives you locals.session.userId. How do I then trigger for example a callback to update user's last_log_date after sign-in?
First of all, great package. Secondly, I'd like to ask if this package allows us to call Clerk server-side.
From this section on Readme, first of all I believe
locals
in reality gives you theuserId
insession
, not the entireClerk user object
, right?Secondly, let's say I want to programatically create an organization for a user, after he signs up. Can I do it using this package? I noticed that you expose
Clerk
on thewindow
object, which I can use on client Svelte components. What about server side? Is what I'm getting inlocals
the only thing I can get from Clerk? And no ability to make calls?And if so, would I have to use their JS SDK?
Update: Looking deeper into the package code, it seems like on
initializeClerkClient
you're makingclerk
available only on thewindow
object. So that means there's no way the package intends to allow use ofclerk
server side, right?