-
Notifications
You must be signed in to change notification settings - Fork 106
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
Support features.storyStoreV7
#126
Conversation
ef0c5f5
to
e46de50
Compare
@tmeasday Any thoughts on the current list of issues? I'm not that familiar with how storybook works but from what I can tell the useEffect in preview.tsx sets the storyId to undefined here for some reason on initial load when there wasn't a defined path: |
Hey @joshwooding -- if you let me know how to run it I can take a look? It isn't entirely clear what the issues mean. Have you looked at what events are being emitted from the preview side? I'm not sure but I think that code would only emit any empty story id if the preview somehow told it to. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple comments scanning through
packages/storybook-builder-vite/codegen-modern-iframe-script.js
Outdated
Show resolved
Hide resolved
@tmeasday
|
a22dfaf
to
fd06954
Compare
After some investigation FEATURES in the stories.ts file isn't being updated. |
@tmeasday I'm seeing some weird stuff. Not sure if it's due to the yarn setup or something else but when installing node_modules from scratch I get a prebuilt manager which does not get changed and is stuck with the features config set to |
Hi @joshwooding, thanks for your work on this. Is there more you're planning to do, or is it ready to review? If so, is there anything we should be aware of as we do? |
@IanVS I think there are some few kinks to iron out. Currently the current issues are:
|
9a28bd6
to
6ecb5bf
Compare
We usually add any third-party dependencies from package.json to the |
@eirslett The 408 requests include third-party dependencies sadly :( |
b83c5ee
to
71df6f8
Compare
The only issue I can see now is that the static storybook sets an empty path? |
This is an issue with |
Thanks for sticking with this one, @joshwooding! I'll give it some 👀 as soon as I can. In the meantime, it would be great if anyone else would be willing to try it out and play around with it, especially those using svelte or vue or other frameworks than React, which is what I'll be testing out. |
Hmm, I can't get svelte to work in the repo. Two instances of ClientApi seem to exist for some reason. |
.svelte story files no longer work due to https://github.com/storybookjs/storybook/blob/next/lib/core-server/src/utils/StoryIndexGenerator.ts#L68 cc @tmeasday I assume this is intentional storybookjs/storybook#16673 an issue has been raised to track this. |
Hmm, yes I guess we will need to think about that @shilman |
71df6f8
to
d146303
Compare
d146303
to
2ac8ece
Compare
I think this and the svelte duplicate ClientAPIs are the only issues left :) I think the duplicate ClientAPIs are due to |
74aa943
to
31746ed
Compare
c2efc06
to
426a654
Compare
I pulled down the branch and am experimenting with it now. I'm seeing a few things so far, still investigating:
So, it seems like we should add After I added OK, found a solution for those warnings: vitejs/vite#5438 (comment). I'll throw up a PR. |
It's so cool to see the new components get fetched only when you view their stories. This should help folks with large storybooks a ton! What do you think about merging this and in our release notes mentioning that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you're willing to add @storybook/channel-websocket
to the list of optimized dependencies and uncomment out the accessibility plugin in the examples, I'll give this my 👍. Great work here, thanks again for sticking with it.
In Vite I would assume they are only getting compiled when requested too, which I assume should help larger storybooks a lot! |
Compiling is really fast in vite, but one of the bottlenecks has been sending all the (sometimes hundreds of) files to the browser at startup. So for both reasons, this is a big step in the right direction! |
426a654
to
01dbbd5
Compare
Sounds great. I've added comments and updated optimizeDeps :) |
Oh shoot, I've caused a merge conflict in the lockfile. Would you mind rebasing one more time? |
01dbbd5
to
c648994
Compare
@IanVS Done :) |
Closes #125