[Bug]: Importing `@storybook/components` into mdx pages results in render failure in Storybook 8 about storybook HOT 5 OPEN

This seems to be some kind of webpack/yarn bundle issue @shilman I can see @storybook/components in two different chunks, specifically try searching for this "../.yarn/__virtual__/@storybook-components-virtual-a8967408c7/4/.yarn/berry/cache/@storybook-components-npm-8.1.3-da5969b1b0-10.zip/node_modules/@storybook/components/dist/index.mjs", it'll be in both these files:

Looking like this in both cases:

from storybook.

@storybookjs/core This looks like some kind of issue with the theme provider. From what I can tell all the package versions are correct, and the Docs page is wrapped in a valid ThemeProvider, so I'm really not sure what's going on here. Any ideas?

from storybook.

What's the use case of rendering storybook/components inside stories? This is not it's intended use-case.

For documentation blocks we have @storybook/blocks.

from storybook.

@ndelangen not strictly inside stories but for more complex documentation pages, where I oftentimes need to import things like buttons, tabs etc. It makes total sense to me to reuse the UI of Storybook for that purpose and this used to work without breaking the rendering in storybook@7

from storybook.

I sympathize that it worked pre 8.0.

However the components defined in @storybook/components require a special context present.

Though it worked.. this was not intended to work / officially supported.

I would be open to adding some more components for blocks, which would then be officially supported.

from storybook.