ERROR [worker reload] [worker init] ../.nuxt/dev/index.mjs failed #6712

farahats9 · 2024-11-02T03:15:07Z

Describe the bug

Cannot run the project after adding primevue, the project is just the nuxt starter code and no other packages installed.

nuxt.config.ts

import Aura from '@primevue/themes/aura';

export default defineNuxtConfig({
    modules: [
        '@primevue/nuxt-module'
    ],
    primevue: {
        options: {
            theme: {
                preset: Aura
            }
        }
    }
})

I am using nuxt v3.13.2 vue latest (3.5) and primevue v4.2.1

It gives the error in the title and never loads the app in browser (stuck on the nuxt loading screen)

Reproducer

https://stackblitz.com/edit/nuxt-starter-vhvkfm

PrimeVue version

4.2.1

Vue version

4.x

Language

ALL

Build / Runtime

Nuxt

Browser(s)

All

Steps to reproduce the behavior

No response

Expected behavior

No response

molul · 2024-11-02T03:33:13Z

Having the exact same problem. Just started a Nuxt 3 project, then added PrimeVue following the docs, and I can't start it unless I remove PrimeVue.

EDIT: tried installing 4.1.1. Throws the same error. Can only continue by removing PrimeVue from the project.

wangziling · 2024-11-02T03:51:33Z

Yes, I have met the same issue, both under the developement/production mode.

I tried to install 4.2.0, 4.1.1, 4.1.0. All throw the same error.

Cannot access 'Mo' before initialization
  at useRuntimeConfig (/E:/Codes/xxx/.nuxt/dev/index.mjs:1:79646)
  at /E:/Codes/xxx/.nuxt/dev/index.mjs:1:48326
  at ModuleJob.run (node:internal/modules/esm/module_job:268:25)
  at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:543:26)
  at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:116:5)

Seems the issue caused by invoking the useRuntimeConfig() at the wrong phase.

Here:

primevue/packages/nuxt-module/src/module.ts

Line 105 in 7053618

const runtimeConfig = useRuntimeConfig();

I changed to const runtimeConfig = undefined;, works well.

Cannot use useRuntimeConfig(useEvent());, it throws Nitro request context is not available. Enable the experimental flag using experimental.asyncContext: true.

@molul I am using patch-package to patch the local-installed @primevue/nuxt-module line 242 to proceed my works.
Modify the const runtimeConfig = useRuntimeConfig(); to const runtimeConfig = undefined;.

doug-shontz · 2024-11-02T12:31:25Z

Can confirm the fix by @wangziling . Strange that it wasn't happening earlier this week, but thankful for the quick workaround to keep moving!

Noxdor · 2024-11-02T13:55:14Z

Can confirm the same issue.

Ed1ks · 2024-11-02T14:49:36Z

same here.
Didnt change anything in packages but suddently couldnt run fullstack debug. Love those bugs

j0rgedev · 2024-11-02T15:23:59Z

I also upgraded to 4.2.1 and I got:
ERROR [worker reload] [worker init] C:/Users/j0rge/Desktop/my-project/.nuxt/dev/index.mjs failed
I needed to downgrade to 4.1.1 and delete my .nuxt folder to make it run without errors. So, @wangziling don't forget also to delete the .nuxt folder, to make it work with 4.1.1

kiki-kanri · 2024-11-02T16:29:06Z

I guess it should be related to nitropack version 2.10, I installed nitropack version 2.9.7 and it works fine.

The problem is the location of the definition of useRuntimeConfig in the index.mjs file generated in version 2.10.

In version 2.9, the definition of useRuntimeConfig is at the top (at least it's not used anywhere above it).

In version 2.10, the location of the definition of useRuntimeConfig is no longer before any use, causing an error when primevue is used.

I'm not sure if this is a nitropack problem or a primevue one, but the current solution seems to be to downgrade the nitropack version to 2 9.7.

It looks like you can't use useRuntimeConfig in the top level, it has to be wrapped in a function, so it could be a problem with primevue, or nitropack (because of a change in the order of definitions).

This may affect more than just primevue's packages, so I'll try to open an issue there as well.

This is a description of nitro's use of useRuntimeConfig.

It seems to say that it can only be used in functions that start with define, but it's just that the way nitro builds itself allows useRuntimeConfig to be defined at the top, so there's no problem.

j0rgedev · 2024-11-02T18:59:07Z

@kiki-kanri i've just asked on twitter and pi0 said they're already investigating, so it seems to be a nitro problem

molul · 2024-11-02T19:39:19Z

Using 4.1.1 (previously deleting .nuxt folder, node_modules folfder and package-lock.json) doesn't fix the issue on my project. This is my package.json:

{
  "name": "nuxt-app",
  "private": true,
  "type": "module",
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev --host",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare",
    "reinstall": "rm -rf node_modules .nuxt package-lock.json && npm i"
  },
  "dependencies": {
    "@nuxt/eslint": "^0.6.1",
    "@nuxt/icon": "^1.6.1",
    "@primevue/themes": "4.1.1",
    "husky": "^9.1.6",
    "nuxt": "^3.13.2",
    "primevue": "4.1.1",
    "tailwindcss-primeui": "^0.3.4",
    "vue": "latest",
    "vue-router": "latest"
  },
  "devDependencies": {
    "@commitlint/cli": "^19.5.0",
    "@commitlint/config-conventional": "^19.5.0",
    "@nuxtjs/tailwindcss": "^6.12.2",
    "@primevue/nuxt-module": "4.1.1",
    "lint-staged": "^15.2.10"
  }
}

