[Bug?]: resolving deps
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.1k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
Self-service
- I'd be willing to implement a fix
Describe the bug
Hi i came back with reference of recurrent issue storybook users facing when using Yarn
https://github.com/storybook-vue/storybook-nuxt/issues/48#issue-1862853449
To reproduce
git clone https://github.com/storybook-vue/storybook-nuxt-starter.git
cd storybook-nuxt-starter & yarn storybook dev
Environment
System:
OS: macOS 13.4
CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Binaries:
Node: 18.16.0 - /private/var/folders/kv/y2txhjh11gs29bdg0blspbcr0000gr/T/xfs-4932319b/node
Yarn: 3.5.1 - /private/var/folders/kv/y2txhjh11gs29bdg0blspbcr0000gr/T/xfs-4932319b/yarn
npm: 9.5.1 - /usr/local/bin/npm
pnpm: 8.5.0 - /usr/local/bin/pnpm
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Clone storybook-vue/storybook-nuxt-starter and run yarn storybook dev with the reported Yarn, Node, and pnpm versions. Use the linked storybook-vue/storybook-nuxt issue as context, then trace the dependency-resolution path involved in the failure. Done means the reproduction starts successfully with Yarn and the dependency-resolution regression is covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100