Results 2 comments of Andersgee

This is still the case and adding a `navigator.serviceWorker.onmessage` is still the solution.

The same issue persists as of vercel cli version 33.4.1 and nextjs 14.1.0 The workaround #79 eg running `vercel dev --debug` to see where the nodejs (and edge runtime) serverless...