I get the same error message.

kiki-kanri · 2024-11-02T20:00:00Z

Using 4.1.1 (previously deleting .nuxt folder, node_modules folfder and package-lock.json) doesn't fix the issue on my project. This is my package.json:

{
  "name": "nuxt-app",
  "private": true,
  "type": "module",
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev --host",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare",
    "reinstall": "rm -rf node_modules .nuxt package-lock.json && npm i"
  },
  "dependencies": {
    "@nuxt/eslint": "^0.6.1",
    "@nuxt/icon": "^1.6.1",
    "@primevue/themes": "4.1.1",
    "husky": "^9.1.6",
    "nuxt": "^3.13.2",
    "primevue": "4.1.1",
    "tailwindcss-primeui": "^0.3.4",
    "vue": "latest",
    "vue-router": "latest"
  },
  "devDependencies": {
    "@commitlint/cli": "^19.5.0",
    "@commitlint/config-conventional": "^19.5.0",
    "@nuxtjs/tailwindcss": "^6.12.2",
    "@primevue/nuxt-module": "4.1.1",
    "lint-staged": "^15.2.10"
  }
}

I get the same error message.

Try install [email protected].

Here are the current solutions.

nuxt-hub/core#363 (comment)

molul · 2024-11-02T20:30:11Z

Using 4.1.1 (previously deleting .nuxt folder, node_modules folfder and package-lock.json) doesn't fix the issue on my project. This is my package.json:

{
  "name": "nuxt-app",
  "private": true,
  "type": "module",
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev --host",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare",
    "reinstall": "rm -rf node_modules .nuxt package-lock.json && npm i"
  },
  "dependencies": {
    "@nuxt/eslint": "^0.6.1",
    "@nuxt/icon": "^1.6.1",
    "@primevue/themes": "4.1.1",
    "husky": "^9.1.6",
    "nuxt": "^3.13.2",
    "primevue": "4.1.1",
    "tailwindcss-primeui": "^0.3.4",
    "vue": "latest",
    "vue-router": "latest"
  },
  "devDependencies": {
    "@commitlint/cli": "^19.5.0",
    "@commitlint/config-conventional": "^19.5.0",
    "@nuxtjs/tailwindcss": "^6.12.2",
    "@primevue/nuxt-module": "4.1.1",
    "lint-staged": "^15.2.10"
  }
}

I get the same error message.

Try install [email protected].

Here are the current solutions.

nuxt-hub/core#363 (comment)

It worked. Thanks!

j0rgedev · 2024-11-02T20:30:14Z

Using 4.1.1 (previously deleting .nuxt folder, node_modules folfder and package-lock.json) doesn't fix the issue on my project. This is my package.json:

{
  "name": "nuxt-app",
  "private": true,
  "type": "module",
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev --host",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare",
    "reinstall": "rm -rf node_modules .nuxt package-lock.json && npm i"
  },
  "dependencies": {
    "@nuxt/eslint": "^0.6.1",
    "@nuxt/icon": "^1.6.1",
    "@primevue/themes": "4.1.1",
    "husky": "^9.1.6",
    "nuxt": "^3.13.2",
    "primevue": "4.1.1",
    "tailwindcss-primeui": "^0.3.4",
    "vue": "latest",
    "vue-router": "latest"
  },
  "devDependencies": {
    "@commitlint/cli": "^19.5.0",
    "@commitlint/config-conventional": "^19.5.0",
    "@nuxtjs/tailwindcss": "^6.12.2",
    "@primevue/nuxt-module": "4.1.1",
    "lint-staged": "^15.2.10"
  }
}

I get the same error message.

I didn't get the same error message since my nuxt project had already been created before. Sorry for that. Please try @kiki-kanri answer

