-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Storybook fails to resolve yarn Plug N Play, (Babel?) dependencies #20861
Comments
@yannbf could this be an issue with the babel migration in yarn pnp? |
This might a problem:
|
I don't know if this is something you'd have access to @kevzettler : But I got it to generate pnp files.. though it failed to install due to missing prebuilt: log:
|
I tried removing this with
I cannot access this That gl build error...
is probably related to |
Describe the bug
When I run
build-storybook
I am seeing the same error output behavior that is reported here: #18801 (comment)The
build-storybook
hangs indefinitely and fails to terminate or complete.I only see these errors when I use yarns 'plug n' play' mode or 'zero-installs'. If I change the yarn
nodeLinker
value tonodeLinker: node-modules
thenbuild-storybook
works successfully.I tried to follow the advice from #18801 (comment)
and try upgrading with
npx sb@next upgrade --prerelease
However the upgrade process then fails at the babel migration step with error:
furthermore, if I revert and then use execute
npx sb@next upgrade --prerelease
while using yarnsnodeLinker :node-modules
mode. It passes successfully.This leads me to believe in my case there is a module resolution issue possibly with the .babelrc storybook is processing
To Reproduce
I have created a reproduction repository here:
https://github.com/kevzettler/storybook-bug-example
This happens with the following dependencies
Node version v16.13.0
yarn -v
3.3.1
You can execute the following shell command sequence to setup the repo and trigger the failure case
You can then execute
npx sb@next upgrade --prerelease
to see the upgrade failures.Conversely you can edit
.yarnrc.yml
to enablenodeLinker: node-modules
and see the success caseSystem
Additional context
No response
The text was updated successfully, but these errors were encountered: