Error: Cannot find module 'react-is' - Production build

What version of Next.js are you using?

12.0.2

What version of Node.js are you using?

16.13.0

What browser are you using?

Chrome

What operating system are you using?

macOS, M1

How are you deploying your application?

next start

Describe the Bug

next dev is working as expected. When I run next build followed by next run and visit the URL, I get the following error in the console and a large part of the application renders blank.

Expected Behavior

It probably shouldn’t throw this error, unless I’m missing something in my setup.

To Reproduce

There isn’t much more context I can give, I think. I’m not sure if it helps to get my entire package.json but I will of course post it if someone needs it for debugging.

[neodon]

In case anyone is interested, here is a docker-compose.yml file that reproduces the issue:

version: '3'

services:
  app:
    image: node:16-slim
    ports:
      - '8080:8080/tcp'
    environment:
      NODE_ENV: $NODE_ENV
    command: >-
      bash -c '
        npx create-next-app@latest app --use-npm --with-static-export
        cd app

        # Static export does not work out of the box due to the Image component
        grep -v Image pages/index.js >pages/index.js2 && mv pages/index.js2 pages/index.js

        npx next build
        npx next export

        npx http-server --proxy http://localhost:8080/index.html? out
      '

Drop that in a directory by itself, then run docker-compose up. Open http://127.0.0.1:8080 in your browser and check the console logs after a refresh. There should be no errors.

Hit CTRL+C to stop the container. Next, run NODE_ENV=development docker-compose up. Reloading the page should now show the error in the console.

It would be great if next export could detect this problem and warn the user. It would save a lot of time and frustration tracking this down.

[calbrecht]

Happened to me as well 😂

Make sure NODE_ENV=production while next build instead of NODE_ENV=development.