Strange behavior after updating to 6.x

[Woloja]

Hello friends!
Today I was updating packages in my project, and as soon as I updated nuxt-auth-sanctum from ^0.5.8 I started receiving duplicate logs from sanctum.interceptors.onRequest in the console:

1st page load and with every page load, I get +1

[nuxt-auth-sanctum:ssr] [onRequest] custom interceptor (/api/user)
[nuxt-auth-sanctum:ssr]  WARN  [response] set-cookie header is missing, CSRF token will not be set

2nd page load

[nuxt-auth-sanctum:ssr] [onRequest] custom interceptor (/api/user)
[nuxt-auth-sanctum:ssr] [onRequest] custom interceptor (/api/user)
[nuxt-auth-sanctum:ssr]  WARN  [response] set-cookie header is missing, CSRF token will not be set

3rd page load

[nuxt-auth-sanctum:ssr] [onRequest] custom interceptor (/api/user)
[nuxt-auth-sanctum:ssr] [onRequest] custom interceptor (/api/user)
[nuxt-auth-sanctum:ssr] [onRequest] custom interceptor (/api/user)
[nuxt-auth-sanctum:ssr]  WARN  [response] set-cookie header is missing, CSRF token will not be set

...

[nuxt-auth-sanctum:ssr] [onRequest] custom interceptor (/api/user)
[nuxt-auth-sanctum:ssr] [onRequest] custom interceptor (/api/user)
[nuxt-auth-sanctum:ssr] [onRequest] custom interceptor (/api/user)
[nuxt-auth-sanctum:ssr] [onRequest] custom interceptor (/api/user)
[nuxt-auth-sanctum:ssr]  WARN  [response] set-cookie header is missing, CSRF token will not be set

Did I do something wrong?

In fact, when I saw this in my project, I decided to check it in an empty sandbox only with nuxt^3.16.2 and nuxt-auth-sanctum^0.6.4

[manchenkoff]

Hey @Woloja! Thanks for this question. Indeed, there is a bug in the last release, I'm on my way to fix it, please track it here - #360