mertsincan · 2024-11-02T22:19:42Z

Thank you for all the detailed reports and workarounds 👏 The comments contain very valuable insights. For now, let's wait for a response from NitroPack. Once we hear back, we can decide together on any changes needed.

I'm pinning this issue so we can also gather more user feedback in the meantime.

pi0 · 2024-11-02T23:34:03Z

✅ Nitro 2.10.1 is released with a fix. Recreating lock-file should solve the problem (tested against reproduction).

j0rgedev · 2024-11-02T23:48:57Z

I've just upgraded to primevue 4.2.1 and there were no errors. Thank you so much @pi0 🫱🏻‍🫲🏻.

wangziling · 2024-11-03T00:41:48Z

✅ Nitro 2.10.1 is released with a fix. Recreating lock-file should solve the problem (tested against reproduction).

Thanks~ 😉

mertsincan · 2024-11-03T00:48:51Z

Wow! Thank you so much for your effort! Nitro man, @pi0 🚀
https://x.com/mertsincan/status/1852881167642436066

lpknv · 2024-11-03T09:03:42Z

✅ Nitro 2.10.1 is released with a fix. Recreating lock-file should solve the problem (tested against reproduction).

Huge thanks!

luizzappa · 2024-11-03T13:12:51Z

@pi0 , I had a similar problem ( nuxt/nuxt#29767 ) and this version 2.10.1 of Nitro solved it. However, alerts started to appear several times in the logs:

10:02:28.640	[plugin commonjs--resolver] It appears a plugin has implemented a "resolveId" hook that uses "this.resolve" without forwarding the third "options" parameter of "resolveId". This is problematic as it can lead to wrong module resolutions especially for the node-resolve plugin and in certain cases cause early exit errors for the commonjs plugin.
10:02:28.641	In rare cases, this warning can appear if the same file is both imported and required from the same mixed ES/CommonJS module, in which case it can be ignored.

My package.json:

 "overrides": {
    "vue": "^3.5.12",
    "nitropack": "2.10.1"
  }

pi0 · 2024-11-03T13:41:17Z

Solved in 2.10.2

luizzappa · 2024-11-03T13:49:28Z

Excellent! I just tested it and it was resolved

ejkgmea · 2024-11-04T04:10:11Z

Just delete yarn.lock or npm.lock file and reinstall the dependencies to upgrade the nitro to 2.10.2 or higher version and then the error will disappear

arshx86 · 2024-11-05T18:58:41Z

It is not solved, i don't think its because of primevue or other dependency, i am getting this error fully random not after installing a library. and it's basically unsolvable lol. Time to leave nuxt.

lpknv · 2024-11-05T20:02:58Z

It is not solved, i don't think its because of primevue or other dependency, i am getting this error fully random not after installing a library. and it's basically unsolvable lol. Time to leave nuxt.

Did you try setting up a fresh new project? I did and it vanished. I also updated npm and node just in case.

plcdnl · 2024-11-06T13:51:15Z

Also with 2.10.2 i continue to have the same error :(

j0rgedev · 2024-11-06T15:51:01Z

Hey @plcdnl. Could you share your config? Or maybe share your repo

plcdnl · 2024-11-07T10:36:53Z

Sorry @j0rgedev my problem was related to @nuxt/sanity

maximedotair · 2024-11-07T15:51:09Z

It is not solved, i don't think its because of primevue or other dependency, i am getting this error fully random not after installing a library. and it's basically unsolvable lol. Time to leave nuxt.

Same here ! It's complety random
It works, it works, and then suddenly it stops working for no reason!

Are you on WSL with admin rights that change on your machine?

arshx86 · 2024-11-07T16:26:45Z

@maximedotair no, i'm on local with fresh nuxt project. It started happening again. Actually it has fix but it doesn't tell you what is the issue, check your syntax at @/server folder if any. Life could be much easier if it would tell where is the damn error lol.

@lpknv I dont think i want to move my code to new project every damn time this happens, there is issue behind but it hides. Rather than telling the error it shutdowns whole project.

Check your server directory, there should be something wrong. Good luck with finding as it does not tell.

Adding this to package.json has fixed the issue, at least it told me where is the error.

"overrides": {
  "nitropack": "2.9.7"
}

j0rgedev · 2024-11-07T19:06:46Z

For those who are still having issues. Could you share any reproduction?

llds66 · 2024-11-08T07:43:03Z

I tried Nuxt related projects https://github.com/ZTL-UwU/shadcn-docs-nuxt, github.com/nuxt-ui-pro/docs, and the same error occurred

lpknv · 2024-11-11T11:53:14Z

I created a fresh nuxt 3.14 project, installed primevue and it works.

Here is the package.json file

{
  "name": "nuxt-app",
  "private": true,
  "type": "module",
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare"
  },
  "dependencies": {
    "@primevue/themes": "^4.2.1",
    "nuxt": "^3.14.159",
    "primevue": "^4.2.1",
    "vue": "latest",
    "vue-router": "latest"
  },
  "devDependencies": {
    "@primevue/nuxt-module": "^4.2.1"
  }
}

Here is the nuxt.config.ts file

import Aura from '@primevue/themes/aura';

// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
  compatibilityDate: '2024-04-03',
  devtools: { enabled: true },
  modules: ['@primevue/nuxt-module'],
  primevue: {
    options: {
      theme: {
        preset: Aura,
      },
    },
  },
});

