EGGSY
Nuxt Content didn't deploy to Netlify, static generation broke my server routes, I fixed all tho.
I had to move to static generation and had to move my server API route to a Netlify function. It's all good now, except I wish I was able to use a node-server.
Also, I was using the
nitro:build:public-assets build hook to generate OG images using Satori for my blog posts (see code here). It used to create a folder in the .output/public directory and everything worked fine, the images were accessible in a normal build and a static build without a preset. But when I deployed on Netlify, it didn't really copy the generated folder to dist directory which made images unavailable on production. This seems like a bug, maybe you should look into this?6 replies