vuejs-templates/webpack

vendor.js hash value changes after component modification

Open

#1,270 opened on 2018年1月24日

GitHub で見る
 (4 comments) (0 reactions) (0 assignees)JavaScript (9,721 stars) (4,466 forks)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
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.
vendor.js hash value changes after component modification · vuejs-templates/webpack#1270 | Good First Issue