Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
sb extract alternative to puppeteer
See original GitHub issueI build and “extract” several static storybooks for composition within a docker-based CI/CD environment similar to Drone. The sb extract command leverages puppeteer to extract metadata. Puppeteer’s headless browser is notoriously difficult to configure and use within docker and other virtual linux environments, and is currently blocking us from implementing fully automated storybook builds.
Is there an alternative for the json metadata fetch that sb extract executes that doesn’t require launching a browser? Could a simple GET request be used in puppeteer’s place?
Alternatively, a working docker image to use for the cli step would be incredibly helpful.
I can potentially contribute time for a fix if help with on-boarding and familiarization with the ecosystem is possible.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:15 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@adrianiy, do you want to save it into the storybook-static dir? I’m going to make the extract step a part of the build process. So you be able to do ‘storybook-build’ and get stories.json automatically in the same directory with storybook static. Is it ok for you?
@shilman @rmknecht. I released a new version of Creevey 0.7.26 with the command ‘creevey --extract’. It generates ‘stories.json’ file, and it’s 10x faster than ‘build-storybook && sb extract’.