Storybook - broken Booker page
Found a bug? Please fill out the sections below. 👍
Issue Summary
when visiting booker it gives an error.
The link: https://ui-rkjl4n59r-cal.vercel.app/?path=/story/atoms-booker--booker&globals=outline:true
Steps to Reproduce
- open storybook
- go to booker
- get the issue
Can you please assign this issue to me? Thanks : )
Hey @a0m0rajab. I'm not able to reproduce the above bug on my local as the Atoms field isn't showing up running yarn dev from apps/storybook folder.
Here is a picture for your reference
You need to open the atoms booker:
but it's not visible on your side.
Here is a screenshot for reference:
Hello !
@deepak-likes-code, The Booker component relies on the os module, which is not available in the browser environment by default. The webpackFinal configuration for os is set to false in .storybook/main.js, disabling browser compatibility entirely.
That's why Booker.stories.mdx can't render properly ( Not Visible ) .
@PeerRich Disabling all of the Node.js core modules may cause the same issue with other stories, Is there a plan to fix it later?
@a0m0rajab Regarding the useContext error you're facing, it is likely related to TRPC. It appears that the TrpcProvider is missing.
thanks @ysfBenali should not it be provided since I am using the default hosted page?