feat(#1046): Add automatic middleware; fix navigateUnauthenticatedTo

[phoenix-ru]

🔗 Linked issue

Closes #1046

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This adds the automatic detection of definePageMeta({ auth: true }) and definePageMeta({ auth: {} }) and attaching the middleware to such pages.

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@sidebase/nuxt-auth@1054

commit: f7c6711

[zoey-kaiser]

question: Don't we lose the callback url then? E.g. if I send someone to a custom register / signin page this could be seen as a breaking behaviour change right?

[phoenix-ru]

No, I have checked and the behaviour seems to be exactly as expected - navigateUnauthenticatedTo only applies for non-logged-in users. If you do the following on a register/signin page:

definePageMeta({
  navigateUnauthenticatedTo: '/',
})

then yes, it will behave exactly like that.

The authjs sign-in is using the error parameter, meaning that it will redirect to the login page and not to the configured navigateUnauthenticatedTo. This seems to not be what users expect in such a case: #1046