-
Notifications
You must be signed in to change notification settings - Fork 1
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
4.x - Update Storybook from 6 to 7 #900
Comments
introduction.stories.mdx
with examples on how to get started with 4.x
Started this in #911 during prof dev time. |
Ha. Going to assign and start to pull down and familiarize myself with what is done and where this needs to go. Going to need to do some reading to catch up. @bspeare suggested a huddle to discuss this more in-depth so ping me whenever. I understand there are more priority items going on. |
Finding myself not being of much help on the actual bullet points. It seems from the storybook docs, I spotted the https://storybook.js.org/docs/api/doc-block-useof type and thought maybe we could use it to create a standalone story doc. Should we update to yarn 3 as part of this?
Also, according to vscode, there are issues with our typescript which could be solved if we updated. [email protected] otherwise that workaround for tsconfig.app.json, tsconfig.vite-config.json and tsconfig.vitest.json seems to work. |
Spotted this as a possible path forward for the standalone combined unless we want to stay away from those kinds of stories. https://github.com/massgov/mayflower/blob/develop/packages/core/stories/components/Template/Template.stories.mdx |
And maybe I didn't understand @pyrello earlier, but regarding
and having to deal with different versions per project, I saw here you can control yarn per project using node 18+ corepack https://yarnpkg.com/getting-started/install, https://yarnpkg.com/migration/guide
Going to leave that local for now and see if anything broke while I keep poking around. |
Try |
For the record, I never run this (always ddev blt frontend) so I had to rebuild node-sass or whatever first.
|
Until storybookjs/storybook#13917 has a better solution? We can "hide" the broke code stuff by decorating each story with:
resulting in ![]() |
Done. 53483aa |
Update Storybook from 6 to 7
Proposed Solution
CardDocs.mdx
file as an example.https://github.com/storybookjs/storybook/issues/13917
might be an issue we are havingcomponent-standalone.css
file that contains, fonts, base.css, and component.css - see https://codepen.io/bspeare/pen/poGOjzm as an example.The text was updated successfully, but these errors were encountered: