Nuxt•2y ago

Need Help with Nuxt Middleware: Unexpected Behavior with navigateTo() Function

Hey everyone, I tried to implement an authentication flow to my Nuxt app, but I got stuck at the authentication middleware. When I use "return navigateTo('/')", the code after the middleware still runs. Is it normal for the navigateTo function to behave this way in a middleware?

<script setup>
definePageMeta({
  middleware: [
    function (to, from) {
      console.log('middleware start')
      return navigateTo('/')
    },
  ],
})

console.log('this code should not running') // ...but running :(
</script>

<script setup>
definePageMeta({
  middleware: [
    function (to, from) {
      console.log('middleware start')
      return navigateTo('/')
    },
  ],
})

console.log('this code should not running') // ...but running :(
</script>

If I use "return '/'" instead, it works as expected, but I'm not sure if this is a reliable solution:

<script setup>
definePageMeta({
  middleware: [
    function (to, from) {
      console.log('middleware start')
      return '/'
    },
  ],
})

console.log('this code should not running') // Not running as expected
</script>

<script setup>
definePageMeta({
  middleware: [
    function (to, from) {
      console.log('middleware start')
      return '/'
    },
  ],
})

console.log('this code should not running') // Not running as expected
</script>

5 Replies

Unknown User•2y ago

Message Not Public

SzaDave 👽OP•2y ago

I'm on 3.4.1.

Cue•2y ago

Just to confirm, this is executing on server side, not client side Seems intermittent too

SzaDave 👽OP•2y ago

Yes, its executing on the server side.

Unknown User•2y ago

Message Not Public

Gaming

Programming

Need Help with Nuxt Middleware: Unexpected Behavior with navigateTo() Function