Cache busting with create react app

问题:

When I updated my site, run npm run build and upload the new files to the server I am still looking the old version of my site. The repo of my project is https://github.com/Alfrex92/serverlessapps

Without React, I can see the new version of my site with cache busting. I do this:

Previous file

<link rel="stylesheet" href="/css/styles.css">

New file

<link rel="stylesheet" href="/css/styles.css?abcde">

How can I do something like this or to achieve cache busting with create react app?

There many threads in the github of create react app about this but no one has a proper/simple answer.

回答1:

This is probably because of your web worker.

If you look into your index.js file you can see

registerServiceWorker();

Never wondered what it did? If we take a look at the file it got imported from we can see

// In production, we register a service worker to serve assets from local cache.

// This lets the app load faster on subsequent visits in production, and gives
// it offline capabilities. However, it also means that developers (and users)
// will only see deployed updates on the "N+1" visit to a page, since previously
// cached resources are updated in the background.

// To learn more about the benefits of this model, read {URL}
// This link also includes instructions on opting out of this behavior.

If you want to delete the web worker, don't just delete the line. Import unregister and call it in your file instead of the register.

import { unregister } from './registerServiceWorker';

and tell call

unregister()

P.S. When you unregister, it will take at least one refresh to make it work

EDIT: create-react-app v2 now have the service worker disabled by default

回答2:

I had the same issue when I use create-react-app ( and deploy to heroku). It keeps showing the old version of my app