Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can't spawn the start-storybook process

See original GitHub issue

Hi,

I have come accross this issue where I am unable to use the serverCmd flag to start a storybook. Please see the outout below:

> storycap --serverCmd "start-storybook -p 9001" http://localhost:9001/

info Wait for connecting storybook server http://localhost:9001/.
events.js:187
      throw er; // Unhandled 'error' event
      ^

Error: spawn start-storybook ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
    at onErrorNT (internal/child_process.js:456:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
    at onErrorNT (internal/child_process.js:456:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: 'ENOENT',
  code: 'ENOENT',
  syscall: 'spawn start-storybook',
  path: 'start-storybook',
  spawnargs: [ '-p', '9001' ]
}

Let me know if you need more info. Thank you 😄

Issue Analytics

State:
Created 4 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

UsamaHameedcommented, Feb 20, 2020

Let me know if I can help with this if you think it would make a good first OSS issue.

0reactions

Quramycommented, Feb 25, 2020

@UsamaHameed Sorry for my late reply. I published v2.3.5 with #143 . I think this issue was caused by missing cp spawning option { shell: true } and I confirmed it fixed via GitHub action’s windows-server env.