-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] [Next 15.0.4 canary] Internal framework (rethrown) errors are broken #299
Comments
I'm getting the same kind of message on latest Next's
|
|
Temp solution is to downgrade to |
I encountered a similar issue with the latest version of Next.js today.
|
v7.9.10-beta.1 should solve these issues. However, due to changes in Next.js's internal error handling mechanism, the next stable release of this library will only be compatible starting from the upcoming Next.js version (presumably 15.0.5). I really don't want to introduce breaking changes, but there's little I can do about it, since the underlying framework APIs have changed a lot, and this library heavily relies on them. Let me know if the beta version solves these issues for you as well using Next.js canary, thanks! |
@TheEdoRan issue solved, thanks for the update |
https://nextjs.org/blog/next-15-1 |
Similar issue
And |
@headironc Yep, 15.0.4-canary has been released as stable 15.1. |
7.10.0 release: - updates and fixes the internal framework error handling detection, for Next.js errors that have to be rethrown - requires action callbacks and validation error shaper functions to be async (see [this](vercel/next.js#72336 (comment))). The minimum required Next.js version will be stable 15.1 and minimum React version will be 19. Older framework versions will not work with next-safe-action >= 7.10.0, and vice versa. ## Related issue(s) or discussion(s) - #288 - #299
Are you using the latest version of this library?
Is there an existing issue for this?
Describe the bug
I have no idea what it's about
Reproduction steps
I tested: it happens even without
use cache
orunstable_cache``. It happens in
canarybecause it does not happen in
15.0.3`:Expected behavior
no Error
Link to a minimal reproduction of the issue
https://codesandbox.io/p/devbox/keen-cloud-gggnf4
Operating System
Windows 11
Library version
7.9.9
Next.js version
15.0.4-canary.23-24
Node.js version
22.10.0
Additional context
No response
The text was updated successfully, but these errors were encountered: