nuxt: Cannot access 'renderer$1' before initialization is:closed

I’m closing this issue, as for me although I haven’t had time to fully investigate it looks to be any issue with something on the server.

I don’t feel like this should be closed tbh. Only because we haven’t figured out the cause yet doesn’t mean it’s not an issue/doesn’t exist

I had a similar issue when using the nuxt-auth package in conjunction with import GoogleProvider from "next-auth/providers/google"; . We might need to append .default to the one we imported, though I’m unclear on the exact reason. For example:

export default NuxtAuthHandler({
    providers: [
        // @ts-expect-error You need to use .default here for it to work during SSR. May be fixed via Vite at some point
        GithubProvider.default({
           clientId: 'enter-your-client-id-here',
           clientSecret: 'enter-your-client-secret-here'
        })
    ]
})

without .default we will got that error. I hope this helps!

@gmariusze are you fetching data from this API? This seems different from render$1 because it’s the name of your endpoint, healthcheck$1.

Can I see your code for where you are calling this API?

no code calling this endpoint (accessing via browser). literally pasted the whole code. “healthcheck$1” error refers to api/healthcheck.ts (the filename), also seen ‘render$1’ error, but honestly i can’t recall what differently i had at the time

using fresh nuxt 3 on pnpm, no other logic, project just initialized. by default api endpoints aren’t working.

nuxt js guide doesnt mention it, nor linter/ide notes it, but after i added EventHandler import to the top line (not defineEventHandler) i no longer see the error:

import type { EventHandler } from 'h3'

export default defineEventHandler(() => ({
"test": "test"
}))

if youre using prisma do npx prisma generate, it then downloads the rust engine i was able to solve this, i used npkill to delete my node modules i think that could be cause but yeah i fixed it with npx prisma generate

I was able to solve this by running npx prisma generate. But if your project doesn’t use Prisma, there might be going on something else unfortunately…

Well, I had the same issue and then I removed the autoImport that I set on nuxt.config.js and the endoint started to work. imports: { autoImport: false, },

experiencing similar issue

[nuxt] [request error] [unhandled] [500] Cannot access 'renderer$1' before initialization                                                22:51:07
  at ./.nuxt/dev/index.mjs:544:65

Hi. I was getting this error and it is solved now. What I was doing wrong is I was using the env file (in the server folder ‘APIs’) which I have deleted before. So I just commented on the line where I was using the env file to get some information. Maybe you are using some variable for another library like API key etc. which is making this issue

In case anyone stumbles upon this thread, the issue is very likely related to using a top level await in your code.

absolutely not. If i create a file with in server/api directory, called healthcheck.ts, that being the only file in server directory with content as such:

export default defineEventHandler(() => ({ “test”: “test” }));

error still occurs. Cannot access ‘healthcheck$1’ before initialization

In our case also the issue is with one of one of the server routes. Also we have specified the wrong keys in .env which prevented the server routes from starting.

Même problème avec le serve de Nuxt / Nitro

Nuxi 3.3.3                                                                                                                                             12:38:25
Nuxt 3.3.3 with Nitro 2.3.2                                                                                                                            12:38:25
                                                                                                                                                       12:38:26
  > Local:    http://localhost:3000/ 
  > Network:  http://172.17.0.2:3000/

ℹ Vite client warmed up in 2311ms                                                                                                                      12:38:29
✔ Nitro built in 551 ms                                                                                                                          nitro 12:38:30
[nitro] [dev] [uncaughtException] ReferenceError: require is not defined in ES module scope, you can use import instead                                12:38:30
    at file:///var/www/.nuxt/dev/index.mjs:705:16
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:526:24)                                                                                12:38:25
    at async loadESM (node:internal/process/esm_loader:91:5)
    at async handleMainPromise (node:internal/modules/run_main:65:12)
✔ Nitro built in 202 ms                                                                                                                          nitro 12:39:34
[nitro] [dev] [uncaughtException] ReferenceError: require is not defined in ES module scope, you can use import instead                                12:39:34
    at file:///var/www/.nuxt/dev/index.mjs:705:1
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:526:24)
    at async loadESM (node:internal/process/esm_loader:91:5)
    at async handleMainPromise (node:internal/modules/run_main:65:12)
[nuxt] [request error] [unhandled] [500] Cannot access 'azerty$1' before initialization                                                                12:40:16
  at ./.nuxt/dev/index.mjs:543:65  
  at processTicksAndRejections (node:internal/process/task_queues:96:5)  
  at async Object.handler (./node_modules/h3/dist/index.mjs:1247:19)  
  at async Server.toNodeHandle (./node_modules/h3/dist/index.mjs:1322:7)
[nuxt] [request error] [unhandled] [500] Cannot access 'renderer$1' before initialization                                                              12:40:16
  at ./.nuxt/dev/index.mjs:545:65  
  at processTicksAndRejections (node:internal/process/task_queues:96:5)  
  at async Object.handler (./node_modules/h3/dist/index.mjs:1247:19)  
  at async toNodeHandle (./node_modules/h3/dist/index.mjs:1322:7)  
  at async Object.ufetch [as localFetch] (./node_modules/unenv/runtime/fetch/index.mjs:9:17)  
  at async Object.errorhandler [as onError] (./.nuxt/dev/index.mjs:470:30)  
  at async Server.toNodeHandle (./node_modules/h3/dist/index.mjs:1329:9)
✔ Nitro built in 165 ms                                                                                                                          nitro 12:41:02
[nitro] [dev] [uncaughtException] ReferenceError: require is not defined in ES module scope, you can use import instead                                12:41:02
    at file:///var/www/.nuxt/dev/index.mjs:705:1
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:526:24)
    at async loadESM (node:internal/process/esm_loader:91:5)
    at async handleMainPromise (node:internal/modules/run_main:65:12)
[nuxt] [request error] [unhandled] [500] Cannot access 'azerty$1' before initialization                                                                12:41:28
  at ./.nuxt/dev/index.mjs:543:65  
  at processTicksAndRejections (node:internal/process/task_queues:96:5)  
  at async Object.handler (./node_modules/h3/dist/index.mjs:1247:19)  
  at async Server.toNodeHandle (./node_modules/h3/dist/index.mjs:1322:7)
[nuxt] [request error] [unhandled] [500] Cannot access 'renderer$1' before initialization                                                              12:41:28
  at ./.nuxt/dev/index.mjs:545:65  
  at processTicksAndRejections (node:internal/process/task_queues:96:5)  
  at async Object.handler (./node_modules/h3/dist/index.mjs:1247:19)  
  at async toNodeHandle (./node_modules/h3/dist/index.mjs:1322:7)  
  at async Object.ufetch [as localFetch] (./node_modules/unenv/runtime/fetch/index.mjs:9:17)  
  at async Object.errorhandler [as onError] (./.nuxt/dev/index.mjs:470:30)  
  at async Server.toNodeHandle (./node_modules/h3/dist/index.mjs:1329:9)

@michealroberts @honeyp-snyk I was getting this same error. Tracked it down to a bad file in /server/api – is that something you have looked into? It’s not obvious from the error but start by checking the files in that directory. I imagine problems could arise if you have non-route handler files that are maybe trying to be exported as route handlers.