Releases: cloudflare/next-on-pages
eslint-plugin-next-on-pages@1.13.7
eslint-plugin-next-on-pages@1.13.7
@cloudflare/next-on-pages@1.13.7
eslint-plugin-next-on-pages@1.13.6
eslint-plugin-next-on-pages@1.13.6
@cloudflare/next-on-pages@1.13.6
Patch Changes
- d879acd: Mark
async_hooks
as external.
eslint-plugin-next-on-pages@1.13.4
eslint-plugin-next-on-pages@1.13.4
@cloudflare/next-on-pages@1.13.5
@cloudflare/next-on-pages@1.13.4
Patch Changes
- 18e0e46: Fix the Webpack chunk deduplication when Sentry is used, as it changes the AST node structure for Webpack chunks.
@cloudflare/next-on-pages@1.13.3
eslint-plugin-next-on-pages@1.13.2
eslint-plugin-next-on-pages@1.13.2
@cloudflare/next-on-pages@1.13.2
Patch Changes
-
968171a: Fix autogenerated content also getting appended to the original public/_headers file
-
2115b9e: fix: implement route specific global scoping strategy
currently routes all share the same global scope, this can be problematic and cause
race conditions and failuresOne example of this is the following code that is present in route function files:
self.webpackChunk_N_E = ...
and
self.webpackChunk_N_E.push(...)
this indicates that an in-memory global collection of the webpack chunks is shared by all routes,
this combined with the fact that chunks can have their own module state this can easily cause routes to conflict with each other at runtime.So, in order to solve the above issue, all route functions are wrapped in a function which accepts as parameters, thus overrides, the
self
,globalThis
andglobal
symbols. The symbols
will be resolved with proxies that redirect setters to route-scoped in-memory maps and
getters to the above mentioned map's values and fallback to the original symbol values otherwise
(i.e.globalThis
will be overridden by a proxy that, when setting values, sets them in a separate
location and, when getting values, gets them from said location if present there or from the real
globalThis
otherwise)