FiveDigitLP
New prerender errors
@kapa.ai I downgraded from rollup 4.27.4 back to 4.22.4 and I am able to run
npm run build
locally without the "Nuxt instance unavailable" error. Is there anything between those versions of rollup or its dependencies that would cause this? I think the issue is a combination of our code and something that changed in Rollup, but I am unable to determine the fix in our code.30 replies
New prerender errors
@kapa.ai Based on my research and the work I've done so far, I think the issue could be an async one. However, I am not sure how to identify where the problem code is. I am seeing this error on the only route we are currently pre-rendering (
/software/bibles
), but if I run npm run generate
then I get plenty of 500 errors for other routes as well. So does that mean this is an async issue at the root of our code or is the problem somewhere else altogether?30 replies
New prerender errors
@kapa.ai We are currently on Nuxt 3.11.1. Do you know if that is incompatible with Rollup 3.29.5? That being said, I also tried running
nuxi upgrade
and even on the latest version of Nuxt we still were receiving this error. Perhaps it is an incompatibility with a different dependency?30 replies
Reactively add/remove a class name to <body>, from within a component...
Thanks! That didn't seem to work.
At this point, I think it might have something to do with the way I have my page routes set up. For some reason, I have a
software.vue
page set up in the root of my pages
folder in addition to having the nested routes under /software
. I remember reading in the documentation during the early stages of my project about this being an option, but I don't remember why exactly I chose this structure as I think it has caused more headaches than it's worth.45 replies
Reactively add/remove a class name to <body>, from within a component...
I hate to piggy-back on this, but at the same time I am dealing with something very similar. The primary difference being that I don't even have any sort of conditional for the class.
My goal is to have a body class that shows up on some pages and not on others. I thought it would be simple enough if I set
bodyAttrs
differently between pages, but that doesn't seem to be doing it. I have tried both setting the value bodyAttrs: { class: }
to a ref
and adding an anonymous function as above, but the class still seems to stick between pages. Any ideas??
Here's what I have for my pricing page:
And here's another page:
The title and page description changes, so I'm not sure why the bodyAttrs
doesn't.45 replies
NuxtLink create an a href="", but a click on it doesn't change page, anything happen
It may be invalid, but that shouldn't be causing his problem. In our code, we put NuxtLinks around PrimeVue buttons that render the same as above and they work just fine.
7 replies
POST to page returns 405 error
In case anyone else struggles with this issue in the future, it does seem that this is an Azure issue and seemingly how they expect/intend for it to work:
https://github.com/Azure/static-web-apps/issues/1132
https://learn.microsoft.com/en-us/azure/static-web-apps/apis-overview
https://github.com/Azure/static-web-apps/issues/831
20 replies