Open jlariza opened 3 years ago
We've been facing the same issues – webpack exits with code 1 because of this (when running in production mode)
I have the same issue with Webpack 5 and I fix the problem with adding the option allowOptimization to true
@MasterTheRock Didn't help me...
I don't know why, but I add new bundle and some of this bundle generate ERROR in Conflict: Multiple assets emit different content to the same filename
, but not all :/
I delete all function one by one in my file and I found one function that create the error, but why? I don't know! This is my function that cause the issue :
function handleKeyPress(event) {
const key = event.which ?? event.keyCode;
if(key === 46) {
const text = event.currentTarget.value;
if(text.indexOf('.') === -1) {
return true;
}
}
if(key > 31 && (key < 48 || key > 57)) {
return false;
}
return true;
}
This is my function that cause no issue :
function handleKeyPress(event) {
const key = event.which ?? event.keyCode;
if(key === 46 && event.currentTarget.value.indexOf('.') === -1) {
return true;
}
if(key > 31 && (key < 48 || key > 57)) {
return false;
}
return true;
}
I ran into this issue as well. We found that it was caused by the MiniCssExtractPlugin (or at least in our case it was). Updating this plugin from 1.6.0 (April 2021) to 2.4.5 (November 2021) and this problem was gone
Good day,
We are using this module to concat some JS. However, when compiling, we get several
ERROR in Conflict: Multiple assets emit different content to the same filename
for each output file.This is the configuration we are using
Are we missing something?
Thank you,