vuejs-templates/webpack

vendor.js hash value changes after component modification

Open

#1,270 建立於 2018年1月24日

在 GitHub 查看
 (4 留言) (0 反應) (0 負責人)JavaScript (9,721 star) (4,466 fork)batch import
help wanted

描述

Reproduction link

https://github.com/iCodeBIT/vendorHashTest

Steps to reproduce

  1. Delete a .vue file in /src/components directory, like Hello2.vue.
  2. npm run build;
  3. After building, we can see from "git status" that a new vendor.js is generated.

What is expected?

The hash value of vendorjs should NOT change.

What is actually happening?

The hash value of vendorjs has changed.

The project is generated from vue-template/webpack. In my point of view, vendorjs is extracted from node_modules, modifications in /src/components should not affect vendorjs. Is there anything wrong with the webpack config?

貢獻者指南

技術棧
javascriptvuehtmlcss
領域
frontendbuild system
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Basic knowledge of Vue.jsUnderstanding of webpack config
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
45
研究方向
Investigate the webpack configuration in the vuejs templates/webpack repository, specifically the chunk splitting logic for vendor.js. Look at how CommonsChunkPlugin or splitChunks is configured to separate node modules from app code. The reproduction repo at https://github.com/iCodeBIT/vendorHashTest shows that deleting a component file changes the vendor hash, which suggests that the vendor chunk includes references to the app code or the hash is computed over all modules. Compare with expected behavior where vendor hash should be stable. Check if there is a linked PR or maintainer response in the issue comments (4 comments) for clues.