shared between client and server, any change on a “client” folder (in packages or even on the root folder of the project) trigger an infinite hot reload in the browser (Chrome, Firefox).
Unfortunately I had to disable it. Any idea what it could be? I am using the very basic Mantra kickstarter project.
Hi @arunoda - I commented this on your Medium post, but also realized that it'd be useful to track it here as well:
I noticed a bug with setPageCacheTimeout. If I have it enabled as you suggested above, and have a simple route like:
shared between client and server, any change on a “client” folder (in packages or even on the root folder of the project) trigger an infinite hot reload in the browser (Chrome, Firefox).
Unfortunately I had to disable it. Any idea what it could be? I am using the very basic Mantra kickstarter project.
Thanks again and, as usual, well done!