Segementation Fault when @nuxt/image is installed in project?

[rabbitfufu]

I have been @nuxt/image (0.6.2) with nuxt on node 14 for a long time with great results.

I have not made any changes to my development environment recently.

However, starting today, when I run 'npx nuxt', my project seems to compile fine, but as soon as I navigate to localhost, nuxt exits with a segmentation fault.

ℹ Waiting for file changes 11:44:12 ℹ Memory usage: 389 MB (RSS: 537 MB) 11:44:12 ℹ Listening on: http://localhost:3000/ 11:44:12 zsh: segmentation fault npx nuxt

After some experimentation, I have discovered that removing @nuxt/image from the project fixes this problem. So that is somehow related.

I have already tried deleting the entire node_modules folder and running npm install again -- however the problem recurs.

I am not sure how to go about troubleshooting this from here. Has anyone else encountered this?

[rabbitfufu]

Okay, so it looks like downgrading to 0.5 of @nuxt/image fixed the issue for me. Would still be good to have some insight into this if anyone has an idea.

[Amar1432]

any updates on this issue??

[jeanmatthieud]

Same issue going from [email protected] to [email protected]; I didn't try 0.6.1

I'm using internal IPX.

[pi0]

Please try upgrading to the latest Node.js LTS 16 and recreate the lockfile. It is most likely an upstream issue. If you still have it, please report your operating system, Node.js version, version of ipx from node_modules/ipx/package.json and version of sharp from node_modules/sharp/package.json 🙏🏼

[stuible]

I am also running into this issue on Node 14. I am not able to upgrade to 16 at this time because doing so appears to break sass compatibility.