拥抱webpack4,有效缩减构建时间57%+
背景
最近有感觉到,随着系统模块数量的增加,wepack
编译打包的速度越来越慢,于是我想给项目做一下优化升级,也借此机会系统地学习一下webpack4
。
升级过程
当前版本
"dependencies": {
"@fullcalendar/core": "^4.2.0",
"@fullcalendar/daygrid": "^4.2.0",
"@fullcalendar/interaction": "^4.2.0",
"@fullcalendar/vue": "^4.2.2",
"axios": "0.18.1",
"babel-polyfill": "6.26.0",
"echarts": "4.0.4",
"element-ui": "2.10.0",
"jquery": "3.3.1",
"js-cookie": "2.2.0",
"js-md5": "0.7.3",
"lodash": "4.17.5",
"moment": "^2.24.0",
"node-sass": "^4.11.0",
"normalize.css": "7.0.0",
"nprogress": "0.2.0",
"qs": "6.5.1",
"vue": "2.6.10",
"vue-router": "3.0.3",
"vuex": "3.1.1"
},
"devDependencies": {
"autoprefixer": "7.2.3",
"babel-core": "6.26.0",
"babel-eslint": "8.0.3",
"babel-helper-vue-jsx-merge-props": "2.0.3",
"babel-loader": "7.1.2",
"babel-plugin-syntax-jsx": "6.18.0",
"babel-plugin-transform-runtime": "6.23.0",
"babel-plugin-transform-vue-jsx": "3.7.0",
"babel-preset-env": "1.6.1",
"babel-preset-stage-2": "6.24.1",
"chalk": "2.3.0",
"copy-webpack-plugin": "4.2.3",
"css-loader": "0.28.7",
"eslint": "4.13.1",
"eslint-friendly-formatter": "3.0.0",
"eslint-loader": "1.9.0",
"eslint-plugin-html": "4.0.1",
"eventsource-polyfill": "0.9.6",
"extract-text-webpack-plugin": "3.0.2",
"file-loader": "1.1.5",
"friendly-errors-webpack-plugin": "1.6.1",
"html-webpack-plugin": "2.30.1",
"node-notifier": "5.1.2",
"optimize-css-assets-webpack-plugin": "3.2.0",
"ora": "1.3.0",
"portfinder": "1.0.13",
"postcss-import": "11.0.0",
"postcss-loader": "2.0.9",
"rimraf": "2.6.2",
"sass-loader": "6.0.6",
"semver": "5.4.1",
"shelljs": "0.7.8",
"svg-sprite-loader": "4.1.6",
"uglifyjs-webpack-plugin": "1.1.3",
"url-loader": "0.6.2",
"vue-loader": "15.7.0",
"vue-style-loader": "4.1.2",
"vue-template-compiler": "2.6.10",
"webpack": "3.10.0",
"webpack-bundle-analyzer": "2.9.1",
"webpack-dev-server": "2.9.7",
"webpack-merge": "4.1.1"
}
目标版本
"dependencies": {
"@fullcalendar/core": "^4.2.0",
"@fullcalendar/daygrid": "^4.2.0",
"@fullcalendar/interaction": "^4.2.0",
"@fullcalendar/vue": "^4.2.2",
"axios": "0.18.1",
"babel-polyfill": "6.26.0",
"echarts": "4.0.4",
"element-ui": "2.10.0",
"jquery": "3.3.1",
"js-cookie": "2.2.0",
"js-md5": "0.7.3",
"lodash": "4.17.5",
"moment": "^2.24.0",
"node-sass": "^4.11.0",
"normalize.css": "7.0.0",
"nprogress": "0.2.0",
"qs": "6.5.1",
"vue": "2.6.10",
"vue-router": "3.0.3",
"vuex": "3.1.1"
},
"devDependencies": {
"autoprefixer": "9.6.1",
"babel-core": "6.26.3",
"babel-eslint": "10.0.3",
"babel-helper-vue-jsx-merge-props": "2.0.3",
"babel-loader": "^7.1.5",
"babel-plugin-syntax-jsx": "6.18.0",
"babel-plugin-transform-runtime": "6.23.0",
"babel-plugin-transform-vue-jsx": "3.7.0",
"babel-preset-env": "1.7.0",
"babel-preset-stage-2": "6.24.1",
"chalk": "2.4.2",
"copy-webpack-plugin": "5.0.4",
"css-loader": "3.2.0",
"eslint": "6.3.0",
"eslint-friendly-formatter": "3.0.0",
"eslint-import-resolver-webpack": "^0.11.1",
"eslint-loader": "3.0.0",
"eslint-plugin-vue": "^5.2.3",
"eventsource-polyfill": "0.9.6",
"file-loader": "4.2.0",
"friendly-errors-webpack-plugin": "1.7.0",
"html-webpack-plugin": "3.2.0",
"mini-css-extract-plugin": "^0.8.0",
"node-notifier": "5.1.2",
"optimize-css-assets-webpack-plugin": "3.2.0",
"ora": "1.3.0",
"portfinder": "1.0.13",
"postcss-import": "12.0.1",
"postcss-loader": "3.0.0",
"rimraf": "2.6.2",
"sass-loader": "8.0.0",
"semver": "5.4.1",
"shelljs": "0.7.8",
"svg-sprite-loader": "4.1.6",
"uglifyjs-webpack-plugin": "2.2.0",
"url-loader": "2.1.0",
"vue-loader": "15.7.1",
"vue-style-loader": "4.1.2",
"vue-template-compiler": "2.6.10",
"webpack": "4.39.3",
"webpack-bundle-analyzer": "3.4.1",
"webpack-cli": "^3.3.8",
"webpack-dev-server": "3.8.0",
"webpack-merge": "4.2.2"
}
第一步
升级webpack
到4.39.3
版本,npm run dev
遇到了报错......
npm run dev报错
webpack-dev-server版本过低
Error: Cannot find module 'webpack/bin/config-yargs'
应该是webpack
与webpack-dev-server
版本不符,于是升级webpack-dev-server
到3.8.0
版本。
webpack-cli缺失
The CLI moved into a separate package: webpack-cli
Please install 'webpack-cli' in addition to webpack itself to use the CLI
-> When using npm: npm i -D webpack-cli
-> When using yarn: yarn add -D webpack-cli
internal/modules/cjs/loader.js:584
throw err;
^
Error: Cannot find module 'webpack-cli/bin/config-yargs'
webpack4
将webpack-cli
单独分离出来了,因此提示我们安装webpack-cli
,那就直接安装吧。
html-webpack-plugin版本问题
10% building 2/2 modules 0 active(node:8596) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
(node:8596) DeprecationWarning: Tapable.apply is deprecated. Call apply on the plugin directly instead
53% building 363/366 modules 3 active D:\coollu\projects\coollu-v3\source-code\develop\coollu-cloud-web\node_modules\core-js\modules\_array-reduce.jsD:\coollu\projects\coollu-v3\source-code\develop\coollu-cloud-web\node_modules\html-webpack-plugin\lib\compiler.js:81
var outputName = compilation.mainTemplate.applyPluginsWaterfall('asset-path', outputOptions.filename, {
^
TypeError: compilation.mainTemplate.applyPluginsWaterfall is not a function
考虑是html-webpack-plugin
版本问题,升级至3.2.0
extract-text-webpack-plugin?
10% building 2/2 modules 0 active(node:19732) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
查到是因为extract-text-webpack-plugin
不再支持webpack4.3
,需要改用mini-css-extract-plugin
。
ps: extract-text-webpack-plugin
是用来抽取依赖的.css
文件的,防止样式全部打包在js bundle
里太大。改用了mini-css-extract-plugin
后,该报错并未消除,考虑要用compiler
钩子重写一些东西,先在这埋个坑,后面弄明白了再来填坑。
eslint-loader升版本
Module build failed (from ./node_modules/eslint-loader/index.js):
TypeError: Cannot read property 'eslint' of undefined
at Object.module.exports (D:\coollu\projects\coollu-v3\source-code\develop\coollu-cloud-web\node_modules\eslint-loader\index.js:148:18)
升级eslint-loader
file-loader升版本
Module build failed (from ./node_modules/file-loader/dist/cjs.js):
TypeError: Cannot read property 'context' of undefined
at Object.loader (D:\coollu\projects\coollu-v3\source-code\develop\coollu-cloud-web\node_modules\file-loader\dist\index.js:34:49)
升级file-loader
npm run build报错
改用splitChunks
webpack.optimize.CommonsChunkPlugin has been removed, please use config.optimization.splitChunks instead.
使用webpack4
的optimization.splitChunks
替代CommonsChunkPlugin
vue-loader升版本
ERROR in ./src/App.vue?vue&type=style&index=0&id=7c362b6c&lang=scss&scoped=tr (./node_modules/mini-css-extract-plugin/dist/loader.js??ref--10-0!./node_mods/vue-loader/lib??vue-loader-options!./src/App.vue?vue&type=style&index=0&id=62b6c&lang=scss&scoped=true&)
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.:
ModuleParseError: Module parse failed: Unexpected character '#' (14:0)
File was processed with these loaders:
* ./node_modules/vue-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
考虑是vue-loader
版本问题,先升级vue-loader@15.7.1
babel-loader降版本
ERROR in ./src/main.js
Module build failed (from ./node_modules/babel-loader/lib/index.js):
Error: Cannot find module '@babel/core'
babel-loader@8 requires Babel 7.x (the package '@babel/core'). If you'd like to use Babel 6.x ('babel-core'), you should install 'babel-loader@7'.
把babel-loader@8
降低了版本,调整为babel-loader@7
ps: 想了一下,觉得可能其他的loader
版本也会过低,于是将其他的loader
都进行了升级,具体见package.json。
优化打包速度
happypack
一个号称用多进程策略提升webpack
打包速度的插件,真的挺管用的。
happypack允许您并行转换多个文件,从而加快了webpack的构建速度。
安装:
npm install --save-dev happypack
简单配置如下:
const HappyPack = require('happypack')
// webpack配置,只列出关于happypack的配置
rules: [
// ...其他rule
{
test: /\.js$/,
// 注释掉原来的babel-loader,改用happypack/loader
// loader: "babel-loader",
use: ['happypack/loader'],
include: [
resolve("src")
]
}
],
plugins: [
// ...其他plugin
// 安装说明简单配置了一下
new HappyPack({
// 将我们刚才注释的loader放在这,告诉happypack
loaders: ['babel-loader'],
// 开启4个子进程,据说是最优解
threads: 4
})
]
总结
经过大量npm
包版本的调整,以及webpack
配置的修改(主要是optimization
的调整;把extract-text-webpack-plugin
换成了mini-css-extract-plugin
;加入了happypack
),报错基本上消除了,经测试,dev
和prod
环境都没有功能上的问题,热加载,编译,打包速度确实得到了显著提升。
热加载
速度得到了显著提升,之前改一行代码,热加载编译的时间差不多要花
1min
,让人难受;优化后,基本上控制在<=5s
webpack
升级前打包:Hash: 35f207120dd3736758dd
Version: webpack 3.10.0
Time: 95987ms
大概需要
96s
的打包时间。webpack
升级后打包:Hash: fb73468076752cad58f6
Version: webpack 4.39.3
Time: 61597ms
打包时间降低到
61.6s
,节约了34.4s
,打包效率提升了35.8%
以上。使用
happypack
后:Happy[1]: Version: 5.0.1. Threads: 4
Happy[1]: All set; signaling webpack to proceed.
Hash: a635e8b39b7064adf41c
Version: webpack 4.39.3
Time: 41047ms
打包时间降低到
41s
,再次节约了20.6s
!总共节约了55s
,与升级前相比,打包效率提升了57%
以上。
当然可优化的空间还很大,webpack4
还有很多东西值得我们去折腾,优化之路还在继续!
扫一扫下方小程序二维码或搜索Tusi博客
,即刻阅读最新文章!
拥抱webpack4,有效缩减构建时间57%+的更多相关文章
- 利用构建缓存机制缩短Docker镜像构建时间
在使用Docker部署PHP或者node.js应用时,常用的方法是将代码和环境镜像打包成一个镜像然后运行,一些云厂商提供了非常便捷的操作,只需要把我们的代码提交到VCS上,然后它们就会帮我们拉取代码并 ...
- 优化webpack构建时间的小技巧
在之前工作的地方,我们一直使用webpck去构建.但是,经过长达四年的更新迭代,每个人都在同一个项目中做了不同的操作和更新,这导致我们生产构建时间达到了惊人的一分半,watch模式的rebuild也达 ...
- Jenkins插件之显示构建时间
1.进入jenkin插件管理器中,安装 Timestamper 插件 2.安装完成后,进入到构建任务里面,在 构建环境 中勾选 Add timestamps to the Console Outp ...
- Java 项目热部署,节省构建时间的正确姿势
上周末,帮杨小邪(我的大学室友)远程调试项目.SpringBoot 构建,没有热部署,改一下就得重启相关模块.小小的 bug ,搞了我一个多小时,大部分时间都还在构建上(特么,下次得收钱才行).我跟他 ...
- Jenkins构建时间Poll Scm的设置
每15分钟构建一次:H/15 * * * * 或*/15 * * * * 每天8点构建一次:0 8 * * * 每天8点~17点,两小时构建一次:0 8-17/2 * * * 周一到周五,8点~1 ...
- Jenkins定时构建时间设置
每隔5分钟构建一次 H/ * * * * 每两小时构建一次 H H/ * * * 每天中午12点定时构建一次 H * * * 每天下午18点定时构建一次 H * * * 在每个小时的前半个小时内的每1 ...
- Jenkins构建时间Poll Scm的设置(常用设置)
每15分钟构建一次:H/15 * * * * 或*/5 * * * * 每天8点构建一次:0 8 * * * 每天8点~17点,两小时构建一次:0 8-17/2 * * * 周一到周五,8点~17 ...
- [Jenkins] Jenkins配置自动构建时间代表意义
- react - web + webpack4 从0构建
https://www.jianshu.com/p/91a4214b913b 文章https://github.com/Liao123/react-web 可运行的代码 dev分支
随机推荐
- SQLHelper.cs类 微软C#版
using System; using System.Data; using System.Xml; using System.Data.SqlClient; using System.Collect ...
- 《Java练习题》习题集一
编程合集: https://www.cnblogs.com/jssj/p/12002760.html Java总结:https://www.cnblogs.com/jssj/p/11146205.ht ...
- HttpRunner学习4--使用正则表达式提取数据
前言 在HttpRunner中,我们可通过extract提取数据,当响应结果为 JSON 结构,可使用 content 结合 . 运算符的方式,如 content.code,用起来十分方便,但如果响应 ...
- 12-Factor与云原生
12-Factor与云原生 云原生应用 今天先到这儿,希望对技术领导力, 企业管理,系统架构设计与评估,团队管理, 项目管理, 产品管理,团队建设 有参考作用 , 您可能感兴趣的文章: 精益IT组织与 ...
- java之枚举和注解
JDK1.5新增的enum关键字用于定义枚举类. 枚举类和普通类的区别: 使用enum定义的枚举类默认继承了java.lang.Enum类: 枚举类的构造器只能使用private修饰符: 枚举类的所有 ...
- Java描述设计模式(14):解释器模式
本文源码:GitHub·点这里 || GitEE·点这里 一.解释器模式 1.基础概念 解释器模式是对象的行为模式.给定一个语言之后,解释器模式可以定义出其文法的一种表示,并同时提供一个解释器.客户端 ...
- .NET面试题解析(9)-SQL语言基础及数据库基本原理
见面试题 1. 索引的作用?她的优点缺点是什么? 2. 介绍存储过程基本概念和 她的优缺点? 3. 使用索引有哪些需要注意的地方? 4. 索引碎片是如何产生的?有什么危害?又该如何处理? 5. 锁的目 ...
- MS16-072域内中间人攻击
0x01 漏洞利用 在目标主机域用户口令已知的条件下,目标主机在进行策略更新时,对域服务器的认证存在漏洞,攻击者劫持认证服务器的过程,引导至伪造的域服务器,并在域服务器中制定用户的计划任务策略,可以获 ...
- reports buileder 触发器的写法
触发器写法: function CF_SHOULD_BACK_TIMEFormula return Number is--其他:取MES工时按工段分别统计产量.投入工时合计:应回报工时=移动数量*[∑ ...
- digitalworld.local:Torment Vulnhub Walkthrough
主机层面扫描: ╰─ nmap -p1-65535 -sV -A 10.10.202.135Starting Nmap 7.70 ( https://nmap.org ) at 2019-08-09 ...