Question

我有一个大型的webpack构建，几乎在91％的额外资产处理和＃34;这个步骤不会给我更多信息。这个步骤消耗长达4分钟，并且在我们向构建中添加模块时似乎几乎呈指数级增长。有没有办法更好地了解在此步骤中完成的工作并最终对其进行优化？

56205ms building modules
31ms sealing
0ms optimizing
0ms basic module optimization
15ms module optimization
0ms advanced module optimization
0ms basic chunk optimization
0ms chunk optimization
16ms advanced chunk optimization
14487ms building modules
0ms module and chunk tree optimization
31ms module reviving
0ms module order optimization
16ms module id optimization
0ms chunk reviving
16ms chunk order optimization
31ms chunk id optimization
140ms hashing
0ms module assets processing
265ms chunk assets processing
0ms additional chunk assets processing
0ms recording
206740ms additional asset processing
79781ms chunk asset optimization
1ms asset optimization
906ms emitting

Answer 1

不确定您的设置是什么，但在我的情况下，Webpack和Extract Text插件导致资产加载时间过长。我改为Webpack 2.7.0和extract-text-webpack-plugin 2.1.2并且加载恢复正常。

Answer 2

在我的情况下，它是webpack babili插件（现在是babel-minify-webpack-plugin）。我用uglifyjs-webpack-plugin替换它。

我的配置：

new UglifyJSPlugin({
  parallel: true,
  exclude: /\/node_modules/,
  uglifyOptions: {
    ecma: 8,
    mangle: true,
    compress: {
      sequences: true,
      dead_code: true,
      conditionals: true,
      booleans: true,
      unused: true,
      if_return: true,
      join_vars: true,
      drop_console: true
    },
    output: {
      comments: false,
      beautify: false
    }
  }
})

webpack2生产构建非常缓慢＆＃34;额外的资产处理＆＃34;

2 个答案: