react-scripts build freezes at "Creating optimized build"

Question

I have upgraded my CRA project to use react-scripts 3.2.0 When I run npm run build I get the "Creating an optimized production build..." message, but then nothing happens, its just stuck forever.

Environment:

node: v12.13.1

npm: 6.12.1

Project details:

typescript, scss and scss modules

package.json

    "dependencies": {
        "@types/jest": "^24.0.11",
        "@types/node": "^11.13.4",
        "@types/react": "^16.8.13",
        "@types/react-dom": "16.8.4",
        "classnames": "^2.2.5",
        "mobx": "^3.6.2",
        "mobx-react": "^4.4.3",
        "node-sass": "^4.12.0",
        "react": "^16.8.6",
        "react-scripts": "^3.2.0",
    },
    "devDependencies": {
        "@typescript-eslint/eslint-plugin": "^2.6.1",
        "@typescript-eslint/parser": "^2.6.1",
        "babel-plugin-transform-decorators-legacy": "^1.3.4",
        "enzyme": "^3.7.0",
        "enzyme-adapter-react-16": "^1.6.0",
        "husky": "^3.0.9",
        "lint-staged": "^9.4.2",
        "prettier": "^1.19.1",
        "typescript": "^3.2.4"
    },

tsconfig.json

{
    "compilerOptions": {
        "outDir": "build/dist",
        "module": "esnext",
        "target": "es5",
        "lib": ["es2016", "dom"],
        "sourceMap": true,
        "allowJs": true,
        "jsx": "preserve",
        "moduleResolution": "node",
        "rootDir": "src",
        "forceConsistentCasingInFileNames": true,
        "noImplicitReturns": true,
        "noImplicitThis": false,
        "noImplicitAny": false,
        "strictNullChecks": false,
        "suppressImplicitAnyIndexErrors": true,
        "noUnusedLocals": false,
        "experimentalDecorators": true,
        "skipLibCheck": true,
        "esModuleInterop": true,
        "allowSyntheticDefaultImports": true,
        "strict": true,
        "resolveJsonModule": true,
        "isolatedModules": true,
        "noEmit": true
    },
    "include": ["src"],
    "types": ["react"]
}

Did you ever figure this out?

CustardBun
– CustardBun

2020-02-14 17:56:12 +00:00
Commented Feb 14, 2020 at 17:56 — CustardBun
– CustardBun, Commented Feb 14, 2020 at 17:56

Surya Mahla · Accepted Answer · 2020-05-12 06:05:11Z

8

This is most probably because of shortage of RAM. Build command requires much more RAM than you'd expect.

answered May 12, 2020 at 6:05

Surya Mahla

5136 silver badges24 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

Alan Yong Over a year ago

we looking for answer but u just talk about RAM

ReNiSh AR Over a year ago

Thanks instance upgraded (ram increased) now working fine...

Surya Mahla Over a year ago

@AlanYong , the answer is to increase your system's RAM :)

llamerr Over a year ago

I see lots of answers adding suggestions like this, but what it's based on? I added -- --verbose to command line, it added a couple of lines of info, but still stuck on Creating an optimized production build.... How can I make it to be verbose instead of being stuck?

Ezra Over a year ago

This is the right answer. I am using Colima as the docker engine on MacBook Pro. Increasing cpu/mem allocation fixed it. stackoverflow.com/questions/70271194/…

Collectives™ on Stack Overflow

react-scripts build freezes at "Creating optimized build"

1 Answer 1

5 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

5 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related