Next.js Discord

Discord Forum

NextJS HMR spam re-compiling on page add/remove

Unanswered
Tosa posted this in #help-forum
Open in Discord
TosaOP
Hey! Its not a big problem, as everything works eventually, but whenever I create a new page.tsx or delete one, the page gets rapidly spam re-compiled or reloaded (not sure which). Any ideas how to stop this?

NextJS: 16.2.7

GET /admin/config/support-departments 200 in 93ms (next.js: 15ms, proxy.ts: 9ms, application-code: 68ms)
GET /admin/config/support-departments 200 in 120ms (next.js: 49ms, proxy.ts: 26ms, application-code: 46ms)
GET /admin/config/support-departments 200 in 34ms (next.js: 4ms, proxy.ts: 6ms, application-code: 25ms)
GET /admin/config/support-departments 200 in 31ms (next.js: 3ms, proxy.ts: 5ms, application-code: 24ms)
GET /admin/config/support-departments 200 in 34ms (next.js: 6ms, proxy.ts: 5ms, application-code: 23ms)
GET /admin/config/support-departments 200 in 38ms (next.js: 3ms, proxy.ts: 8ms, application-code: 27ms)
GET /admin/config/support-departments 200 in 35ms (next.js: 4ms, proxy.ts: 7ms, application-code: 25ms)
GET /admin/config/support-departments 200 in 45ms (next.js: 8ms, proxy.ts: 6ms, application-code: 32ms)
GET /admin/config/support-departments 200 in 61ms (next.js: 5ms, proxy.ts: 11ms, application-code: 45ms)
GET /admin/config/support-departments 200 in 81ms (next.js: 12ms, proxy.ts: 8ms, application-code: 61ms)
GET /admin/config/support-departments 200 in 35ms (next.js: 3ms, proxy.ts: 5ms, application-code: 26ms)
GET /admin/config/support-departments 200 in 38ms (next.js: 6ms, proxy.ts: 6ms, application-code: 26ms)
GET /admin/config/support-departments 200 in 42ms (next.js: 4ms, proxy.ts: 6ms, application-code: 32ms)
GET /admin/config/support-departments 200 in 40ms (next.js: 3ms, proxy.ts: 6ms, application-code: 31ms)

It does it about 70-100 times

3 Replies

TosaOP
It happens regardless of the page size/functionality. A single div page does it too.
Its an enormous application tho, so its hard to narrow down what's causing it
B33fb0n3
Yes, that’s a bug since nextjs 16. you can’t really do much against it. Accept it and it’s fine :/