storybook-vue / storybook-nuxt

Deprecated in favor of https://github.com/nuxt-modules/storybook/
https://github.com/nuxt-modules/storybook/
132 stars 20 forks source link

Unable to start a new storybook nuxt project on windows #88

Closed gab9281 closed 9 months ago

gab9281 commented 9 months ago

node version : 20.11.0 yarn version : 1.22.21 windows version : 23H2 (22631.3085)

Step to reproduce :

Result :

node:events:496
      throw er; // Unhandled 'error' event
      ^

Error: spawn yarn ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ChildProcess instance at:
    at ChildProcess._handle.onexit (node:internal/child_process:292:12)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn yarn',
  path: 'yarn',
  spawnargs: [ 'install' ]
}

Try to identify the situation :

Result : same error

node:events:496
      throw er; // Unhandled 'error' event
      ^

Error: spawn yarn ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ChildProcess instance at:
    at ChildProcess._handle.onexit (node:internal/child_process:292:12)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn yarn',
  path: 'yarn',
  spawnargs: [ 'install' ]
}

2nd resolution try (with deps of 1st try) :

I've been working a full day on this previously @ job (4 days ago) and had a esbuild-arm@npm20.0.0 error at theses steps. I am still posting this due to being helpfull for those stuck @ step1 but i'm confused.

For thoses that were wondering : Trying a clean state with yarn 4.1.0 does not fix the issue

gab9281 commented 9 months ago

Wrong repo, sorry