Is there a certain file size the 200.js script can reach where the browser force caches it?
I see a success message on deploy, but my production site continues to fetch the 200.js file from disk cache, even on hard reload. I have to open Inspector and issue an "Empty Cache and Reload" command (one step above hard reload) for it to refetch 200.js, at which point I do see my javacript changes (I am testing this with a simple console log on render).
For reference, the size of my bundle in the network tab is "1.8MB transferred over network, resource size: 8.6MB."
Is there a certain file size the 200.js script can reach where the browser force caches it?
I see a success message on deploy, but my production site continues to fetch the 200.js file from disk cache, even on hard reload. I have to open Inspector and issue an "Empty Cache and Reload" command (one step above hard reload) for it to refetch 200.js, at which point I do see my javacript changes (I am testing this with a simple console log on render).
For reference, the size of my bundle in the network tab is "1.8MB transferred over network, resource size: 8.6MB."