-
Notifications
You must be signed in to change notification settings - Fork 16
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
Can't see zeplin tab #55
Comments
I'm facing the same error |
Could you share Storybook version? |
Latest version |
Me, too, same issue |
Hey @joeetr, I couldn't reproduce the bug. Is it possible to share your project? If not, could you please share the following information:
|
This is what i did: |
I'm getting same error, is there an update? |
I had a similar issue today and was able to resolve it by clearing the localStorage cache in Chrome and refreshing |
Are you guys still having this issue? Any chance @mannyblum's solution works for you? |
Hi, i cant see the zeplin tab in storybook.
Getting these warnings:
`WARNING in ./node_modules/@zeplin/storybook-inspector/node_modules/prettier/standalone.js 66:43-50
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
@ ./node_modules/@zeplin/storybook-inspector/dist/index.js 1:20227-20257
@ ./node_modules/storybook-zeplin/dist/register.js 6:0-91 22:33-49 33:54-64 34:80-94
@ ./node_modules/storybook-zeplin/register.js
WARNING in ./node_modules/@zeplin/storybook-inspector/node_modules/prettier/standalone.js 72:46-53
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
@ ./node_modules/@zeplin/storybook-inspector/dist/index.js 1:20227-20257
@ ./node_modules/storybook-zeplin/dist/register.js 6:0-91 22:33-49 33:54-64 34:80-94
@ ./node_modules/storybook-zeplin/register.js
2 warnings have detailed information that is not shown.
Use 'stats.errorDetails: true' resp. '--stats-error-details' to show it.`
using:
node v17.7.1 (npm v8.5.2)
The text was updated successfully, but these errors were encountered: