New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[nuxt] Cannot load payload /_payload.json #22068
Comments
I ran into the same issue. It works fine in Nuxt version 3.6.1. I think it's caused by this PR: #21860 |
This did fix the warning message, but it did not fix the navigation issue. I still get redirected back to "/". It seems like this only applies to routes with multiple childeren. Normal routes without childeren works or routes with only 1 child works fine. |
In that case, would you provide a reproduction? 🙏 |
possibly same issue as #22072 |
Experienced this when attempting to deploy a fully static site with payload extraction. Downgrade to 3.6.1 fixed it for me. |
What I’ve found out is that since export default defineNuxtConfig({
experimental: {
payloadExtraction: true
}
}) |
That fixes it for me 🙏🏽 |
Would you try with the latest v3.6.3? |
Had the issue with |
This fixed it for me too! thanks a lot! |
I think the problem is that after #21860, |
Cannot load payload in Nuxt 3.6.5 mounted() {
experimental: { I'm trying to fix it , still not solve this error |
@JonathanDoelan Thank you for the workaround. This worked to get |
When using |
My workaround is not necessary any more since v3.6.3 |
@manniL Oh interesting, I'll have to look into the docs and maybe the source code more regarding that, I guess. Thanks! |
Environment
Reproduction
its a pretty big project, It always worked fine and all I did before this happened was running npm install
Describe the bug
When using my nuxt site using a different domain navigating to other pages stops working
when I build my site and upload it to azure it comes available on multiple domains
On our subdomain the website navigation stops working and spits out the following error:
Additional context
No response
Logs
The text was updated successfully, but these errors were encountered: