'yarn storybook' creates node_modules/.cache in Yarn 2 PnP project

[turtle601]

Describe the bug

My project is using Yarn 2 PnP and consequently there exists no node_modules folder.

After I installed StoryBook with yarn version

yarn workspace @package/ui dlx storybook init

then run storybook

yarn workspace @package/ui storybook

them node_modules will be created.

Storybook had the same issue 3 years ago.

I am still curious whether the node_modules library is still unconditionally required to use storybook,

or if there is a way to run it in pnp mode without creating node_modules.

[valentinpalkovic]

For convenience reasons, Storybook's cache directory is located in the node_modules folder, since it is normally not checked in via version control. I understand, that in yarn PnP mode this folder doesn't exist. When Storybook creates a node_modules/.cache folder, do you encounter any side effects? Does it have a negative impact in yarn pnp mode when the node_modules folder is created or is it just nasty to have it in place, although it isn't required?

[turtle601]

👋 Thank you for answering 👋

We suprised that it is nasty to have it in place, but storybook ran smoothly.
(I haven't found any other problems yet.)

This may be a very surprising situation for users who are using Storybook and yarn berry pnp mode for the first time.

I felt that the command in the photo above especially supports yarn pnp mode. It would be good to mention in the official document that pnp mode is supported, but the node_modules created there are essential.

[valentinpalkovic]

That's a good point. I will mention @jonniebigodes here to bring it onto his radar and to adjust the docs.

Thank you for reaching out!

[turtle601]

@valentinpalkovic
I wrote a message explaining that node_modules are created when running storybook in pnp mode.

Please give me a feedback for message about PR 👍

Issue link
PR link