I'm trying react-native here, and following the instructions here I installed the standalone app (since it doesn't seem to work inside chromium browser).
I had no problem or whatsoever during install but the when I try to run it it simply doesn't start... no errors no nothing, so I think I might need some help here.
this is the log for the sake of it...
~
âž” react-devtools
~
âž”
The only error I could manage to opbtain was when following the instruction to use react-devtools not globally but inside my project with npm run react-devtools, and here is the log:
~
âž” npm run react-devtools
> [email protected] react-devtools /home/nature/junk/reactNativeTest
> react-devtools
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] react-devtools: `react-devtools`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] react-devtools script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/nature/.npm/_logs/2018-08-09T13_04_49_554Z-debug.log
Maybe I should also mention that I'm using the method with adb over network.
Thanks !
nbonfils
All 19 comments
I think I have something similar.
Installed as per the docs and, as above, "I had no problem or whatsoever during install but the when I try to run it it simply doesn't start... no errors no nothing" and I also was able to obtain an error when running it through an NPM script (I have tried installing locally via --save-dev as well as globally but the result is the same - it doesn't run at all.)
I am running Ubuntu 18.04.1 LTS and react-devtools 3.2.3.
Here is the error log:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'devtools' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'predevtools', 'devtools', 'postdevtools' ]
5 info lifecycle [email protected]~predevtools: [email protected]
6 silly lifecycle [email protected]~predevtools: no script for predevtools, continuing
7 info lifecycle [email protected]~devtools: [email protected]
8 verbose lifecycle [email protected]~devtools: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~devtools: PATH: /usr/share/npm/bin/node-gyp-bin:/home/alex/projects/q-app/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin:/home/alex/Android/Sdk/tools:/home/alex/Android/Sdk/tools/bin:/home/alex/Android/Sdk/platform-tools:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin:/home/alex/Android/Sdk/tools:/home/alex/Android/Sdk/tools/bin:/home/alex/Android/Sdk/platform-tools
10 verbose lifecycle [email protected]~devtools: CWD: /home/alex/projects/q-app
11 silly lifecycle [email protected]~devtools: Args: [ '-c', 'react-devtools' ]
12 info lifecycle [email protected]~devtools: Failed to exec devtools script
13 verbose stack Error: [email protected] devtools: react-devtools
13 verbose stack spawn ENOENT
13 verbose stack at ChildProcess.
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:925:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid [email protected]
15 verbose cwd /home/alex/projects/q-app
16 error Linux 4.15.0-30-generic
17 error argv "/usr/bin/node" "/usr/bin/npm" "run" "devtools"
18 error node v8.10.0
19 error npm v3.5.2
20 error file sh
21 error code ELIFECYCLE
22 error errno ENOENT
23 error syscall spawn
24 error [email protected] devtools: react-devtools
24 error spawn ENOENT
25 error Failed at the [email protected] devtools script 'react-devtools'.
25 error Make sure you have the latest version of node.js and npm installed.
25 error If you do, this is most likely a problem with the qapp package,
25 error not with npm itself.
25 error Tell the author that this fails on your system:
25 error react-devtools
25 error You can get information on how to open an issue for this project with:
25 error npm bugs qapp
25 error Or if that isn't available, you can get their info via:
25 error npm owner ls qapp
25 error There is likely additional logging output above.
26 verbose exit [ 1, true ]
AlexJeffcott
on 15 Aug 2018
I have the same problem. Has anyone solved this problem?
agustinch
on 28 Feb 2019
Same problem here. I tried to run react-devtools from my project folder (even if it shouldn't be necessary) but it simply won't start, returning the terminal control to the user. No errors, warnings, nothing. Didn't find a workaround or a fix yet.
I'm using Windows 10 but all my projects have been created on the Linux Subsystem that comes with it. Therefore I installed react-devtools in the Subsystem. react and react-native are installed on the subsystem as well.
ghost
on 5 Mar 2019
I have the same problem to run devtools with react native windows. All setup are run on Windows 10. I installed react-devtools but chrome devtools is not enabled
devdanoliveira
on 7 Mar 2019
I have the same problem.I'm looking for solution
thought7878
on 18 Mar 2019
you can use this React Native Debugger ,intead of react-devtools
thought7878
on 18 Mar 2019
I'm having the same problem
melvsparks
on 23 Apr 2019
Same problem - seems like there's no solution yet?
StartupSam
on 1 May 2019
you can use this React Native Debugger ,intead of react-devtools
I tried using this, but it seems to have the same problem of refusing to start (with no error messages).
StartupSam
on 1 May 2019
I also tried the full npm cache clean, delete packages etc. just in case, but the issue persists. :'(
StartupSam
on 1 May 2019
For those who come come later: A solution on this thread worked for me: https://github.com/facebook/react-devtools/issues/1097
StartupSam
on 1 May 2019
This solved my issue
sudo apt install libgconf-2-4
saeedeyvazy
on 3 May 2019
I am facing the same issue, yesterday it was running fine and open. But today, it is silently close, with no warning or error.
When I try to install it locally, and run it with node .\node_modules\react-devtools\bin.js I get this error:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Users\\Me\\AppData\\Local\\nvs\\default\\node.exe',
1 verbose cli 'C:\\Users\\Me\\AppData\\Local\\nvs\\default\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'tools' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'pretools', 'tools', 'posttools' ]
5 info lifecycle @~pretools: @
6 info lifecycle @~tools: @
7 verbose lifecycle @~tools: unsafe-perm in lifecycle true
8 verbose lifecycle @~tools: PATH: Removed
9 verbose lifecycle @~tools: CWD: C:\Users\Me\code\react-native-sample
10 silly lifecycle @~tools: Args: [ '/d /s /c', 'node ./node_modules/react-devtools/bin.js' ]
11 silly lifecycle @~tools: Returned: code: 1 signal: null
12 info lifecycle @~tools: Failed to exec tools script
13 verbose stack Error: @ tools: `node ./node_modules/react-devtools/bin.js`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Users\Me\AppData\Local\nvs\node\8.15.1\x64\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\Me\AppData\Local\nvs\node\8.15.1\x64\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:915:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid @
15 verbose cwd C:\Users\Me\code\react-native-sample
16 verbose Windows_NT 10.0.17763
17 verbose argv "C:\\Users\\Me\\AppData\\Local\\nvs\\default\\node.exe" "C:\\Users\\Me\\AppData\\Local\\nvs\\default\\node_modules\\npm\\bin\\npm-cli.js" "run" "tools"
18 verbose node v8.15.1
19 verbose npm v6.9.0
20 error code ELIFECYCLE
21 error errno 1
22 error @ tools: `node ./node_modules/react-devtools/bin.js`
22 error Exit status 1
23 error Failed at the @ tools script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Node version: v8.15.1
NPM version: 6.9.0
react-devtools version: 3.6.1
Operating System: Windows 10
apiep
on 10 May 2019
@saeedeyvazy Thank you so much dude, this one solved my issue.
michaellee8
on 20 May 2019
Any update on this? I still am unable to use the React-devtools stand alone app on Windows 10 with React Native. It just sits there and hangs, nothing opens up.
No errors when ran:
- From the project with
npm run react-devtools - From outside the project with
react-devtools
melvsparks
on 7 Jun 2019
@saeedeyvazy Thank you so much dude, this one solved my issue.
I'm so happy!
saeedeyvazy
on 9 Jun 2019
Facing the same issue. Windows 10. Please halp.
akshayjain90
on 23 Jun 2019
I installed react devtools again (version 3.6.1) using npm i -g react-devtools and it's now working
melvsparks
on 2 Jul 2019
React DevTools has been rewritten and recently launched a new version 4 UI. The source code for this rewrite was done in a separate repository and now lives in the main React repo (github.com/facebook/react).
Because version 4 was a total rewrite, and all issues in this repository are related to the old version 3 of the extension, I am closing all issues in this repository. If you can still reproduce this issue, or believe this feature request is still relevant, please open a new issue in the React repo: https://github.com/facebook/react/issues/new?labels=Component:%20Developer%20Tools
bvaughn
on 20 Aug 2019
Related issues
CodyReichert
·
5Comments
levani
·
4Comments
sophiebits
·
5Comments
keyz
·
5Comments
mmahalwy
·
3Comments
Most helpful comment
This solved my issue
sudo apt install libgconf-2-4