Fail start-local about adrenaline HOT 2 CLOSED

I am also facing the same issue

from adrenaline.

Same here, on Windows 11. Full log file:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'start-local' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart-local', 'start-local', 'poststart-local' ]
5 info lifecycle [email protected]prestart-local: [email protected]
6 info lifecycle [email protected]start-local: [email protected]
7 verbose lifecycle [email protected]start-local: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]start-local: PATH: C:\Users\secur\AppData\Roaming\nvm\v10.16.3\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\secur\repos\adrenaline\adrenaline\node_modules.bin;C:\Users\secur\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\local\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\secur\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\Eclipse Adoptium\jdk-8.0.345.1-hotspot\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Users\secur.jdks\corretto-1.8.0_342\bin;C:\Gradle\bin;C:\Users\secur\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Program Files\Docker\Docker\resources\bin;C:\Program Files\Amazon\AWSCLIV2;C:\Program Files\Git\cmd;C:\Users\secur\AppData\Local\Microsoft\WindowsApps;C:\Program Files\JetBrains\IntelliJ IDEA 2022.2.1\bin;C:\Users\secur\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\secur\apache-maven-3.8.6\bin;C:\Users\secur\PycharmProjects\re-evaluateClaims\venv\Scripts;C:\Program Files\Git\usr\bin\vendor_perl;C:\Program Files\Git\usr\bin\core_perl
9 verbose lifecycle [email protected]start-local: CWD: C:\Users\secur\repos\adrenaline\adrenaline
10 silly lifecycle [email protected]start-local: Args: [ '/d /s /c', 'react-scripts start' ]
11 silly lifecycle [email protected]start-local: Returned: code: 1 signal: null
12 info lifecycle [email protected]start-local: Failed to exec start-local script
13 verbose stack Error: [email protected] start-local: react-scripts start
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (C:\Users\secur\AppData\Roaming\nvm\v10.16.3\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess. (C:\Users\secur\AppData\Roaming\nvm\v10.16.3\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid [email protected]
15 verbose cwd C:\Users\secur\repos\adrenaline\adrenaline
16 verbose Windows_NT 10.0.22621
17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "start-local"
18 verbose node v10.16.3
19 verbose npm v6.9.0
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start-local: react-scripts start
22 error Exit status 1
23 error Failed at the [email protected] start-local script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

from adrenaline.