Spunkie
Explore posts from serversWhere do I place CF workers/functions?
I have a statically generated, content driven, nuxt3 site that is deployed on CF pages through the github integration.
Where an I supposed to be placing my workers/functions in my nuxt file structure so it eventually gets compiled to where it should be when generated? So CF pages automatically picks them up and deploys them as CF workers/functions?
4 replies
Comprehensive list of native front-matter meta tags?
The docs(https://content.nuxt.com/usage/markdown#front-matter) say that
title
, description
, draft
, navigation
, and head
are the only native parameters for front-matter.
But if I put an image
tag into my front-matter content files like this
nuxt does render it properly into a og:image
meta tag:
So where can I find an actual comprehensive list of native front-matter parameters?1 replies
404 status when displaying `Document is empty` message?
I have a static and content/document driven nuxt 3 blog.
It has some placeholder markdown files under
/content/
that just have their front-matter filled out. For example:
When I go to to the above example, example.com/tester
, it displays this error/msg but still returns a 200
status code.
How can I get nuxt to return a 404 status code whenever this Document is empty
error/msg shows up?1 replies
`npx nuxi generate` sometimes builds to .output/public and other times to .dist?
I'm using the latest nuxt on cloudflare pages but my builds are failing sometimes because of the differing output dir. I don't really understand what is causing the difference in behavior.
I'm following the nuxt docs on deployment so on CF pages I'm running
npx nuxi generate
and looking for the build dir of .output/public
. I've also tried with node 16 and 18 but it doesn't fix the issue.
Some branches are building, while others are not on CF. If I clone the branches with failed builds and run npx nuxi generate
locally it builds to the correct .output/public
dir.
CF pages:
Building same commit locally:
2 replies