Closed santiagoaloi closed 3 months ago
Additionally
const { data } = await useAsyncData('articles', () => queryContent('/articles').find())
running this in production, while owning a /content/articles folder with .md files in it, returns an empty Array.
Hi,
Not sure if it helps but just leaving some feedback here. I also came across this issue (or very similar, error 500 when querying content only on prod) and managed to fix it by adding the following in my package.json:
"resolutions": {
"nitropack": "2.8.1"
}
Using yarn v4 with nodeLinker: node-modules
Hi,
Not sure if it helps but just leaving some feedback here. I also came across this issue (or very similar, error 500 when querying content only on prod) and managed to fix it by adding the following in my package.json:
"resolutions": { "nitropack": "2.8.1" }
Using yarn v4 with nodeLinker: node-modules
Using resolutions
and nitropack@2.8.1
indeed resolves the issue. I appreciate you sharing this workaround. π
Seems that Nitro generate different kind of chunk for JSON files.
Maybe @pi0 could help us on this
This issue is resolved in the latest Nitro version (v2.9.3).
For reference: https://github.com/unjs/nitro/pull/2239.
We can all remove the resolutions override and use the latest Nitro version again. π
How to update the nitro version? i dont see nitro in my package.json π€
How to update the nitro version? i dont see nitro in my package.json π€
You have to delete your lockfile (package-lock.json
or pnpm-lock.yaml
) and install your dependencies freshly.
Could this be related somehow? https://github.com/nuxt/content/issues/2378
I'm using nitropack: 2.9.4
which is the latest and getting this error during build:
Prerendering 1 routes nitro 3:45:45 PM
ββ /api/_content/cache.1711021521779.json (14ms) nitro 3:45:45 PM
β βββ Error: [500]
nitro 3:45:45 PM
Errors prerendering:
ββ /api/_content/cache.1711021521779.json (14ms) nitro 3:45:45 PM
β βββ Error: [500]
nitro 3:45:45 PM
ERROR Exiting due to prerender errors.
any idea ?
I'm also on nitropack@2.9.4, getting the following error when running nuxt generate
:
ERROR Entry module "../node_modules/.pnpm/nitropack@2.9.1/node_modules/nitropack/dist/runtime/entries/nitro-prerenderer" cannot be external.
at getRollupError (node_modules/.pnpm/rollup@4.13.0/node_modules/rollup/dist/es/shared/parseAst.js:376:41)
at error (node_modules/.pnpm/rollup@4.13.0/node_modules/rollup/dist/es/shared/parseAst.js:372:42)
at ModuleLoader.loadEntryModule (node_modules/.pnpm/rollup@4.13.0/node_modules/rollup/dist/es/shared/node-entry.js:18918:20)
at async Promise.all (index 0)
I'm using
nitropack: 2.9.4
which is the latest and getting this error during build:Prerendering 1 routes nitro 3:45:45 PM ββ /api/_content/cache.1711021521779.json (14ms) nitro 3:45:45 PM β βββ Error: [500] nitro 3:45:45 PM Errors prerendering: ββ /api/_content/cache.1711021521779.json (14ms) nitro 3:45:45 PM β βββ Error: [500] nitro 3:45:45 PM ERROR Exiting due to prerender errors.
any idea ?
Hi @tahirmahmudzade,
I've the same error. Did you find any fix for the issue? I'm on the latest nitropack@2.9.6
.
I'm using
nitropack: 2.9.4
which is the latest and getting this error during build:Prerendering 1 routes nitro 3:45:45 PM ββ /api/_content/cache.1711021521779.json (14ms) nitro 3:45:45 PM β βββ Error: [500] nitro 3:45:45 PM Errors prerendering: ββ /api/_content/cache.1711021521779.json (14ms) nitro 3:45:45 PM β βββ Error: [500] nitro 3:45:45 PM ERROR Exiting due to prerender errors.
any idea ?
Hi @tahirmahmudzade, I've the same error. Did you find any fix for the issue? I'm on the latest
nitropack@2.9.6
.
Could you share yournuxt.config
file?
Here is my nuxt.config.ts
export default defineNuxtConfig({
modules: ['@nuxthub/core', '@nuxt/ui', '@nuxt/image', '@nuxt/content'],
devtools: { enabled: true },
image: {
format: ['avif', 'webp'],
},
});
and package versions in package.json
"dependencies": {
"@nuxt/content": "^2.12.1",
"@nuxt/image": "^1.5.0",
"@nuxt/ui": "^2.15.1",
"@nuxthub/core": "^0.4.0",
"nuxt": "^3.11.2"
},
"devDependencies": {
"@nuxt/eslint-config": "^0.2.0",
"eslint": "^8.57.0",
"vue-tsc": "^2.0.7",
"wrangler": "^3.45.0"
}
Below is the build log on my local machine
βΉ Initializing prerenderer nitro 12:56:52 AM
βΉ Prerendering 1 routes nitro 12:56:58 AM
ββ /api/_content/cache.1712258784361.json (9ms) nitro 12:56:58 AM
β βββ Error: [500]
nitro 12:56:58 AM
Errors prerendering:
ββ /api/_content/cache.1712258784361.json (9ms) nitro 12:56:58 AM
β βββ Error: [500]
nitro 12:56:58 AM
ERROR Exiting due to prerender errors. 12:56:58 AM
at prerender (node_modules/nitropack/dist/chunks/prerender.mjs:218:11)
at async node_modules/nuxt/dist/index.mjs:3471:7
at async build (node_modules/nuxt/dist/index.mjs:5001:5)
at async Object.run (node_modules/nuxi/dist/chunks/build.mjs:95:5)
at async runCommand$1 (node_modules/nuxi/dist/shared/nuxi.9edf0930.mjs:1648:16)
at async runCommand$1 (node_modules/nuxi/dist/shared/nuxi.9edf0930.mjs:1639:11)
at async runMain$1 (node_modules/nuxi/dist/shared/nuxi.9edf0930.mjs:1777:7)
ERROR Exiting due to prerender errors. 12:56:58 AM
error: script "build" exited with code 1
This issue is resolved in the latest Nitro version (v2.9.3).
Perfect, this settles the issue then.
Here is my
nuxt.config.ts
export default defineNuxtConfig({ modules: ['@nuxthub/core', '@nuxt/ui', '@nuxt/image', '@nuxt/content'], devtools: { enabled: true }, image: { format: ['avif', 'webp'], }, });
and package versions in
package.json
"dependencies": { "@nuxt/content": "^2.12.1", "@nuxt/image": "^1.5.0", "@nuxt/ui": "^2.15.1", "@nuxthub/core": "^0.4.0", "nuxt": "^3.11.2" }, "devDependencies": { "@nuxt/eslint-config": "^0.2.0", "eslint": "^8.57.0", "vue-tsc": "^2.0.7", "wrangler": "^3.45.0" }
Below is the build log on my local machine
βΉ Initializing prerenderer nitro 12:56:52 AM βΉ Prerendering 1 routes nitro 12:56:58 AM ββ /api/_content/cache.1712258784361.json (9ms) nitro 12:56:58 AM β βββ Error: [500] nitro 12:56:58 AM Errors prerendering: ββ /api/_content/cache.1712258784361.json (9ms) nitro 12:56:58 AM β βββ Error: [500] nitro 12:56:58 AM ERROR Exiting due to prerender errors. 12:56:58 AM at prerender (node_modules/nitropack/dist/chunks/prerender.mjs:218:11) at async node_modules/nuxt/dist/index.mjs:3471:7 at async build (node_modules/nuxt/dist/index.mjs:5001:5) at async Object.run (node_modules/nuxi/dist/chunks/build.mjs:95:5) at async runCommand$1 (node_modules/nuxi/dist/shared/nuxi.9edf0930.mjs:1648:16) at async runCommand$1 (node_modules/nuxi/dist/shared/nuxi.9edf0930.mjs:1639:11) at async runMain$1 (node_modules/nuxi/dist/shared/nuxi.9edf0930.mjs:1777:7) ERROR Exiting due to prerender errors. 12:56:58 AM error: script "build" exited with code 1
For this one I had raised an issue in the @nuxthub/core
repo. Here is the resolution.
Environment
Build Modules: -
Reproduction
Repo: https://github.com/santiagoaloi/nuxt_content_issue Live: https://nuxt-content-issue.vercel.app/
Describe the bug
I'm encountering a production-specific 500 error when using
queryContent
in any Vue SFC component within my Nuxt 3 project. This issue does not occur during development.Steps to Reproduce:
1- Create a fresh Nuxt 3 project (no custom configurations or additional libraries). 2- Define some content using the
@nuxt/content
module., e.g a file namedhello.json
with the following content:3- In any SFC component, attempt to fetch content using
queryContent
:4- Build the project for production:
5- Run the production server and the app in the browser.
Expected Behavior:
The content defined in page should be successfully retrieved and displayed in the component's template.
Actual Behavior:
The server throws a 500 Internal Server Error. The error log typically includes:
Additional context
I've also attempted the following troubleshooting steps:
Deployment to Vercel: I deployed the project to Vercel to see if the issue was specific to my local development environment. However, the 500 error persisted in the production build on Vercel.
Nitro Prerender Settings: I experimented with various Nitro prerender settings in an attempt to resolve the issue, but none of the configurations seemed to address the problem.
Nitropack Override: I tried overriding the default Nitropack version in the
package.json
file by adding the following configuration:However, this attempt also did not resolve the 500 error.
Logs
No response