-
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
Infra: update Yarn scripts #579
Conversation
- Remove unnecessary extract-storybook scripts; they are deprecated and breaking the deployed builds. Adding the `storyStoreV7` feature back into the config accomplishes the same task - Visually separate groups of scripts for easier locating - Group the WC and React scripts together - Rename the scripts to more consistent names; **take note of these** - Add `watch:tsc` to the dev scripts so that component file changes reflect immediately in Storybook while developing Also bumped dependencies
|
size-limit report 📦
|
* fix(infra): update Yarn scripts - Remove unnecessary extract-storybook scripts; they are deprecated and breaking the deployed builds. Adding the `storyStoreV7` feature back into the config accomplishes the same task - Visually separate groups of scripts for easier locating - Group the WC and React scripts together - Rename the scripts to more consistent names; **take note of these** - Add `watch:tsc` to the dev scripts so that component file changes reflect immediately in Storybook while developing Also bumped dependencies * chore(infra): refresh yarn.lock * fix(infra): update Chromatic workflow command * fix(infra): update babel plugin name * fix(lint): update TS syntax * Revert "chore(infra): refresh yarn.lock" This reverts commit 4bd67ec. * fix(infra): revert and fix deps and config
This change: (check at least one)
Is this a breaking change? (check one)
Is the: (complete all)
What does this change address?
The Netlify build for the deployed Storybooks is currently failing.
@jialin-he also recently noted that changing component files locally was a chore because Storybook wasn't automatically reflecting those changes and required restarting it each time.
How does this change work?
storyStoreV7
feature back into the config accomplishes the same goal, which is to end up with astories.json
file that can be used in the composed Storybookwatch:tsc
to the dev scripts so that component file changes reflect immediately in Storybook while developingAdditional context
Also bumped Storybook dependencies