从 create-react-app 的 service worker 缓存中排除 index.html
exclude index.html from service worker cache in create-react-app
我有一个 reactJs 应用程序,使用 create-react-app。该应用程序使用 service-worker 和其他 PWA 功能,但不知何故我发现尽管更新了网站或部署了新版本,chrome 总是从服务中选择 index.html
worker 并且根本不进行网络调用。
我认为使用 service worker 缓存 index.html 是个问题,但无法将其排除在缓存之外,我确实检查了一些关于 SO 的问题和关于 github 的问题但是无法解决这个问题。
我正在使用默认的 service-worker 注册
registerServiceWorker.js
// 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.
// This link also includes instructions on opting out of this behavior.
const isLocalhost = Boolean(
window.location.hostname === 'localhost' ||
// [::1] is the IPv6 localhost address.
window.location.hostname === '[::1]' ||
// 127.0.0.1/8 is considered localhost for IPv4.
window.location.hostname.match(
/^127(?:\.(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)){3}$/
)
);
export default function register() {
if (/*process.env.NODE_ENV === 'production' &&*/ 'serviceWorker' in navigator) {
// alert('found' + process.env.NODE_ENV);
// The URL constructor is available in all browsers that support SW.
const publicUrl = new URL(process.env.PUBLIC_URL, window.location);
if (publicUrl.origin !== window.location.origin) {
// Our service worker won't work if PUBLIC_URL is on a different origin
// from what our page is served on. This might happen if a CDN is used to
// serve assets; see https://github.com/facebookincubator/create-react-app/issues/2374
return;
}
window.addEventListener('load', () => {
const swUrl = `${process.env.PUBLIC_URL}/service-worker.js`;
if (isLocalhost) {
// This is running on localhost. Lets check if a service worker still exists or not.
checkValidServiceWorker(swUrl);
} else {
// Is not local host. Just register service worker
registerValidSW(swUrl);
}
});
} else {
//alert('not found' + process.env.NODE_ENV);
}
}
function registerValidSW(swUrl) {
navigator.serviceWorker
.register(swUrl)
.then(registration => {
registration.onupdatefound = () => {
const installingWorker = registration.installing;
installingWorker.onstatechange = () => {
if (installingWorker.state === 'installed') {
if (navigator.serviceWorker.controller) {
// At this point, the old content will have been purged and
// the fresh content will have been added to the cache.
// It's the perfect time to display a "New content is
// available; please refresh." message in your web app.
console.log('New content is available; please refresh.');
} else {
// At this point, everything has been precached.
// It's the perfect time to display a
// "Content is cached for offline use." message.
console.log('Content is cached for offline use.');
}
}
};
};
})
.catch(error => {
console.error('Error during service worker registration:', error);
});
}
function checkValidServiceWorker(swUrl) {
// Check if the service worker can be found. If it can't reload the page.
fetch(swUrl)
.then(response => {
// Ensure service worker exists, and that we really are getting a JS file.
if (
response.status === 404 ||
response.headers.get('Content-Type').indexOf('javascript') === -1
) {
// No service worker found. Probably a different app. Reload the page.
navigator.serviceWorker.ready.then(registration => {
registration.unregister().then(() => {
window.location.reload();
});
});
} else {
// Service worker found. Proceed as normal.
registerValidSW(swUrl);
}
})
.catch(() => {
console.log(
'No internet connection found. App is running in offline mode.'
);
});
}
export function unregister() {
if ('serviceWorker' in navigator) {
navigator.serviceWorker.ready.then(registration => {
registration.unregister();
});
}
}
请帮忙。
尝试了多种选择后,效果最好的不是我真正愿意实施的,但找不到更好的。
从 service-worker.js
文件中删除以下行
workbox.routing.registerNavigationRoute("/index.html", {
blacklist: [/^\/_/,/\/[^\/]+\.[^\/]+$/],
});
这不会缓存 index.html
并且每次都尝试从服务器中提取它,虽然这听起来不是最好的但确实有效。
如果您已从 create-react-app 弹出,您可以进入 /config/webpack.config.js 并将 GenerateSW() 的默认参数更改为以下内容:
new WorkboxWebpackPlugin.GenerateSW({
clientsClaim: true,
exclude: [/\.map$/, /asset-manifest\.json$/, /index.html/],
importWorkboxFrom: "cdn",
navigateFallbackBlacklist: [
// Exclude URLs starting with /_, as they're likely an API call
new RegExp("^/_"),
// Exclude URLs containing a dot, as they're likely a resource in
// public/ and not a SPA route
new RegExp("/[^/]+\.[^/]+$")
]
这样您就不必在每次建造后手动更改 serviceworker.js。
对于使用 InjectManifest 而不是 GenerateSW 的人
您可能已经发现,InjectManifest 不允许使用 blacklist
和 navigateFallbackBlacklist
选项。
我的解决方案是制作一个可以缓存的 index-shell.html 并将原始的 index.html 保留在缓存之外。
new InjectManifest({
include: [
/index-shell\.html$/,
],
exclude: [
/index\.html$/,
],
modifyURLPrefix: {'/public/': '/'}, // solved my routing issues with publicPath and what not...
...
})
我有一个 reactJs 应用程序,使用 create-react-app。该应用程序使用 service-worker 和其他 PWA 功能,但不知何故我发现尽管更新了网站或部署了新版本,chrome 总是从服务中选择 index.html
worker 并且根本不进行网络调用。
我认为使用 service worker 缓存 index.html 是个问题,但无法将其排除在缓存之外,我确实检查了一些关于 SO 的问题和关于 github 的问题但是无法解决这个问题。
我正在使用默认的 service-worker 注册
registerServiceWorker.js
// 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.
// This link also includes instructions on opting out of this behavior.
const isLocalhost = Boolean(
window.location.hostname === 'localhost' ||
// [::1] is the IPv6 localhost address.
window.location.hostname === '[::1]' ||
// 127.0.0.1/8 is considered localhost for IPv4.
window.location.hostname.match(
/^127(?:\.(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)){3}$/
)
);
export default function register() {
if (/*process.env.NODE_ENV === 'production' &&*/ 'serviceWorker' in navigator) {
// alert('found' + process.env.NODE_ENV);
// The URL constructor is available in all browsers that support SW.
const publicUrl = new URL(process.env.PUBLIC_URL, window.location);
if (publicUrl.origin !== window.location.origin) {
// Our service worker won't work if PUBLIC_URL is on a different origin
// from what our page is served on. This might happen if a CDN is used to
// serve assets; see https://github.com/facebookincubator/create-react-app/issues/2374
return;
}
window.addEventListener('load', () => {
const swUrl = `${process.env.PUBLIC_URL}/service-worker.js`;
if (isLocalhost) {
// This is running on localhost. Lets check if a service worker still exists or not.
checkValidServiceWorker(swUrl);
} else {
// Is not local host. Just register service worker
registerValidSW(swUrl);
}
});
} else {
//alert('not found' + process.env.NODE_ENV);
}
}
function registerValidSW(swUrl) {
navigator.serviceWorker
.register(swUrl)
.then(registration => {
registration.onupdatefound = () => {
const installingWorker = registration.installing;
installingWorker.onstatechange = () => {
if (installingWorker.state === 'installed') {
if (navigator.serviceWorker.controller) {
// At this point, the old content will have been purged and
// the fresh content will have been added to the cache.
// It's the perfect time to display a "New content is
// available; please refresh." message in your web app.
console.log('New content is available; please refresh.');
} else {
// At this point, everything has been precached.
// It's the perfect time to display a
// "Content is cached for offline use." message.
console.log('Content is cached for offline use.');
}
}
};
};
})
.catch(error => {
console.error('Error during service worker registration:', error);
});
}
function checkValidServiceWorker(swUrl) {
// Check if the service worker can be found. If it can't reload the page.
fetch(swUrl)
.then(response => {
// Ensure service worker exists, and that we really are getting a JS file.
if (
response.status === 404 ||
response.headers.get('Content-Type').indexOf('javascript') === -1
) {
// No service worker found. Probably a different app. Reload the page.
navigator.serviceWorker.ready.then(registration => {
registration.unregister().then(() => {
window.location.reload();
});
});
} else {
// Service worker found. Proceed as normal.
registerValidSW(swUrl);
}
})
.catch(() => {
console.log(
'No internet connection found. App is running in offline mode.'
);
});
}
export function unregister() {
if ('serviceWorker' in navigator) {
navigator.serviceWorker.ready.then(registration => {
registration.unregister();
});
}
}
请帮忙。
尝试了多种选择后,效果最好的不是我真正愿意实施的,但找不到更好的。
从 service-worker.js
文件中删除以下行
workbox.routing.registerNavigationRoute("/index.html", {
blacklist: [/^\/_/,/\/[^\/]+\.[^\/]+$/],
});
这不会缓存 index.html
并且每次都尝试从服务器中提取它,虽然这听起来不是最好的但确实有效。
如果您已从 create-react-app 弹出,您可以进入 /config/webpack.config.js 并将 GenerateSW() 的默认参数更改为以下内容:
new WorkboxWebpackPlugin.GenerateSW({
clientsClaim: true,
exclude: [/\.map$/, /asset-manifest\.json$/, /index.html/],
importWorkboxFrom: "cdn",
navigateFallbackBlacklist: [
// Exclude URLs starting with /_, as they're likely an API call
new RegExp("^/_"),
// Exclude URLs containing a dot, as they're likely a resource in
// public/ and not a SPA route
new RegExp("/[^/]+\.[^/]+$")
]
这样您就不必在每次建造后手动更改 serviceworker.js。
对于使用 InjectManifest 而不是 GenerateSW 的人
您可能已经发现,InjectManifest 不允许使用 blacklist
和 navigateFallbackBlacklist
选项。
我的解决方案是制作一个可以缓存的 index-shell.html 并将原始的 index.html 保留在缓存之外。
new InjectManifest({
include: [
/index-shell\.html$/,
],
exclude: [
/index\.html$/,
],
modifyURLPrefix: {'/public/': '/'}, // solved my routing issues with publicPath and what not...
...
})