Storybook: Error spawn cmd ENOENT

Created on 11 Jul 2019  路  5Comments  路  Source: storybookjs/storybook

After 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
image

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
cli core inactive question / support

Most helpful comment

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!

All 5 comments

Automention: Hey @Keraito, you've been tagged! Can you give a hand here?

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook!

bump on this one

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!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

levithomason picture levithomason  路  3Comments

arunoda picture arunoda  路  3Comments

miljan-aleksic picture miljan-aleksic  路  3Comments

shilman picture shilman  路  3Comments

purplecones picture purplecones  路  3Comments