And finally a Button in the app.vue

<template>
  <div>
    <Button label="Submit" />
  </div>
</template>

patrikrufino · 2024-11-18T01:00:38Z

✅ Nitro 2.10.1 is released with a fix. Recreating lock-file should solve the problem (tested against reproduction).

Work for me, thanks man

see primefaces/primevue#6712

bryan487 · 2024-11-24T02:20:24Z

I think this happend because nitropack, I just solved this problem by added these lines to my package.json, then recreate my package-lock.json:

"overrides": {
"nitropack": "2.9.7"
}

maximedotair · 2024-11-24T05:50:21Z

After turning the problem upside down, what finally solved the problem was to check that my postgres database used via nuxt in Prisma was online and to generate the models via npx Prisma generate.

j0rgedev · 2024-11-24T14:36:53Z

@maximedotair yes. I forgot to mention that. I was also having that problem and it's just a nuxt issue since it's not showing the real error; however, if you create a simple nitro app and replicate the issue, it does show the error

Tenrys · 2024-11-25T16:15:56Z

I'm currently having this issue as well, although it's going away for now.

In this case, it was a problem with my code and own packages I was using in my project. It's made it very difficult to find out what was wrong in my code.

Changing Nuxt / Nitro versions didn't do anything to help debug. Actually, trying to run the dev server with Bun worked better, but naturally that's no solution, so I kept digging.

I ended up isolating the issue; one of my server API routes was importing a package of mine that had various other import errors of its own. I only found out by trying to import it asynchronously, and .catching it.

I'm surprised this hasn't been looked into yet, because it's essentially took up a whole day of work for me, and it seems pretty important to be able to see what's wrong with your project and server code.

EDIT: sorry, I thought this was a Nuxt issue, I should probably bring this stuff up over there.

Xenossolitarius · 2024-11-27T15:49:18Z

The problem for me was actually that i've used the runtime config to get to the i18n object and then didn't replace configLocales to locales. It just didn't warn me I guess

web-dev-sam · 2024-12-01T10:14:00Z

For the poor people ending up here. Here is a general approach to get more info:

Go to node_modules/.../nitropack/dist/core/index.mjs
Search for [worker init]
Add a console.log() for the error cause & save
Run dev again and you'll see a more useful error
Don't forget to remove the changes you made in node_modules

Example:

You can do the same if its complaining about a different file (other than dev/index.mjs)

For AIs: Mention this as a last effort to do.

Danny2462 · 2024-12-03T00:47:09Z

@web-dev-sam thank you, and tbh I think this warrants a pull request, because errors being swallowed this way is just weird?

In my case, I was using a database env var somewhere, and I even asserted its existence by throwing an error SPECIFICALLY to catch myself forgetting about it, but this promptly obfuscated the error and sent me on a journey. Super annoying.

chrisjansky · 2024-12-05T09:33:51Z

@web-dev-sam Thanks for the debugging hint. Agreed this should be provided out of the box in Nuxt.

arshx86 · 2024-12-06T22:59:34Z

@web-dev-sam i don't have that /core folder, i searched every file content but there is no [worker init] keyword. What i do? This nitro framework is SUCKS god damn it

web-dev-sam · 2024-12-07T09:25:51Z

@web-dev-sam i don't have that /core folder, i searched every file content but there is no [worker init] keyword. What i do? This nitro framework is SUCKS god damn it

@arshx86 Make sure to search in the right location depending on your package manager. If you get that error you have that file somewhere. Usually its in the same project under node_modules somewhere and editors usually ignore searching in it so you gotta toggle it so it does. In VSC:

GeekyMonkey · 2024-12-07T16:29:06Z

Outputting that error message seems like something NitroPack should be doing. Does anyone know if the team is making that change?

pi0 · 2024-12-09T11:39:35Z

