Adding an option to disable hash in file query in development #2492
Comments
haoqunjiang
added a commit
that referenced
this issue
Sep 12, 2018
closes #2492 The change was intended to mitigate the problem that Safari keeps caching dev bundles. But it caused several unintended bugs: 1. [Hashes in file names with HMR enabled might cause memory leaks](webpack/webpack-dev-server#377 (comment)) 2. Moving the hash to file query also breaks many webpack loaders: 1. [mocha-webpack](f683583) 2. [django-webpack-loader](#2492)) So till we find a better way to solve this issue, hashes in dev bundles should be removed.
ZanderOlidan
pushed a commit
to ZanderOlidan/vue-cli-service-chalkfix
that referenced
this issue
Feb 5, 2024
closes #2492 The change was intended to mitigate the problem that Safari keeps caching dev bundles. But it caused several unintended bugs: 1. [Hashes in file names with HMR enabled might cause memory leaks](webpack/webpack-dev-server#377 (comment)) 2. Moving the hash to file query also breaks many webpack loaders: 1. [mocha-webpack](vuejs/vue-cli@f683583) 2. [django-webpack-loader](vuejs/vue-cli#2492)) So till we find a better way to solve this issue, hashes in dev bundles should be removed.
ZanderOlidan
pushed a commit
to ZanderOlidan/vue-cli-service-chalkfix
that referenced
this issue
Feb 5, 2024
closes #2492 The change was intended to mitigate the problem that Safari keeps caching dev bundles. But it caused several unintended bugs: 1. [Hashes in file names with HMR enabled might cause memory leaks](webpack/webpack-dev-server#377 (comment)) 2. Moving the hash to file query also breaks many webpack loaders: 1. [mocha-webpack](vuejs/vue-cli@f683583) 2. [django-webpack-loader](vuejs/vue-cli#2492)) So till we find a better way to solve this issue, hashes in dev bundles should be removed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What problem does this feature solve?
Hi, we are using
django-webpack-loaderwhich would expect the files generated to end with their extension. With v3.0.2 this is no longer true so we have to stick with v3.0.1.Is it possible to add an option for this?
What does the proposed API look like?
It would probably be a config entry in
vue.config.js.The text was updated successfully, but these errors were encountered: