Ed Morley

Oops `Transition` is from `react-transition-group` instead, making the only remaining part of this issue identical to #1159. Sorry for the noise!

Hi! Thank you for filing an issue. I'm not able to reproduce using: ```js // package.json { "dependencies": { "terser-webpack-plugin": "2.1.3", "webpack": "4.41.1", "webpack-chain": "6.0.0" } } ``` ```js //...

@bosens-China Hi! Please can you create a fully contained testcase that demonstrates the issue? And file as a new issue? I can't use the above, since `webpack.common` is missing.

> My problem was that I used vue-cli-plugin-nativescript-vue with vue-cli 4.x > They have different interface usage(4 vs 6) within webpack-chain plugin. Thank you for this clue. Checking out that...

I've dug into this more yesterday/today. This error message is shown when the plugin configuration is incomplete, which can happen in a variety of ways. Whilst this isn't a webpack-chain...

v6.3.1 has just been released, which includes some improvements to the error message shown in some of the scenarios outlined above, which should make it easier to self-debug what's broken...

Hi! Thank you for filing this issue - I agree webpack-chain should support this case. Would you be open to creating a PR for it? :-)

Looking at the webpack docs ([concepts](https://webpack.js.org/concepts/entry-points/); [config](https://webpack.js.org/configuration/entry-context/)) and [config schema](https://github.com/webpack/webpack/blob/627510d7e72582463d76608fe3cda5a70ea17a12/schemas/WebpackOptions.json#L31-L95), it looks like the accepted forms of `entry` are: A) Single entry shorthand with single filename: ```js module.exports = {...

Ah sorry I used numbers for both the "accepted webpack config output" forms and the "there are a few problems with this" list. I've changed the former to use A-E...

Sorry I haven't replied yet - need to sit down and think about this some more when I have more solid block of time free :-)