Extending webpack config fails without user-provided module property (storybook/vue)

[hoopyfroody]

Issue details

This issue is exactly as described in #1467, only now with @storybook/vue. I would have tried the fix from that story, but the structure of the part where the webpack config is extended is a little more ancient in storybook-vue it seems and I couldn't quite make it work.

Please specify which version of Storybook and optionally any affected addons that you're running

• storybook/vue 3.3.15

[igor-dv]

What if you just add empty rules?

{
   module: {
      rules: [],
   },
   plugins: [
     /// ,,,,
   ]
}

[hoopyfroody]

Yeah, that's the workaround, but that doesn't seem like something you want a user to have to think of.

[Hypnosphi]

Looks like we just need to apply #1468 fix to other frameworks. E.g. here's the place to apply it for vue:
https://github.com/storybooks/storybook/blob/master/app/vue/src/server/config.js#L74

Anybody is welcome to open a PR

[Hypnosphi]

Fix for vue released as 3.4.0-rc.4. Please do the same for angular and polymer

[stale]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[igor-dv]

It should've been fixed with moving server/config.js to the core

[Hypnosphi]

Yes, but not for 3.4

[igor-dv]

I think it can be closed already.