Next.js HMR sometimes not working

[schickling]

I've noticed that in some situations Next.js' HMR stops working after some time. I suspect this rather to be a problem in Next.js than in Contentlayer but I'm not certain yet since I can't yet reliably reproduce the problem.

If someone else faces the same problem, please share your situation below in the comments. 🙏

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[schickling]

I was able to confirm that this is indeed a bug in Next.js (thanks @sokra for your help!). The problem is that Next.js seems to only listen to changes for ~30 seconds after the last change and then automatically "unsubscribes". This might change with the introduction of React Server Components.

[OmkarK45]

Hey! is there any fix in this case!?
Would polling work ?

[schickling]

Unfortunately I'm not aware of any workaround / solution to this problem but I'm in touch with the Next.js team about it. I've also just filed a bug report for it: vercel/next.js#34054

[OmkarK45]

Alright no worries. Thanks a lot for creating this lib <3

[schickling]

Seems like this can be configured like here: https://nextjs.org/docs/api-reference/next.config.js/configuring-onDemandEntries

Will look into how to make this the default behaviour for Contentlayer out of the box soon.

[schickling]

This should be addressed with 0.1.2.

However, ideally the workaround implemented with 0.1.2 isn't necessary in the future when the underlaying Next.js problem has been solved (see vercel/next.js#34054 (comment))