nuxt-hub / core

Build full-stack applications with Nuxt on CloudFlare, with zero configuration.
https://hub.nuxt.com
Apache License 2.0
993 stars 57 forks source link

Could not load /opt/buildhome/repo/node_modules/nitropack/dist/runtime/routes/openapi.mjs #366

Closed remihuigen closed 2 weeks ago

remihuigen commented 2 weeks ago

Describe the bug On nuxhub/core@0.8.4, I'm getting a fatal build error (after nitro server is built). It fails to import openapi from nitropack

If nitro.experimental.openAPI is disabled in nuxt.config, the build succeeds.

Could be something related to the nitro 2.10.0 release?

12:14:39.987 [success] Server built in 8586ms
12:14:39.990 [log] adding trailing slash to all prerender routes
12:14:39.991 [info] [nitro] Initializing prerenderer
12:14:41.340 [error] [nitro] Error: Could not load /opt/buildhome/repo/node_modules/nitropack/dist/runtime/routes/openapi.mjs (imported by node_modules/@nuxthub/core/dist/runtime/openapi/server/api/_hub/openapi.get.js): ENOENT: no such file or directory, open '/opt/buildhome/repo/node_modules/nitropack/dist/runtime/routes/openapi.mjs'
12:14:41.341 
12:14:41.341 
12:14:41.341 undefined
12:14:41.341 [error] Could not load /opt/buildhome/repo/node_modules/nitropack/dist/runtime/routes/openapi.mjs (imported by node_modules/@nuxthub/core/dist/runtime/openapi/server/api/_hub/openapi.get.js): ENOENT: no such file or directory, open '/opt/buildhome/repo/node_modules/nitropack/dist/runtime/routes/openapi.mjs'
12:14:41.341    
12:14:41.341 
12:14:41.341 [error] Could not load /opt/buildhome/repo/node_modules/nitropack/dist/runtime/routes/openapi.mjs (imported by node_modules/@nuxthub/core/dist/runtime/openapi/server/api/_hub/openapi.get.js): ENOENT: no such file or directory, open '/opt/buildhome/repo/node_modules/nitropack/dist/runtime/routes/openapi.mjs'
12:14:41.415 Failed: Error while executing user command. Exited with error code: 1
12:14:41.426 Failed: build command exited with code: 1
12:14:42.606 Failed: error occurred while running build command
atinux commented 2 weeks ago

This is now fixed in v0.8.5