Thread <unnamed> panicked

[fabianwohlfart]

Hi guys,

Yesterday I ran into a problem on our production server.
When using Vite (through Nuxt) and building my application I get this Rust error.

The guys from server administration can not explain it, but say it has to do with Rollup (which is used by VIte) and I am not dev ops enough to understand this.
Maybe one of you has an idea what is going on and how we can fix it? – Or what we can try to work around it?

Error in all Versions of Vite (tested 4.3.9 onwards)

thread '<unnamed>' panicked at /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/stacker-0.1.15/src/lib.rs:416:13:
assertion `left == right` failed
  left: 2
 right: 0
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5

[villamarianne]

Hi,

I'm facing the exact same issue.

I just started modernizing my workflow, so I don't know much about bundlers and stuff, but I found out, that if I do not import bootstrap javascript, it works as expected.

As you are from Germany, is it possible that youre server is hosted by Mittwald like mine?

[fabianwohlfart]

Yes it is Mittwald!
What is happening there? Never had any problems with other hosts.
What do you mean by »not import bootstrap javascript«?

[StrahinjaG]

If anyone else is searching for a solution, I refer to this thread: rollup/rollup#5304. After a fresh installation of Laravel Breeze with Inertia, I encountered the same error message at Mittwald. I added

"resolutions": { "rollup": "npm:@rollup/wasm-node" }

to the end of my package.json and ran yarn install. After that, npm run build worked. I hope this helps someone.

[fabianwohlfart]

Yes, I can confirm, this is working on Mittwald.

[villamarianne]

Thanks @StrahinjaG, that works perfect.

If you are using npm, you have to use a slightly different solution.
Thanks to @morpheus-87 at rollup/rollup#5194 (comment)

"overrides": {
    "vite": {
        "rollup": "npm:@rollup/wasm-node"
    }
}

I also had to remove package-lock.json, node_modules and run npm install again.

[timokleemann]

I can also confirm that this works at the German web host All-Inkl.

[whydesign]

Also worked for me with All-Inkl. thanks!

[Ulrich-Mbouna]

Same issue here after setting overides in package.json