Skip to content
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

Remove storybook symlink workaround #2152

Merged
merged 1 commit into from
Jul 24, 2021
Merged

Conversation

garrettjstevens
Copy link
Collaborator

It looks like the bug that necessitated this workaround was fixed and released in storybook v6.2.2, and since we've upgraded to a minimum of storybook v6.3.4, this PR removes it.

It also changes the name of the package.json script from build-storybok to build:storybook. The reason is that the executable is called build-storybook, and it's good to avoid having the script name be the same as the executable name. This is because if you want to call the executable with different args than are in the script (e.g. calling it without --quiet), you can no longer use yarn build-storybook to do that because that calls the script instead of the executable.

@garrettjstevens garrettjstevens self-assigned this Jul 23, 2021
@github-actions github-actions bot added the needs label triage Needs a label to show in changelog (breaking, enhancement, bug, documentation, or internal) label Jul 23, 2021
@garrettjstevens garrettjstevens added internal and removed needs label triage Needs a label to show in changelog (breaking, enhancement, bug, documentation, or internal) labels Jul 23, 2021
@cmdcolin cmdcolin merged commit 3c017bf into main Jul 24, 2021
@cmdcolin cmdcolin deleted the remove_storybook_workaround branch July 24, 2021 02:28
@cmdcolin
Copy link
Collaborator

good stuff... this attention to storybook also made me find #2153 earlier today which was an important fix...good catch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants