You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running NextJS inside a docker container that mounts a local volume, the server is typically slower to respond than on bare metal. In combination with Node 8, this often leads to INCOMPLETE_CHUNKED_ENCODING errors when hot module reloading.
This was fixed for bare metal setups in #2166, but the chosen heartbeat is often too short for a containerised instance.
Can we make heartbeat in server/hot-reloader.js configurable through next.config.js?
When running NextJS inside a docker container that mounts a local volume, the server is typically slower to respond than on bare metal. In combination with Node 8, this often leads to INCOMPLETE_CHUNKED_ENCODING errors when hot module reloading.
This was fixed for bare metal setups in #2166, but the chosen heartbeat is often too short for a containerised instance.
Can we make heartbeat in
server/hot-reloader.js
configurable through next.config.js?https://github.com/zeit/next.js/blob/canary/server/hot-reloader.js#L224
The text was updated successfully, but these errors were encountered: