Just curious on https://supertokens.com/docs/emailpassword/common-customizations/sessions/securing-component, why is the component which checks the session and redirects to auth routes specific to a recipe?

right yea. Is it clear?

Not from the docs, needed to dive into the code. Was going to PR the docs to call out the more generic component if you don't need email verification

Ah right yea. We are in the middle of this kind of a change anyway. Where you no longer need a recipe specific wrapper.