-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Generating output with different contents but the same hash #2631
Comments
Yeah… short answer is we aren't able to make JavaScript actually cachable with webpack 1. I'm pretty sure this is fixable for the coming upgrade to webpack 3 but for now, don't cache JS just things in Planning on writing a Gatsby caching docs page soon. |
Thanks for that. Nice to know I am not going insane. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I am having trouble with some of my js files outputting different content with the same hashes. This gives me javascript exceptions because due to caching I have some files from the old build and some from the new saved in the CDN.
The result is I get
Uncaught TypeError: Cannot read property 'call' of undefined
inwebpackJsonp
until I invalidate the cache in the CDN and browser and the browser-based js doesn't work.package.json:
gatsby-node.js:
gatsby-config.js
I am running node v8.7.0 on MacOS X High Sierra. Any ideas?
The text was updated successfully, but these errors were encountered: