Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

I am having this problem, whenever I am running yarn dev or npm run dev :

yarn run v1.22.10
warning ../../../../package.json: No license field
$ next dev
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info  - Using webpack 5. Reason: no next.config.js https://nextjs.org/docs/messages/webpack5
event - compiled successfully
event - build page: /
wait  - compiling...
error Command failed with signal "SIGSEGV".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

package.json:

"name": "nextjs", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev", "build": "next build", "start": "next start" "dependencies": { "next": "^10.2.3", "react": "17.x", "react-dom": "17.x", "webpack": "^5.39.1" "devDependencies": { "webpack-cli": "^4.7.2" Certainly, this information is not sufficient to know what went wrong. Please provide a minimal reproducible example. Also, can you verify if this issue is not the same as your problem: github.com/vercel/next.js/issues/24421 – brc-dd Jun 17, 2021 at 14:25 If you are using a mac with M1, the problem can be fixed using node version -> v16.5.0 or above on Mac M1. just use: nvm install v16.5.0 if you are using nvm... – Fernando Nogueira Oct 22, 2021 at 1:00 I'm having this issue trying to run on ARM64 docker with node:current-alpine (which is node 17.4.0 ... still looking for a solution – Filipiz Jan 28, 2022 at 15:31

Appears to be a problem with Mac M1, as @Fernando Gomes commented.

In order to get it working on my environment, I am using Docker with following parameters:

docker buildx build --platform linux/amd64 .
        

Thanks for contributing an answer to Stack Overflow!

  • Please be sure to answer the question. Provide details and share your research!

But avoid

  • Asking for help, clarification, or responding to other answers.
  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.