If it helps, a rollback to `supertoken-node` to 4....
# support-questions
g
If it helps, a rollback to
supertoken-node
to 4.3.1 solves the issue