create-react-app: npm start gives error
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
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 8
- Comments: 24 (2 by maintainers)
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
Somehow this is caused by
react-refresh-webpack-plugin
. If I disable it, the app works as expected for meenv FAST_REFRESH=false npm start
Hi - as far as I understand this error is only happening on Apple Silicon M1 based devices.
This mostly is not use but rather upstream - some packages in the HMR hot path (like
source-map
(source map generation) andchokidar
(file watching)) depends on WASM or native capabilities, which with Node.js not even having proper support for the platform, is bound to fail.You could try to lower the actual amount of memory Node.js would try to allocate to potentially evade the issue (ref: pmmmwh/react-refresh-webpack-plugin#259)
Is this on Apple silicon?
This has been released today in Node 15.3.0. Can confirm that the error has disappeared for me after the update.
I have the same problem.
Environment
brew install node
)Logs
node v12.21.0 react-scripts 4.0.3 Big Sur 11.2.3 M1 chip
I know node v12 is not the newest, yet I use it with other things, while some aws lambda integrations still require v12 even lambda itself supports v14 but this is all out of scope of this thread.
any hope to have this fixed for node v12 and v14 while both are in LTS. I can confirm it works with node v15, but not with v14 or v12.
https://nodejs.org/en/about/releases/
@pmmmwh is correct - the issue is way upstream from CRA or react-refresh, and it has been fixed in Node at https://github.com/nodejs/node/commit/c1442ec9c45cecf156fb32ad2174c4aceef37de7 (I confirmed by compiling from that commit and it works as expected). That commit is not yet included in any released versions, but Node folks are hard at making a stable Apple Silicon version for us, so we’ll just wait.
(root㉿kali)-[~/AhMyth-Android-RAT/AhMyth-Server] └─# npm start
[1212/174734.032768:FATAL:electron_main_delegate.cc(300)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180. /root/AhMyth-Android-RAT/AhMyth-Server/node_modules/electron-nightly/dist/electron exited with signal SIGTRAP
note"" I use kali linux on vertual box and windows 10 sandbox and hyper v was activated any solutions jdk version 17.0.5 node version 18.12.1 npm vrsion 9.1.2
@Harshadcse You are using Node
v14
- the easiest way to make this work is to upgrade to a current releasev16
.@MasatoshiTada This might be related https://github.com/nodejs/node/issues/37061