Skip to content

Releases: cloudflare/next-on-pages

@cloudflare/[email protected]

29 Sep 15:46
6545453
Compare
Choose a tag to compare

Patch Changes

  • 072af87: Temporarily revert the change to package-manager-manager so that the bug fix in the latest release for new next.js versions can still be releases, while a fix for #474 is investigated in the meantime.

@cloudflare/[email protected]

29 Sep 09:42
a6b9d0e
Compare
Choose a tag to compare

Patch Changes

  • cd2f7ee: correctly handle newly introduced .prefetch.rsc suffixes
  • 5b4a5b7: improve package managers and package handling by using the package-manager-manager third party library
  • b585099: Avoid using the Vercel custom config hack for Bun package manager support when a version of the Vercel CLI that supports Bun is used.
  • 628f6bb: Ignore invalid nodejs i18n functions with valid alternatives.

@cloudflare/[email protected]

15 Sep 10:53
6d849e1
Compare
Choose a tag to compare

Patch Changes

  • 0168496: Fix named capture groups in has entries in the build output config not applying to route destination paths.
  • f764fff: Fix process.env not being enumerable due to being a proxy.
  • 1e25a97: Fix dynamic parameters with an underscore leading to an incorrect param being provided.
  • c06b437: Normalize the injected function entrypoints for Windows.

[email protected]

26 Aug 19:36
82dacc5
Compare
Choose a tag to compare

@cloudflare/[email protected]

26 Aug 19:36
82dacc5
Compare
Choose a tag to compare

Minor Changes

  • 291bfde: Support for the internal fetch (suspense) cache, and next/cache data revalidation.

Patch Changes

  • cb32baf: avoid the default is not a function unclear error

    if there is some issue evaluating a lazy loaded edge function
    its default export ends up not being a function and that results
    in an unhelpful error like the following:

     TypeError: u.default is not a function
    

    slightly improve the user experience by catching such error and
    letting the user know that something went wrong with the edge
    function's evaluation:

     Error: An error occurred while evaluating the target edge function (<edge-function-path>)
    
  • 291bfde: Stop the cache property in fetch requests causing internal server error.

  • 4570aa6: add vercel@31 as a peer dependency

  • c788def: fix package version detection for yarn

  • fe6ea04: Add vercel@32 as a peer dependency

[email protected]

14 Aug 16:32
fc256cb
Compare
Choose a tag to compare

Patch Changes

  • 5bfbbe1: Add workaround so that people can use standard not-found routes in their app directory applications

    The problem is that:

    • if there's a static not-found route in app dir, that generates a serverless (edge incompatible) function (_not-found)
    • if there's a dynamic not-found route in app dir, that generates two serverless (edge incompatible) functions (_not-found, _error)

    The workaround being introduced here is:

    • if there's a static not-found route in app dir, we delete the generated _not-found serverless function
      (which is not needed as we can just fallback to the static 404 html)
    • if there's a dynamic not-found route in app dir, we can't actually fix it but provide a warning for the user

    Besides the above the no-app-not-found-runtime eslint rule has been introduced to try to help developers avoid
    the issue

@cloudflare/[email protected]

14 Aug 16:32
fc256cb
Compare
Choose a tag to compare

Patch Changes

  • 7da1fd8: fix package version detection not correctly working with yarn v1

  • 5bfbbe1: Add workaround so that people can use standard not-found routes in their app directory applications

    The problem is that:

    • if there's a static not-found route in app dir, that generates a serverless (edge incompatible) function (_not-found)
    • if there's a dynamic not-found route in app dir, that generates two serverless (edge incompatible) functions (_not-found, _error)

    The workaround being introduced here is:

    • if there's a static not-found route in app dir, we delete the generated _not-found serverless function
      (which is not needed as we can just fallback to the static 404 html)
    • if there's a dynamic not-found route in app dir, we can't actually fix it but provide a warning for the user

    Besides the above the no-app-not-found-runtime eslint rule has been introduced to try to help developers avoid
    the issue

  • 7f94fd2: Apply search params to rewritten URLs in matching.

  • 7da1fd8: install vercel yarn dev dependency only when not already present

[email protected]

31 Jul 20:46
7a18efb
Compare
Choose a tag to compare

@cloudflare/[email protected]

31 Jul 20:46
7a18efb
Compare
Choose a tag to compare

Minor Changes

  • ea98a8f: Support for defining an _routes.json file in the root of the project. Entries in the root's file are copied over to the generated one in the output directory.
  • 9faf701: add warning indicating that usage under windows is not advised
  • c6621c6: Support for using Bun as a package manager in projects.

Patch Changes

  • 3affd17: Normalize injected import paths for builds done on Windows machines.

  • 226d562: Specify the framework is nextjs in the Vercel project.json file.

  • 5aefce5: watch mode only on file changes

    only watch for file changes instead of watching for all possible changes (such as directories additions/removals, etc...),
    making sure that we don't rerun the build process unnecessarily

[email protected]

25 Jul 20:16
eae9f6a
Compare
Choose a tag to compare