Skip to content

Hash different for app-legacy.js and precache-manifest.js #2397

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
CaleCrawford opened this issue Aug 29, 2018 · 1 comment
Open

Hash different for app-legacy.js and precache-manifest.js #2397

CaleCrawford opened this issue Aug 29, 2018 · 1 comment
Labels
needs team repro We acknowledged your report and will soon try to reproduce it scope: cli-service build

Comments

@CaleCrawford
Copy link

Version

3.0.1

Reproduction link

https://github.com/CaleCrawford/vue-hash-reproduction

Node and OS info

Node v8.11.3, Yarn v1.9.4, Ubuntu 14.04.5 LTS

Steps to reproduce

  • Clone repo
  • Run yarn && yarn build on 2 different docker containers on 2 different servers (in the same location in our case).

What is expected?

All hashes on different docker containers with the same code should have the same filename hashes

What is actually happening?

app-legacy.js and precache-manifest.js have different hashes.


I know this issue was already reported here #1728 but none of the solutions have worked. I have tried updating vue-loader (currently ^15.3.0 as required by @vue/[email protected]). It seems to only be these 2 files that have different hashes.
Screeen shot from running build in both of my containers: https://typenine.d.pr/PoLqnB.
Same thing is happening in my larger repo: http://typenine.d.pr/7HZxqI

The contents of /dist on container #1:
css,
favicon.ico,
img,
index.html,
js,
manifest.json,
precache-manifest.00903023fe2f17b68dfaf5fe111fcc51.js,
precache-manifest.25d0c87b563be8df42f1a2d89909121c.js,
robots.txt,
service-worker.js

The contents of /dist/js on container #1:
about.5d688836.js,
about.5d688836.js.map,
about-legacy.5d688836.js,
about-legacy.5d688836.js.map,
app.fbf8891e.js,
app.fbf8891e.js.map,
app-legacy.8aa133d2.js,
app-legacy.8aa133d2.js.map,
chunk-vendors.60f29df0.js,
chunk-vendors.60f29df0.js.map,
chunk-vendors-legacy.dd398368.js,
chunk-vendors-legacy.dd398368.js.map

The contents of /dist/css on container #1:
app.9615c6dc.css

The contents of /dist on container #2:
css,
favicon.ico,
img,
index.html,
js,
manifest.json,
precache-manifest.1b4eaafdf12c205c137c7241ad52d03a.js,
precache-manifest.4eb3797952d9b3c7e80dcf1d2eed5af0.js,
robots.txt,
service-worker.js

The contents of /dist/js on container #2:
about.5d688836.js,
about.5d688836.js.map,
about-legacy.5d688836.js,
about-legacy.5d688836.js.map,
app.fbf8891e.js,
app.fbf8891e.js.map,
app-legacy.9095116f.js,
app-legacy.9095116f.js.map,
chunk-vendors.60f29df0.js,
chunk-vendors.60f29df0.js.map,
chunk-vendors-legacy.dd398368.js,
chunk-vendors-legacy.dd398368.js.map

The contents of /dist/css on container #2:
app.9615c6dc.css

Let me know if there is any other information I can get you.

@Akryum Akryum added needs team repro We acknowledged your report and will soon try to reproduce it scope: cli-service build labels Sep 2, 2018
@zhouxinyong
Copy link
Contributor

I still find this issue and error when I build the same repo in two different machine! the file hash still change and not same after build....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs team repro We acknowledged your report and will soon try to reproduce it scope: cli-service build
Projects
None yet
Development

No branches or pull requests

3 participants