question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

npm start gives error

See original GitHub issue

Npm start throws error. Project was created with npx create-react-app

FATAL ERROR: WasmCodeManager::Commit: Cannot make pre-reserved region writable Allocation failed - process out of memory

Error log 0 info it worked if it ends with ok 1 verbose cli [ 1 verbose cli ‘/opt/homebrew/Cellar/node/15.2.1/bin/node’, 1 verbose cli ‘/opt/homebrew/bin/npm’, 1 verbose cli ‘start’ 1 verbose cli ] 2 info using npm@6.14.8 3 info using node@v15.2.1 4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ] 5 info lifecycle test@0.1.0~prestart: test@0.1.0 6 info lifecycle test@0.1.0~start: test@0.1.0 7 verbose lifecycle test@0.1.0~start: unsafe-perm in lifecycle true 8 verbose lifecycle test@0.1.0~start: PATH: /opt/homebrew/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/audrius/code/react/fullstackopen/exercises/test/node_modules/.bin:/opt/homebr$ 9 verbose lifecycle test@0.1.0~start: CWD: /Users/audrius/code/react/fullstackopen/exercises/test 10 silly lifecycle test@0.1.0~start: Args: [ ‘-c’, ‘react-scripts start’ ] 11 silly lifecycle test@0.1.0~start: Returned: code: 1 signal: null 12 info lifecycle test@0.1.0~start: Failed to exec start script 13 verbose stack Error: test@0.1.0 start: react-scripts start 13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (/opt/homebrew/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16) 13 verbose stack at EventEmitter.emit (node:events:329:20) 13 verbose stack at ChildProcess.<anonymous> (/opt/homebrew/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack at ChildProcess.emit (node:events:329:20) 13 verbose stack at maybeClose (node:internal/child_process:1055:16) 13 verbose stack at Process.ChildProcess._handle.onexit (node:internal/child_process:288:5) 14 verbose pkgid test@0.1.0 15 verbose cwd /Users/audrius/code/react/fullstackopen/exercises/test 16 verbose Darwin 20.1.0 17 verbose argv “/opt/homebrew/Cellar/node/15.2.1/bin/node” “/opt/homebrew/bin/npm” “start” 18 verbose node v15.2.1 19 verbose npm v6.14.8 20 error code ELIFECYCLE 21 error errno 1 22 error test@0.1.0 start: react-scripts start 22 error Exit status 1 23 error Failed at the test@0.1.0 start script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]

My system: System: OS: macOS 11.0.1 CPU: (8) arm64 Apple processor Binaries: Node: 15.2.1 - /opt/homebrew/bin/node Yarn: Not Found npm: 6.14.8 - /opt/homebrew/bin/npm Browsers: Chrome: Not Found Edge: Not Found Firefox: Not Found Safari: 14.0.1 npmPackages: react: ^17.0.1 => 17.0.1 react-dom: ^17.0.1 => 17.0.1 react-scripts: 4.0.0 => 4.0.0 npmGlobalPackages: create-react-app: Not Found

Issue Analytics

  • State:open
  • Created 3 years ago
  • Reactions:8
  • Comments:23 (2 by maintainers)

github_iconTop GitHub Comments

16reactions
dhyeyshahcommented, Feb 11, 2021

any updates on this?..I am still facing this problem when I do npm start, with node v15.8.0 and big sur 11.2.1 m1 macbook air

16reactions
eugene1gcommented, Nov 19, 2020

Somehow this is caused by react-refresh-webpack-plugin. If I disable it, the app works as expected for me env FAST_REFRESH=false npm start

Read more comments on GitHub >

github_iconTop Results From Across the Web

npm start giving error in node.js - Stack Overflow
The error suggests that the ./bin/www directory is not found. Paths specified with a dot are relative to the current directory, ...
Read more >
How to fix npm start command not working - Nathan Sebhastian
How to fix npm start command not working · Check if the package.json file exists · Check if the start script is defined...
Read more >
npm ERR! Missing script: "start" [Solved] | bobbyhadz
To solve the npm ERR! Missing script: "start" error, make sure to add a start command to the scripts object in your package.json...
Read more >
npm err! missing script: start Solution - Career Karma
If you type npm start and get the npm err! missing script: start error, there must be a missing line in the script...
Read more >
Common errors | npm Docs
Possible temporary npm registry glitch, or corrupted local server cache. Run npm cache clean and/or try again later. · This can be caused...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found