K
Kinde•22h ago
Hillary

500 Server Error until Kinde Cookie is deleted in Nuxt

Users keep getting 500 Server Error, whenever app domain changes and callback url changes, or another Kinde Web app logs out. We've been solving this by clearing Kinde Cookies in the browser application settings This is what appears in our logs: 
[request error] [unhandled] [GET] https://localhost:3000/__nuxt_error?error=true&url=%2F&statusCode=500&statusMessage=Server+Error&message=Server+Error
 Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/app/.output/server/node_modules/vue/index.mjs' imported from /app/.output/server/chunks/routes/renderer.mjs
Did you mean to import "file:///app/.output/server/node_modules/.nitro/[email protected]/dist/vue.cjs.prod.js"?
    at finalizeResolution (node:internal/modules/esm/resolve:274:11)
    ... 6 lines matching cause stack trace ...
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
  cause: Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/app/.output/server/node_modules/vue/index.mjs' imported from /app/.output/server/chunks/routes/renderer.mjs
  Did you mean to import "file:///app/.output/server/node_modules/.nitro/[email protected]/dist/vue.cjs.prod.js"?
      at finalizeResolution (node:internal/modules/esm/resolve:274:11)
      at moduleResolve (node:internal/modules/esm/resolve:859:10)
      at defaultResolve (node:internal/modules/esm/resolve:983:11)
      at #cachedDefaultResolve (node:internal/modules/esm/loader:717:20)
      at ModuleLoader.resolve (node:internal/modules/esm/loader:694:38)
      at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:308:38)
      at ModuleJob._link (node:internal/modules/esm/module_job:183:49)
      at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
    code: 'ERR_MODULE_NOT_FOUND',
    url: 'file:///app/.output/server/node_modules/vue/index.mjs'
  },
  statusCode: 500,
  fatal: false,
  unhandled: true,
  statusMessage: undefined,
  data: undefined
}
[request error] [unhandled] [GET] https://localhost:3000/__nuxt_error?error=true&url=%2F&statusCode=500&statusMessage=Server+Error&message=Server+Error
 Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/app/.output/server/node_modules/vue/index.mjs' imported from /app/.output/server/chunks/routes/renderer.mjs
Did you mean to import "file:///app/.output/server/node_modules/.nitro/[email protected]/dist/vue.cjs.prod.js"?
    at finalizeResolution (node:internal/modules/esm/resolve:274:11)
    ... 6 lines matching cause stack trace ...
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
  cause: Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/app/.output/server/node_modules/vue/index.mjs' imported from /app/.output/server/chunks/routes/renderer.mjs
  Did you mean to import "file:///app/.output/server/node_modules/.nitro/[email protected]/dist/vue.cjs.prod.js"?
      at finalizeResolution (node:internal/modules/esm/resolve:274:11)
      at moduleResolve (node:internal/modules/esm/resolve:859:10)
      at defaultResolve (node:internal/modules/esm/resolve:983:11)
      at #cachedDefaultResolve (node:internal/modules/esm/loader:717:20)
      at ModuleLoader.resolve (node:internal/modules/esm/loader:694:38)
      at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:308:38)
      at ModuleJob._link (node:internal/modules/esm/module_job:183:49)
      at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
    code: 'ERR_MODULE_NOT_FOUND',
    url: 'file:///app/.output/server/node_modules/vue/index.mjs'
  },
  statusCode: 500,
  fatal: false,
  unhandled: true,
  statusMessage: undefined,
  data: undefined
}
2 Replies
Roshan
Roshan•18h ago
Hi Hillary, thanks for sharing this. To reproduce and escalate internally, could you clarify: - Does the 500 happen specifically while logging in or when your app is calling other associated APIs? - Does it also happen after changing/adding callback URLs, or after logging out of another Kinde app in the same browser? - Could you outline the exact steps (browser, domain, URLs, and at what point the 500 appears)? This might be something fundamental on our side, but I’ll need a reproducible case to take it to the internal team.

Thanks a lot.
Hillary
HillaryOP•16h ago
Hi Roshan, while trying to reproduce the issue, I figured that the 500 Server Error we had a while back has probably been resolved - it might have been incorrect callbacks. Can't recall exactly what caused them, but it usually happened when we added a custom domain after having logged in using the default cloud provider's app url. Then when using the new URL, that's where the error would occur. Quick Update is that I've now resolved the current build issues we were facing. After doing some research, I found similar problems reported with Vue The issue we were experiencing was that certain packages weren't being properly handled during the build process, leading to module resolution errors in production. The problems I faced included: 1. Vue module resolution error: Cannot find module 'vue/index.mjs' 2. Entities package export error: Package subpath './lib/decode.js' is not defined by "exports" 3. Estree-walker default export error: The requested module 'estree-walker' does not provide an export named 'default' and the solution I applied is that I updated our nuxt.config.ts to properly handle these packages by adding them to the transpile list and module side effects: 
// In nuxt.config.ts
nitro: {
  esbuild: {
    options: {
      target: 'esnext'
    }
  },
  experimental: {
    wasm: true
  },
  rollupConfig: {
    external: []
  },
  moduleSideEffects: ['vue', 'entities', 'estree-walker']
},
build: {
  transpile: ['vue', 'entities', 'estree-walker']
},
// In nuxt.config.ts
nitro: {
  esbuild: {
    options: {
      target: 'esnext'
    }
  },
  experimental: {
    wasm: true
  },
  rollupConfig: {
    external: []
  },
  moduleSideEffects: ['vue', 'entities', 'estree-walker']
},
build: {
  transpile: ['vue', 'entities', 'estree-walker']
},
rollupConfig.external: [] prevents these packages from being treated as external dependencies The fix ensured that npm run start and bun run start worked correctly after building our application.

Did you find this page helpful?