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
Is your feature request related to a problem? Please describe
I am unifying the cache directory path for our tools and storybook is the last hard-headed one that seemingly cannot be persuaded to use it (as seen in resolve-path-in-sb-cache.ts#L6)
Describe the solution you'd like
Consider introducing some solution for this to be configurable?
You are seemingly using find-cache-dir for some cache path, which should be manipulable by CACHE_DIR env variable, but not in the linked location, which results in node_modules/.cache/storybook/{dev-server,public} being created in my workspace root (I use Yarn's PNP mechanism, so otherwise I do not have node_modules at all)…
Describe alternatives you've considered
No response
Are you able to assist to bring the feature to reality?
kubijo
changed the title
[Feature Request]:
[Feature Request]: Unify the cache locations configurability by using find-cache-dir everywhere
Apr 12, 2023
kubijo
added a commit
to kubijo/storybook
that referenced
this issue
Apr 12, 2023
Is your feature request related to a problem? Please describe
I am unifying the cache directory path for our tools and storybook is the last hard-headed one that seemingly cannot be persuaded to use it (as seen in
resolve-path-in-sb-cache.ts#L6
)Describe the solution you'd like
Consider introducing some solution for this to be configurable?
You are seemingly using
find-cache-dir
for some cache path, which should be manipulable byCACHE_DIR
env variable, but not in the linked location, which results innode_modules/.cache/storybook/{dev-server,public}
being created in my workspace root (I use Yarn's PNP mechanism, so otherwise I do not have node_modules at all)…Describe alternatives you've considered
No response
Are you able to assist to bring the feature to reality?
yes, I can
Additional context
#4665 (comment)
The text was updated successfully, but these errors were encountered: