Consider a logging warning when both `GQL_TOKEN` and `clients.default.token` are set

[maximilliangeorge]

Your use case

I spent a few agonising hours trying to understand why authentication wasn't working in production. Turns out I had an old GQL_TOKEN in my environment variables, which cancelled out whatever token I was trying to define in my nuxt.config.ts.

The solution you'd like

I can see the benefits of being able to define the token in two separate ways, but it would be nice with some sort of hint that the token in nuxt.config.ts was being overwritten.

Possible alternatives

No response

Additional information

No response