Environment
- Operating System: Darwin
- Node Version: v22.14.0
- Nuxt Version: 3.15.4
- CLI Version: 3.21.1
- Nitro Version: 2.10.4
- Package Manager: npm@10.9.2
- Builder: -
- User Config: app, build, css, devServer, modules, nitro, runtimeConfig, ssr, vite, compatibilityDate
- Runtime Modules: @element-plus/nuxt@1.1.1, @nuxtjs/tailwindcss@6.13.1, @vueuse/nuxt@12.7.0, nuxt-graphql-client@0.2.43, unplugin-icons/nuxt@0.19.3
- Build Modules: -
Describe the bug
In nuxt-graphql-client version 0.2.34, I used useGqlToken(newToken) in login process, but now I upgraded to the 0.2.43 and it stopped working - no cookie was set.
But when I set client explicitly (for both clients I need) it works again:
useGqlToken(newToken, { client: 'default' })
useGqlToken(newToken, { client: 'tenant' })
In past it used just one cookie gql:default, but with this workaround is obviously sets two cookies - gql:default and gql:tenant.
Expected behaviour
Plain useGqlToken(newToken) should work again.
Reproduction
No response
Additional context
No response
Logs
Environment
Describe the bug
In nuxt-graphql-client version 0.2.34, I used
useGqlToken(newToken)in login process, but now I upgraded to the 0.2.43 and it stopped working - no cookie was set.But when I set client explicitly (for both clients I need) it works again:
In past it used just one cookie gql:default, but with this workaround is obviously sets two cookies - gql:default and gql:tenant.
Expected behaviour
Plain
useGqlToken(newToken)should work again.Reproduction
No response
Additional context
No response
Logs