When I simply enable the '@nuxtjs/robots' module using Nuxt bridge v3.0.0-27639120.e7a7f9b, I get the following error:
...
✔ Generated public .output/public nitro 22:46:27
ℹ Initializing prerenderer nitro 22:46:27
ℹ Prerendering 1 routes nitro 22:46:41
ERROR [h3] [unhandled] This page could not be found 22:46:42
at createError (node_modules/.pnpm/h3@0.7.12/node_modules/h3/dist/index.mjs:191:15)
at nodeHandler (node_modules/.pnpm/h3@0.7.12/node_modules/h3/dist/index.mjs:381:21)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async ufetch (node_modules/.pnpm/unenv@0.5.2/node_modules/unenv/runtime/fetch/index.mjs:9:17)
at async generateRoute (node_modules/.pnpm/nitropack@0.4.12_vite@2.9.14+webpack@4.46.0/node_modules/nitropack/dist/chunks/prerender.mjs:2535:17)
at async prerender (node_modules/.pnpm/nitropack@0.4.12_vite@2.9.14+webpack@4.46.0/node_modules/nitropack/dist/chunks/prerender.mjs:2565:22)
at async node_modules/.pnpm/@nuxt+bridge-edge@3.0.0-27639120.e7a7f9b_sz4l2dz37qxtrukeof3aez25wu/node_modules/@nuxt/bridge-edge/dist/chunks/module.mjs:361:7
at async Nuxt.callHook (node_modules/.pnpm/hable@3.0.0/node_modules/hable/dist/hable.js:1:959)
at async Builder.build (node_modules/.pnpm/@nuxt+builder-edge@2.16.0-27616340.013f051b_m56akxypyp7f72pxuiucyg54wm/node_modules/@nuxt/builder-edge/dist/builder.js:264:5)
at async Object.invoke (node_modules/.pnpm/nuxi@3.0.0-rc.6/node_modules/nuxi/dist/chunks/build.mjs:41:5)
at async _main (node_modules/.pnpm/nuxi@3.0.0-rc.6/node_modules/nuxi/dist/cli.mjs:46:20)
├─ /robots.txt (802ms) (Error: [404] Internal Server Error) nitro 22:46:42
start Building server... nitro 22:46:42
...
Accessing /robots.txt when running the built output results in a 404 as well. I tried using options and a config file too, but that yields no change. If that issue is not already on the radar and not reproducible for someone else, I can set up a codesandbox of course.
When I simply enable the
'@nuxtjs/robots'
module using Nuxt bridgev3.0.0-27639120.e7a7f9b
, I get the following error:Accessing
/robots.txt
when running the built output results in a 404 as well. I tried using options and a config file too, but that yields no change. If that issue is not already on the radar and not reproducible for someone else, I can set up a codesandbox of course.