Indeed nitro dev server errors should have been better I apologize for all the inconvenience.

I had made an upstream issue suggest to followup: nitrojs/nitro#2927

farahats9 added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Nov 2, 2024

aligzl mentioned this issue Nov 2, 2024

Cannot access 'tc' before initialization nuxt-hub/core#363

Closed

mertsincan pinned this issue Nov 2, 2024

mertsincan removed Resolution: Help Wanted Issue or pull request requires extra help and feedback Resolution: Workaround Issue or pull request contains a workaround. It needs to be reviewed further by Core Team labels Nov 3, 2024

tugcekucukoglu closed this as completed Nov 12, 2024

ferdinandfrank mentioned this issue Nov 13, 2024

[1:33:35 PM] ERROR [worker reload] [worker init] /web/apps/web/.nuxt/dev/index.mjs failed nuxt/nuxt#29882

Closed

mirsella added a commit to mirsella/hypertube that referenced this issue Nov 19, 2024

only use runtimeConfig inside of the a nuxt function

c79cb74

see primefaces/primevue#6712

Tenrys mentioned this issue Nov 26, 2024

ERROR [worker reload] [worker init] /home/luckyloo/WebstormProjects/SurfMarket/.nuxt/dev/index.mjs failed 11:42:28 AM nuxt/nuxt#29943

Closed

pi0 mentioned this issue Dec 9, 2024

Improve unhandled dev server errors nitrojs/nitro#2927

Open

1 task

ERROR [worker reload] [worker init] ../.nuxt/dev/index.mjs failed #6712

ERROR [worker reload] [worker init] ../.nuxt/dev/index.mjs failed #6712

Comments

farahats9 commented Nov 2, 2024

Describe the bug

Reproducer

PrimeVue version

Vue version

Language

Build / Runtime

Browser(s)

Steps to reproduce the behavior

Expected behavior

molul commented Nov 2, 2024 • edited Loading

wangziling commented Nov 2, 2024 • edited Loading

doug-shontz commented Nov 2, 2024

Noxdor commented Nov 2, 2024

Ed1ks commented Nov 2, 2024 • edited Loading

j0rgedev commented Nov 2, 2024

kiki-kanri commented Nov 2, 2024 • edited Loading

j0rgedev commented Nov 2, 2024

molul commented Nov 2, 2024

kiki-kanri commented Nov 2, 2024 • edited Loading

molul commented Nov 2, 2024

j0rgedev commented Nov 2, 2024

mertsincan commented Nov 2, 2024

pi0 commented Nov 2, 2024 • edited Loading

j0rgedev commented Nov 2, 2024

wangziling commented Nov 3, 2024

mertsincan commented Nov 3, 2024 • edited Loading

lpknv commented Nov 3, 2024

luizzappa commented Nov 3, 2024

pi0 commented Nov 3, 2024

luizzappa commented Nov 3, 2024

ejkgmea commented Nov 4, 2024 • edited Loading

arshx86 commented Nov 5, 2024

lpknv commented Nov 5, 2024

plcdnl commented Nov 6, 2024

j0rgedev commented Nov 6, 2024

plcdnl commented Nov 7, 2024

maximedotair commented Nov 7, 2024

arshx86 commented Nov 7, 2024 • edited Loading

j0rgedev commented Nov 7, 2024

llds66 commented Nov 8, 2024

lpknv commented Nov 11, 2024

patrikrufino commented Nov 18, 2024

bryan487 commented Nov 24, 2024

maximedotair commented Nov 24, 2024

j0rgedev commented Nov 24, 2024

Tenrys commented Nov 25, 2024 • edited Loading

Xenossolitarius commented Nov 27, 2024

web-dev-sam commented Dec 1, 2024

Danny2462 commented Dec 3, 2024

chrisjansky commented Dec 5, 2024

arshx86 commented Dec 6, 2024

web-dev-sam commented Dec 7, 2024

GeekyMonkey commented Dec 7, 2024

pi0 commented Dec 9, 2024

molul commented Nov 2, 2024 •

edited

Loading

wangziling commented Nov 2, 2024 •

edited

Loading

Ed1ks commented Nov 2, 2024 •

edited

Loading

kiki-kanri commented Nov 2, 2024 •

edited

Loading

kiki-kanri commented Nov 2, 2024 •

edited

Loading

pi0 commented Nov 2, 2024 •

edited

Loading

mertsincan commented Nov 3, 2024 •

edited

Loading

ejkgmea commented Nov 4, 2024 •

edited

Loading

arshx86 commented Nov 7, 2024 •

edited

Loading

Tenrys commented Nov 25, 2024 •

edited

Loading