lodash
做爲一個比較經常使用的前端開發工具集,在使用webpack進行vendor
分離的實踐中,會遇到將整個lodash
文件分離到vendor.js
的問題。這樣會使vendor.js
文件變得特別大。前端
webpack.config.js
文件代碼以下:node
var path = require('path'); module.exports = mode => { return { entry: { A: './moduleA.js', B: './moduleB.js', C: './moduleC.js', }, mode: mode, output: { path: path.resolve(__dirname, 'dist/'), filename: '[name].js' }, optimization: { usedExports: true, splitChunks: { cacheGroups: { commons: { chunks: 'all', minChunks: 2, maxInitialRequests: 5, minSize: 0 }, vendor: { test: /node_modules/, chunks: "initial", name: "vendor", priority: 10, enforce: true } } } }, module: { }, plugins: [ ] } }
運行npm run test
腳本命令,結果以下:webpack
Hash: 5d86af7ed04c57cca071 Version: webpack 4.28.4 Time: 5707ms Built at: 2019-01-11 19:25:04 Asset Size Chunks Chunk Names A.js 1.46 KiB 3 [emitted] A B.js 1.53 KiB 4 [emitted] B C.js 1.54 KiB 5 [emitted] C commons~A~B~C.js 132 bytes 0 [emitted] commons~A~B~C commons~A~C.js 238 bytes 1 [emitted] commons~A~C vendor.js 69.7 KiB 2 [emitted] vendor Entrypoint A = vendor.js commons~A~B~C.js commons~A~C.js A.js Entrypoint B = commons~A~B~C.js B.js Entrypoint C = vendor.js commons~A~B~C.js commons~A~C.js C.js
如上面的狀況,vendor.js
文件爲69.7kb
,若是再引用了其餘第三方庫,文件會更大。git
那麼,如何在開發的過程當中,壓縮lodash
呢?github
可使用babel-loader
在對*.js
文件進行解析,而後藉助於babel-plugin-lodash
插件對引用的lodash
進行相似tree shaking
的操做,這樣就能夠去除未使用的lodash
代碼片斷。web
安裝所需依賴:npm
yarn add babel-loader @babel/core @babel/preset-env babel-plugin-lodash --dev
像下面這樣修改webpack.config.js
配置文件:babel
... module: { rules: [ { test: /\.js$/, exclude: /node_modules/, use: { loader: 'babel-loader', options: { presets: ['@babel/preset-env'], plugins: ['lodash'] } } } ] } ...
運行npm run test
,腳本命令結果以下:工具
Hash: 30def5521978552cc93d Version: webpack 4.28.4 Time: 3249ms Built at: 2019-01-11 21:25:23 Asset Size Chunks Chunk Names A.js 1.46 KiB 3 [emitted] A B.js 1.53 KiB 4 [emitted] B C.js 1.54 KiB 5 [emitted] C commons~A~B~C.js 132 bytes 0 [emitted] commons~A~B~C commons~A~C.js 226 bytes 1 [emitted] commons~A~C vendor.js 502 bytes 2 [emitted] vendor Entrypoint A = vendor.js commons~A~B~C.js commons~A~C.js A.js Entrypoint B = commons~A~B~C.js B.js Entrypoint C = vendor.js commons~A~B~C.js commons~A~C.js C.js
vendor.js
文件從69.7kb
降至502bytes
。開發工具
根據babel-plugin-lodash
參考文檔介紹,使用lodash-webpack-plugin
能夠進一步壓縮lodash
。
安裝lodash-webpack-plugin
依賴:
yarn add lodash-webpack-plugin --dev
修改webpack.config.js
配置文件以下:
var LodashModuleReplacementPlugin = require('lodash-webpack-plugin'); ... plugins: [ new LodashModuleReplacementPlugin, ] ...
運行npm run test
腳本命令,結果以下所示:
Hash: 30def5521978552cc93d Version: webpack 4.28.4 Time: 2481ms Built at: 2019-01-11 21:07:23 Asset Size Chunks Chunk Names A.js 1.46 KiB 3 [emitted] A B.js 1.53 KiB 4 [emitted] B C.js 1.54 KiB 5 [emitted] C commons~A~B~C.js 132 bytes 0 [emitted] commons~A~B~C commons~A~C.js 226 bytes 1 [emitted] commons~A~C vendor.js 502 bytes 2 [emitted] vendor Entrypoint A = vendor.js commons~A~B~C.js commons~A~C.js A.js Entrypoint B = commons~A~B~C.js B.js Entrypoint C = vendor.js commons~A~B~C.js commons~A~C.js C.js
vendor.js
依然是502 bytes
,問題不在loadsh-webpack-plugin
,它雖然會進一步優化lodash
,可是在沒法進一步優化的狀況下,它也沒辦法。
通常狀況下,不使用lodash-webpack-plugin
就能夠知足開發的須要,可是文件特別大的狀況下,建議仍是使用它。