Refresh token invalidation after refreshing an access token

// token has been invalidated
if (!user || user.count !== data.count) {
return next();
}

const tokens = createTokens(user);

Should we increment the count everytime before we refreshing new tokens?
Since refresh token lives longer and there would be many Live refresh tokens out there with the same count.

Since one year has passed, did you come up better solution for token invalidation? I'm coming from your YT channel and I love your content btw.

Start by locating the TypeScript entry points corresponding to the shown count comparison and createTokens(user) call; the issue names no files or tests. Clarify the intended invalidation behavior for multiple live refresh tokens before choosing an approach. Done means the agreed behavior is implemented and verified with appropriate authentication tests.

Written by the indexing model from the issue text.