我遇到了这个问题已经持续两天了。因此,我决定完全禁用uglifyjs-webpack-plugin
来构建webpack。我找不到任何关于webpack 4的解决方案。
我遇到了这个问题已经持续两天了。因此,我决定完全禁用uglifyjs-webpack-plugin
来构建webpack。我找不到任何关于webpack 4的解决方案。
module.exports = {
optimization:{
minimize: false, // <---- disables uglify.
// minimizer: [new UglifyJsPlugin()] if you want to customize it.
}
}
如果您正在管理单个webpack.config.js
并基于环境使用package.json npmscripts
,那么您也可以使用这种方法。
您可以像这样做:创建一个默认的插件数组并检查环境,如果环境是prod,则将其推送到数组中,否则使用默认插件。如下所示:
package.json
"config-prod": "webpack --env.NODE_ENV=prod --parallel build-webpack",
"build-prod": "npm run config-prod"
webpack.config.js
仅添加了相关部分,以便易于阅读。
var webpack = require("webpack");
var path = require("path");
const UglifyJSPlugin = require("uglifyjs-webpack-plugin");
const HtmlWebpackPlugin = require("html-webpack-plugin");
const MiniCssExtractPlugin = require("mini-css-extract-plugin");
const webpackUtilities = require("./webpack.utilities");
module.exports = (env) => {
var defaultplugins = [
new webpack.DefinePlugin({
///// section deleted
}),
new MiniCssExtractPlugin({
///// section deleted
}),
];
return {
mode: env.NODE_ENV == "prod" ? "production" : "development",
devtool: env.NODE_ENV == "prod" ? "" : "source-map";,
entry: {
///// section deleted
},
output: {
///// section deleted
},
module: {
rules: [
{
///// section deleted
},
],
},
plugins:
env.NODE_ENV == "prod"
? [...defaultplugins, new UglifyJSPlugin()]
: [...defaultplugins],
resolve: {
extensions: [".js", ".jsx", ".scss", ".css"],
},
};
};