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
I am seeing intermittent errors in my Vercel logs where fetch fails with the cause of "SocketError: Other Side closed". Apparently this has to do with some sort of undici problem. The internet recommends I use a fetch polyfill, but I know I can't stitch that into the next-sanity plugin. ()
I haven't been able to reproduce this error but I am seeing it in my logs.
Here's a screenshot of what I'm seeing in my vercel logs. This error has occurred over 60 times in the past 24 hours! Any help or insights would be much appreciated.
The text was updated successfully, but these errors were encountered:
I am seeing intermittent errors in my Vercel logs where fetch fails with the cause of "SocketError: Other Side closed". Apparently this has to do with some sort of undici problem. The internet recommends I use a fetch polyfill, but I know I can't stitch that into the next-sanity plugin. ()
Versions:
1.) next v14.2.5
2.) next-sanity 9.4.5
3.) node v20.8.0
4.) npm v10.1.0
I haven't been able to reproduce this error but I am seeing it in my logs.
Here's a screenshot of what I'm seeing in my vercel logs. This error has occurred over 60 times in the past 24 hours! Any help or insights would be much appreciated.
The text was updated successfully, but these errors were encountered: