Mostafa Sherif

@shilman first of all, thanks so much for this, second, sorry for noticing this PR so late, third, can we restructure the `features` prop to contain framework specific features listed...

Hi @nikhilnxvverma1 The errors you are getting is because the storybook tsconfig.json file actually is including all files from src/**/*.ts, that's where your problem lies, I would suggest: * [...

@JReinhold 1- you're correct, this only affects webpack for the current time being. We need to plan the vite movement to addon-docs accordingly. 2- The `remark-mdx-code-meta` plugin does only one...

@JReinhold, I've done the following: * [x] add vite support for themed fenced code blocks. * [x] add code blocks story into `addon-docs`. * [x] remove sandbox part that prevented...

@shilman I totally agree with you in regards to making this a recipe instead of implementing it into `builder-vite` or `addon-docs`, should we submit a PR to `frontpage` or close...

@Integrayshaun I'm preparing a doc and I will share with you shortly.

@maicol07 The proper migration here is to use `of` instead of actual children elements. ```jsx ``` Please refer to https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#canvas-block

@shilman & @jonniebigodes I can take over this docs task. I already know of the issue and wrote about it @ https://sheriffmoose.medium.com/storybook-markdown-docs-not-mdx-part-2-757463fcad84

Yes, because Storybook is expecting `preview.@(js|jsx|ts|tsx)`. I have created #20718 to handle the processing better.

For anyone interested, I've already published a new library [webpack-plugin-istanbul](https://npmjs.org/package/webpack-plugin-istanbul) for the purpose of using upgraded version of `istanbul-lib-instrument v5` along with supporting `webpack v5`. The new library contains both...