So i've noticed these message in the console, but i did not associate them with Storybook itself until just now. Is there anything i can do to get rid of them?
#Storybook deprecation messages?
full harbor
Only custom addon i have is msw-storybook-addon cc @ruby glen ?
Source of the messages is this: https://github.com/storybookjs/storybook/blob/6bbbd405397b21bba56ad26160a4572b25145aec/code/lib/manager-api/src/modules/stories.ts#L550
manic perch
Hm, yeah it sure would be useful to know where that is coming from, wouldn't it?
full harbor
Yeah, just tried stepping through the code in the devtools debugger
but i couldn't see any actual end-user kind of code
@dapper mesa any ideas perhaps?
manic perch
Maybe do a search through your node_modules?
full harbor
for storiesHash?
manic perch
yeah
manic perch
You have to uncheck this
full harbor
looks like msw-storybook-addon is the culprit @ruby glen
probably because the addon still uses storybook 6
so i guess i'm stuck with the messages until 7 is out and the msw addon can be upgraded
@manic perch thanks for the help 🙂
manic perch
I see there is https://github.com/mswjs/msw-storybook-addon/issues/95 in the addon.
ruby glen
I'll work on it as soon as I can
full harbor
@ruby glen msw-storybook-addon also doesn't seem to survive a reload very gracefully: after a forced page reload, msw works great; but when webpack reloads, msw no longer intercepts the /api/entities/0 backend call.
ruby glen
could you file an issue on the repo? I'm not sure if that's an addon or a MSW issue
full harbor
sure
