Is your proposal related to a problem?
When we build assets in reactjs using the. command react build the generated assets are like this: 2.ef2371b4.chunk.js. Where ef37.. is the hash of the file. Given that hash codes can clash, there is a possibility for the browser to render the old assets for certain parts of the code when deploying release 2 from release 1.
Describe the solution you'd like
Can we expose configuration where the hashcode can be replaced with the current time in millis -- a monotonically increasing number. In this case there is no chance for the hash code to clash
Is your proposal related to a problem?
When we build assets in reactjs using the. command
react buildthe generated assets are like this:2.ef2371b4.chunk.js. Whereef37..is the hash of the file. Given thathash codescan clash, there is a possibility for the browser to render the old assets for certain parts of the code when deploying release 2 from release 1.Describe the solution you'd like
Can we expose configuration where the
hashcodecan be replaced with thecurrent time in millis-- a monotonically increasing number. In this case there is no chance for the hash code to clash