vuejs-templates/webpack

vendor.js hash value changes after component modification

Open

#1 270 ouverte le 24 janv. 2018

Voir sur GitHub
 (4 commentaires) (0 réactions) (0 assignés)JavaScript (9 721 stars) (4 466 forks)batch import
help wanted

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?

Guide contributeur

Stack technique
javascriptvuehtmlcss
Domaine
frontendbuild system
Type d'issue
bug
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
3
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
1-3 hours
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
stale
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
mostly clear
Prérequis
Basic knowledge of Vue.jsUnderstanding of webpack config
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
45
Direction de recherche
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.