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
Getting started docs indicate that we should use node@16 to work on the Storybook code. I use Volta to manage node versions but it does not work well with Node's corepack feature. Corepack uses the "packageManager" property in the package.json file to determine which manager and version to use but volta uses its own values and is not aware of "packageManager" setting. The Volta team are aware and our looking into ways to resolve volta-cli/volta#987 and volta-cli/volta#282.
In the meantime a workaround is to duplicate the settings:
If the community agrees I would like to propose that we add Volta pinning to the package.json. It has no effect if you don't use Volta but I understand it might not be for everyone. I'll raise a PR and see.
Describe the bug
Getting started docs indicate that we should use
node@16
to work on the Storybook code. I use Volta to manage node versions but it does not work well with Node's corepack feature. Corepack uses the"packageManager"
property in the package.json file to determine which manager and version to use but volta uses its own values and is not aware of"packageManager"
setting. The Volta team are aware and our looking into ways to resolve volta-cli/volta#987 and volta-cli/volta#282.In the meantime a workaround is to duplicate the settings:
If the community agrees I would like to propose that we add Volta pinning to the package.json. It has no effect if you don't use Volta but I understand it might not be for everyone. I'll raise a PR and see.
To Reproduce
git clone
the fork andcd
into the projectvolta pin node@16
yarn start
A bleeding edge RC version of yarn 4 is installed and build fails.
System
Additional context
No response
The text was updated successfully, but these errors were encountered: