Hey, quick question. How does the supertoken handling the parallel refreshToken rotatation? I mean, when the refresh token need to roatated. And there's 2 parallel request doing this. One of the will invalid (assuming the token is saved in browser cookie) does it have a grace period or something?

We use a locking mechanism which makes sure that only one refresh api is called at a time. This mechanism also locks across browser tabs

i see, how's the locking mechanism works? Is there any further resource I can read?

You can checkout our SDK browser-tabs-lock

awesome, thank you @rp_st