Norbert de Langen

I've found a 'hack' to suit my use-case for now actually. Are you interested in this feature?

Sure, what do you need to know? The configure method is just a basic bootstrap to enable hot module replacement, see the implementation here: https://github.com/storybooks/storybook/blob/360fb0b588cf593fb142b4916d20abc451836678/app/react-native/src/preview/index.js#L32

```js import StoryRouter from 'storybook-vue-router'; export default { title: 'PopupMenu', decorators: [StoryRouter], }; export const defaultPopupMenu = () => ({ template: '', }); ``` You're placing the decorators property in...

I'm effectively reverting the breaking change @yannbf Yes this is preferred over importing it from the main entry, especially in the `manager.ts` file.

We started doing this to ensure we use the 'correct' babel-loader and other stuff users might have multiple versions installed of. I think this has just become an "established pattern"...

Very true @tmeasday , it can likely be dropped!

Will be fixed in 7.0

@GanHingLong0423 thank you for this PR, unfortunately I'm going to close this one; sorry. This package doesn't have any build steps at all, it's just a single file which is...

Yes, I think `lib/core-webpack` is a good target!

Just as a heads-up for users of (as of writing in alpha 7.0): In storybook 7.0 we renamed this id to `#storybook-root`.