Skip to content

Releases: cloudflare/next-on-pages

[email protected]

09 Dec 10:06
2cd4c3c
Compare
Choose a tag to compare

@cloudflare/[email protected]

09 Dec 10:06
2cd4c3c
Compare
Choose a tag to compare

Patch Changes

  • e1d65f4: fix Next.js calling a non-bound waitUntil function
  • edd4fea: Allow import of node:* and cloudflare:* in worker custom entrypoint

[email protected]

28 Nov 13:20
835bec5
Compare
Choose a tag to compare

@cloudflare/[email protected]

28 Nov 13:20
835bec5
Compare
Choose a tag to compare

Patch Changes

  • d879acd: Mark async_hooks as external.

[email protected]

04 Oct 08:58
e9a9e18
Compare
Choose a tag to compare

@cloudflare/[email protected]

04 Oct 19:53
96c331d
Compare
Choose a tag to compare

Patch Changes

  • 930a79f: fix: webpack chunks not deduping with sentry (#886)

    (duplicated changeset needed because the 1.13.4 npm release doesn't properly work)

@cloudflare/[email protected]

04 Oct 08:58
e9a9e18
Compare
Choose a tag to compare

Patch Changes

  • 18e0e46: Fix the Webpack chunk deduplication when Sentry is used, as it changes the AST node structure for Webpack chunks.

@cloudflare/[email protected]

21 Sep 12:12
585f2ab
Compare
Choose a tag to compare

Patch Changes

  • d1dce9e: Fix prerendered dynamic ISR functions with catch-all segments
  • e890632: Provide __NEXT_BUILD_ID env var to functions, making them compatible with Next v14.2.8 and newer.

[email protected]

07 Aug 15:16
12080f6
Compare
Choose a tag to compare

@cloudflare/[email protected]

07 Aug 15:16
12080f6
Compare
Choose a tag to compare

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 failures

    One 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 and global 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)