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
// - The `AbortController` is meant for the client side, but ends in the server code somehow.
8
+
// That's why we can get ride of it. See https://github.com/vercel/next.js/pull/73975/files.
9
+
// - Top level instantiation of `AbortController` are not supported by workerd as of March, 2025.
10
+
// See https://github.com/cloudflare/workerd/issues/3657
11
+
// - As Next code is not more executed at top level, we do not need to apply this patch
12
+
// See https://github.com/opennextjs/opennextjs-cloudflare/pull/497
13
+
//
4
14
// We try to be as specific as possible to avoid patching the wrong thing here
5
-
// It seems that there is a bug in the worker runtime. When the AbortController is created outside of the request context it throws an error (not sure if it's expected or not) except in this case. https://github.com/cloudflare/workerd/issues/3657
6
-
// It fails while requiring the `app-page.runtime.prod.js` file, but instead of throwing an error, it just return an empty object for the `require('app-page.runtime.prod.js')` call which makes every request to an app router page fail.
7
-
// If it's a bug in workerd and it's not expected to throw an error, we can remove this patch.
0 commit comments