You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
** Disclaimer** This information might be inaccurate, due to it being generated automatically
This behavior is controlled in code/lib/cli/src/detect.ts. To prevent Storybook from adding the packageManager field: 1. Add STORYBOOK_DISABLE_PACKAGE_MANAGER_DETECTION=true to your environment variables The incorrect detection likely occurs in the getPackageManager() function in detect.ts which checks for lockfiles in this order: - yarn.lock - pnpm-lock.yaml - package-lock.json This means if both yarn.lock and package-lock.json exist, yarn will be incorrectly detected. You can either: 1. Delete any yarn.lock file if not using yarn 2. Set the environment variable above to disable detection entirely
About Greptile
This response provides a starting point for your research, not a precise solution.
Help us improve! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
Describe the bug
Partial duplicate of #29146 – that issue relates to PNPM
Storybook alters the project's package.json adding a packageManager entry that is
A) Undesired – how to disable this invasive behavior?
B) Incorrect – it sets it to Yarn even though the project uses NPM, not Yarn
Reproduction link
None
Reproduction steps
No response
System
Additional context
No response
The text was updated successfully, but these errors were encountered: