next/image on node 16 give SIGSEGV
Problem
What version of Next.js are you using? 10.1.3 What version of Node.js are you using? 16.0.0 What browser are you using? Chrome, Firefox What operating system are you using? macOS 11.2.3 How are you deploying your application? next dev Describe the Bug Mac Mini M1, Node 16 next start crashes hitting next/images Already nuked node_modules and locks after updating node version [code block] Expected Behavior To work :) To Reproduce Use a simple next/image on a next.js project. Either using js or TS does not change the behavior
Error Output
error Command failed with signal "SIGSEGV".
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: next/image on node 16 give SIGSEGV
I'm experiencing this problem too. Just tested in a fresh installed macOS and a simple Next JS project. It crashes using either Node LTS or 16.0.0. My dev script works fine until you scroll into view any next/image component, so maybe the bug its related with the lazy loading? I can confirm it only happens in my dev environment, pushing to production works completely fine for me. I'm using a MacB
Trust Score
5 verifications
- 1
I'm experiencing this problem too. Just tested in a fresh installed macOS and a
I'm experiencing this problem too. Just tested in a fresh installed macOS and a simple Next JS project. It crashes using either Node LTS or 16.0.0. My dev script works fine until you scroll into view any next/image component, so maybe the bug its related with the lazy loading?
- 2
I can confirm it only happens in my dev environment, pushing to production works
I can confirm it only happens in my dev environment, pushing to production works completely fine for me. I'm using a MacBook Air M1 and deploying to Vercel, if that helps.
Validation
Resolved in vercel/next.js GitHub issue #24421. Community reactions: 9 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep