Error spawn cmd ENOENT
See original GitHub issueAfter run Storybook, I see an error
To Reproduce
Steps to reproduce the behavior:
1- Run command start-storybook -p 6006
2- See an error
Screenshots
Code snippets
import { configure } from '@storybook/react';
import { initializeRTL } from 'storybook-addon-rtl';
initializeRTL();
// automatically import all files ending in *.stories.js
const req = require.context('../src', true, /\.stories\.js$/);
function loadStories() {
req.keys().forEach(filename => req(filename));
}
configure(loadStories, module);
System:
- OS: Windows10
- Device: PC
- Browser: Chrome
- Framework: react (create-react-app)
- Addons: [@storybook/addon-knobs, @storybook/addon-notes/, storybook-addon-rtl]
- Version: 5.1.9
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
node.js - Get 'spawn cmd ENOENT' when try to build Cordova ...
I checked system variables one more time and found the cause of the problem: missing C:\Windows\System32\ variable. I added it and that solved...
Read more >Error: spawn cmd ENOENT in VS code · Issue #1818 - GitHub
Hi, I am getting following error while running command- SFDX: Authorize an Org in VS Code: Error: spawn cmd ENOENT at Process.ChildProcess.
Read more >[Solved-5 Solutions] Error spawn enoent on node.js - Wikitechy
Spawn may emit the ENOENT error if the filename command (i.e, 'some-command') does not exist in at least one of the directories defined...
Read more >Problem with npm start (error : spawn cmd ENOENT)-Reactjs
[Solved]-Problem with npm start (error : spawn cmd ENOENT)-Reactjs · Go to search bar and write environment variables. · Under the Advanced section...
Read more >Error when Authenticate Orgs - Salesforce Stack Exchange
Run command prompt as admin (Start > cmd > Right-Click > RunAs Admin) · Run the command: netstat - ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Double bump, what’s going on with this? Tried multiple things to resolve with no conclusion.
UPDATE: After further digging (and pure luck), I was able to determine that this issue was due to a default browser not being specified.
It should work if you run
BROWSER=none npm run storybook
Hope this helps someone else!
@snyderhaus Thank you! That worked for me. Is there any way to specify a default browser? like a storybook or webpack env file?