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
As of now, the NextJS build emits a series of errors related to its aggressive caching and the heuristics it tries to employ in determining which pages and routes can be cached. This is what causes the deployment logs to be spammed with API endpoint logging because NextJS literally runs API endpoints in the process of determining what can and cannot be cached.
It would be better that either these routes explicitly declare themselves as not being cached or to rework them to be cache friendly (e.g., don't use request.url and instead rely on passing request params in the body of POST requests, etc). Either way, this would make deployment logs a lot less noisy.
The text was updated successfully, but these errors were encountered:
Related: #27
As of now, the NextJS build emits a series of errors related to its aggressive caching and the heuristics it tries to employ in determining which pages and routes can be cached. This is what causes the deployment logs to be spammed with API endpoint logging because NextJS literally runs API endpoints in the process of determining what can and cannot be cached.
It would be better that either these routes explicitly declare themselves as not being cached or to rework them to be cache friendly (e.g., don't use
request.url
and instead rely on passing request params in the body ofPOST
requests, etc). Either way, this would make deployment logs a lot less noisy.The text was updated successfully, but these errors were encountered: