-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Core: Merge channels into a single package #23032
Conversation
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.
Seems like a good step forward but I still don't think createPostMessageChannel()
should end up creating both a PM and WS transport, that's just confusing.
My advice would be to have two files, postmessageTransport.ts
and websocketTransport.ts
that are responsible for the transports, and are "dumb". Then a second file createBrowserChannel
or similar that uses the two transports and is used by the builders.
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.
LGTM thanks @ndelangen!
New and updated dependency changes detected. Learn more about Socket for GitHub ↗︎ |
Telescoped off: #22940
@storybook/channels
./code/deprecated
, added shims to the old content that's moved.createPostMessageChannel
from@storybook/channels
createBrowserChannel
functioncreateBrowserChannel
Custom builders will need this change applied as well, or their browser won't listen to the serverChannel.