fix: Remove getSession usage from SSR

[anku255]

Summary of change

This PR updates the boilerplate of Astro, Remix and NextJS (app dir) to remove the getSession usage in the SSR.

Related issues

• Link to issue1 here
• Link to issue1 here

Test plan

• If added a new boilerplate
  • I tested the new boilerplate by running the CLI locally
  • I tested that the boilerplate is created and works correctly when using command line flags (--recipe=... for example)
• If added a new recipe, frontend or backend
  • I tested that the newly added option is usable by passing command line flags (--recipe=... for example)

Checklist for important updates

• Changelog has been updated
• Changes to the version if needed
  • In package.json
  • In package-lock.json
  • In lib/ts/version.ts
• Had run npm run build-pretty
• Had installed and ran the pre-commit hook
• If added a new recipe, I also modified types to include the new recipe in Recipe and allRecipes
• If added a new frontend, I also modified types to include the new frontend in SupportedFrontends and allFrontends if required
• If added a new backend, I also modified types to include the new backend in SupportedBackends and allBackends if required

[tocaherge]

Is there a documented reason behind this change?
These docs still show getSSRSession being used: https://supertokens.com/docs/thirdparty/nextjs/app-directory/protecting-route#using---presessionauthfornextjs-and-checking-for-sessions--pre

[anku255]

Hi @tocaherge!

The reason behind this change is that getSession / verifySession functions from the supertokens-node SDK may update the access token. These updated tokens would not be propagated to the client side properly, as request interceptors do not run on the server side. So, instead we use regular JWT verification library to parse the tokens to avoid any inconsistency.

As for the docs, they will be updated very soon. You can track the changes in supertokens/docs#804