Closed jknight12882 closed 7 years ago
@jknight12882 I can't reproduce the error, the two plugins co-exist fine for me. What versions of webpack and of the two plugins are you using?
@jknight12882 Which version of wrapper-webpack-plugin
?
The latest v1.0.0
@jknight12882 The configuration you posted in the other issue works fine for me.
I created an empty vendor-manifest.json
file to make it work, so perhaps that's the different.
@jknight12882 Closed for now, if you manage to reproduce it let me know.
This issue reproduces repeatedly and consistently using the above listed configuration. I had to remove this plugin in order to get things running smoothly. Not sure why you weren't able to reproduce
@jknight12882 Your configuration example is complex so I filled in the gaps as best I could to make it work; and got webpack to build normally.
I assume you're using babel to transpile the webpack configuration to es5/6, so could it possibly be related to the version/config of babel you're using?
I used babel-cli 6.24.1
with the following configuration:
{
"presets": ["es2015"],
"plugins": ["transform-object-rest-spread"]
}
Node.js version is latest v6, which is v6.11.2.
It would help if you could distill the configuration into just the bare necessities to recreate the issue as you understand it.
I am also seeing this issue. When digging deeper into the code, I placed a log statement to see what the text variable actually is and it turns out it is a function instead of an array. I am using webpack 3 with etp 3.0.0 my loaders being used are less, css and style loader. Im seeing this specifically on watch mode. The first compilation succeeds but when attempting to make a change sometimes this error pops up. I can't seem to pin it down to a single reproducible set of configurations but thought this information might provide some light on the situation.
@sresant Thanks for the extra info, I'll take another look into it.
Have you tried it again with webpack@3.5.5
? I was experiencing similar problems with webpack@3.4.1
but they are gone after upgrading webpack.
@sresant I still can't recreate this error, and as per @ctavan newer versions of webpack
seem to not cause this error at all (hopefully).
If anyone can post a webpack
configuration that can consistently recreate this error it would be very helpful, otherwise there isn't much I can do about it.
When I use
WrapperPlugin
withExtractTextPlugin
, I get the following exceptionRemoving
WrapperPlugin
causes the issue to go away