vuejs-templates/webpack

vendor.js hash value changes after component modification

Open

#1,270 opened on Jan 24, 2018

View on GitHub
 (4 comments) (0 reactions) (0 assignees)JavaScript (4,466 forks)batch import
help wanted

Repository metrics

Stars
 (9,721 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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?

Contributor guide

Research direction
Examine the webpack configuration, specifically the CommonsChunkPlugin or splitChunks settings, to understand why vendor chunk hash depends on component files.
Tech stack
javascriptvue
Domain
build systemfrontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScriptwebpack
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60