Closed rashidpathiyil closed 1 year ago
same problem nuxt 3.5.0 change @nuxt/kit in this commit
I use "refresh" scheme. I just changed the strategy to the existing one "auth0" and set "refresh" scheme. This works as a temporary fix.
auth: {
strategies: {
auth0: {
scheme: 'refresh',
.....
same issue here
+1 here
I got this error when I upgraded nuxt to version 3.5.0
I just installed the module:
npm install local
Possibly has to do with this: https://github.com/nuxt/nuxt/issues/20883 I'd suggest sticking with something below 3.5 til they update so I can see if I need to make some updates.
Possibly has to do with this: https://github.com/nuxt/nuxt/issues/20883
https://github.com/nuxt/nuxt/issues/20883 is closed in Nuxt 3.5.1 but the issue is still there.☹️ @Teranode
+1 with nuxt nuxt 3.4.3
& 3.5.1
I use "refresh" scheme. I just changed the strategy to the existing one "auth0" and set "refresh" scheme. This works as a temporary fix.
auth: { strategies: { auth0: { scheme: 'refresh', .....
Also did like this but it will attach scope: string[]
field to request. After configuring the backend to not to fail when meeting unknown properties login started to work
I made some research and here are my observations:
1) The error message doesn't affect anything. Authentication works normally both in dev build and in production build.
2) The problem was always there! The only difference between Nuxt 3.5 and 3.4 is that 3.4 printed no warning message for a failed import—but it was crashing the same way. If you add console.log
into this catch block if you will see all sort of errors importing local
, cookie
, refresh
, etc.:
https://github.com/nuxt-alt/auth/blob/23028d60e561ea2a97ae904e095733a92e43b54f/src/resolve.ts#L120-L125
3) I came up with this simple hack/workaround to silence the error:
export default defineNuxtConfig({
auth: {
strategies: {
refresh: {
// Silence nuxt-auth error, see https://github.com/nuxt-alt/auth/issues/54
provider: () => {},
},
},
},
})
@Teranode Is that essential to bump dependencies
to "@nuxt/kit": "^3.6.1"
? Will the module not work in Nuxt 3.4.x? At first glance it seems there is no code in the patch that depends on 3.6.
The reason I'm asking is because I can't upgrade to Nuxt 3.5 as it introduced some breaking regressions (e.g. https://github.com/nuxt/nuxt/issues/21417). Now I can't upgrade @nuxt-alt/auth
either.
@IlyaSemenov looks like the project is dead and someone need to fork this module
@Teranode Is that essential to bump
dependencies
to"@nuxt/kit": "^3.6.1"
? Will the module not work in Nuxt 3.4.x? At first glance it seems there is no code in the patch that depends on 3.6.The reason I'm asking is because I can't upgrade to Nuxt 3.5 as it introduced some breaking regressions (e.g. nuxt/nuxt#21417). Now I can't upgrade
@nuxt-alt/auth
either.
Hmm, I usually bump things up because there's usually something that breaks when going back a minor version, I'll change it.
@IlyaSemenov looks like the project is dead and someone need to fork this module
It's not dead, I've just been really busy and was taking a long time off development. I'm back now though.
@Teranode Is that essential to bump
dependencies
to"@nuxt/kit": "^3.6.1"
? Will the module not work in Nuxt 3.4.x? At first glance it seems there is no code in the patch that depends on 3.6.The reason I'm asking is because I can't upgrade to Nuxt 3.5 as it introduced some breaking regressions (e.g. nuxt/nuxt#21417). Now I can't upgrade
@nuxt-alt/auth
either.
try updating to 2.5.2
Environment
Nuxt Config
Reproduction
-
Describe the bug
Error In Terminal
After Upgraded to:
Upgraded From.
Using Nuxt@3.5.0
Additional context
No response
Logs
No response