Storybook setup is broken
See original GitHub issueDescribe the bug A storybook tool fails to run.
To Reproduce Steps to reproduce the behavior:
- clone project
- run ‘npm run storybook’
- you will see following error at terminal
Desktop (please complete the following information):
- OS: windows, Ubuntu
- Browser: [e.g. chrome, safari]
- Version: [e.g. 22]
Additional context
Possible solution:
comment out line 99 of tools/ui-components/tailwind.config.js
file:
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Broken build with updated Storybook (5.3) Configuration
Broken build with updated Storybook (5.3) Configuration. Hello, I am having issues publishing to my DSM after making the changes listed here ...
Read more >Configure Storybook
Storybook is configured via a folder called .storybook , which contains various configuration files. Note that you can change the folder that Storybook...
Read more >Webpack - Storybook
Storybook displays your components in a custom web application built using Webpack. Webpack is a complex tool, but our default configuration is intended...
Read more >Test runner Addon | Storybook: Frontend workshop for UI ...
Zero config setup; Smoke test all stories; ▶️ Test stories with play ... NOTE: These test hooks are experimental and may be subject...
Read more >Building pages with Storybook - JS.ORG
See https://storybook.js.org/docs/react/configure/overview#configure-story-loading * to learn how to generate automatic titles */ title: 'DocumentScreen', ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hmm that commented line is needed in order to have a correct styling. I’m not sure what’s gone wrong there but I can take a look.
Oh thanks @shootermv! That’s what I actually did in my fix. I tested the change and the styling is correct 😁