#Nuxt 3.15.3 CORS change error with Firebase Auth
3 messages · Page 1 of 1 (latest)
Based on the knowledge sources provided, I don't have enough specific information to directly answer your question about the CORS change in Nuxt 3.15.3 affecting Firebase Auth. However, I can provide some relevant insights and suggestions based on the available information:
-
The changelog for Nuxt 3.15.3 doesn't mention any specific CORS-related changes that would affect Firebase Auth Github Pull Request. The changes listed are mostly related to performance improvements and fixes for unrelated issues.
-
There have been reports of issues with Firebase Auth in Nuxt 3 applications, particularly when deployed. For example, one user reported a "FirebaseError: Firebase: Error (auth/login-blocked)" issue Stack Overflow Post. In that case, the problem was resolved by removing the VueFire package.
-
If you suspect it's related to CORS, you might want to check your browser's console for any specific CORS-related error messages. These could provide clues about which domains are being blocked.
-
As a workaround, you could try disabling some experimental features to see if it resolves the issue. For example:
// nuxt.config.ts export default defineNuxtConfig({ experimental: { appManifest: false, } })This has been suggested as a workaround for other issues in Nuxt 3.15.x Github Issue Comment.
-
If the issue persists, you might want to try clearing your build cache. You can do this by removing the
.nuxtand.outputdirectories, and runningnpm clean-install(or your package manager's equivalent) before rebuilding.
- If none of these suggestions help, you might consider temporarily reverting to Nuxt 3.15.2 until a fix is found or more information becomes available.