Summary

I noticed that at some point the fallback to the offline page stopped working. I was able to debug that the anomaly only occurs when using next/link. I.e. the fallback itself "kinda works" (but it kinda doesn't reload the page and you don't see the offline page just an error on the client side. A hard reset loads the offline page). If we use a regular link or other link type component the problem is not there.

Versions

next-pwa: 5.6.0
next: 13.0.2 (I also saw the same error in version 12.3.1)

How To Reproduce

Just use next/link and enter offline mode to try to load the fallback

Expected Behaviors

Working offline fallback for next/link

Screenshots

Additional Context

next.config.mjs:

import runtimeCaching from 'next-pwa/cache.js';
import i18next from './next-i18next.config.js';
import nextPWA from 'next-pwa';

const withPWA = nextPWA({
    disable: process.env.NODE_ENV === 'development',
    dest: 'public',
    cacheOnFrontEndNav: true,
    skipWaiting: true,
    runtimeCaching,
    fallbacks: {
        document: '/offline',
    },
});

const config = {
    i18n: i18next.i18n,
    images: {
        domains: ['googleusercontent.com'],
        formats: ['image/avif', 'image/webp'],
        minimumCacheTTL: 31536000,
    },
    reactStrictMode: true,
};

export default withPWA(config);

shadowwalker / next-pwa

cacheOnFrontEndNav stop working for next/link #428