forked from cloudflare/next-on-pages
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add changeset for cloudflare#585 (cloudflare#592)
- Loading branch information
1 parent
37260e2
commit a4efc7b
Showing
1 changed file
with
15 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
--- | ||
'@cloudflare/next-on-pages': patch | ||
--- | ||
|
||
ignore invalid `_error` functions in the App router | ||
|
||
In the App router, error boundaries are implemented as client components (see: https://nextjs.org/docs/app/api-reference/file-conventions/error), | ||
meaning that they should not produce server side logic. | ||
|
||
The Vercel build process can however generate `_error.func` lambdas (as they are useful in the | ||
Vercel network I'd assume), through experimentation we've seen that those do not seem to be | ||
necessary when building the application with next-on-pages so they should be safe to ignore. | ||
|
||
The changes here make such invalid `_error.func` lambdas (if present) ignored (as they would otherwise | ||
cause the next-on-pages build process to fail) |