vrr/eigent
2
0
Fork 0
mirror of https://github.com/eigent-ai/eigent.git synced 2026-04-29 04:00:09 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

chore: fix pre commit format and pipeline issue (#1144)

Browse source
This commit is contained in:
Wendong-Fan 2026-02-04 00:06:29 +00:00 • committed by GitHub
parent 2256497dff
commit 893f51fc82
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
970 changed files with 11235 additions and 9533 deletions
Download patch file Download diff file Expand all files Collapse all files

8
package/@stackframe/stack-shared/dist/esm/utils/react.js vendored
View file

@ -35,9 +35,9 @@ var NoSuspenseBoundaryError = class extends Error {
constructor(options) {
super(deindent`
${options.caller ?? "This code path"} attempted to display a loading indicator, but didn't find a Suspense boundary above it. Please read the error message below carefully.
The fix depends on which of the 3 scenarios caused it:
1. You are missing a loading.tsx file in your app directory. Fix it by adding a loading.tsx file in your app directory.
2. The component is rendered in the root (outermost) layout.tsx or template.tsx file. Next.js does not wrap those files in a Suspense boundary, even if there is a loading.tsx file in the same folder. To fix it, wrap your layout inside a route group like this:
@ -51,7 +51,7 @@ var NoSuspenseBoundaryError = class extends Error {
- - - the rest of your app
For more information on this approach, see Next's documentation on route groups: https://nextjs.org/docs/app/building-your-application/routing/route-groups
3. You caught this error with try-catch or a custom error boundary. Fix this by rethrowing the error or not catching it in the first place.
See: https://nextjs.org/docs/messages/missing-suspense-with-csr-bailout
@ -75,4 +75,4 @@ export {
suspend,
suspendIfSsr
};
//# sourceMappingURL=react.js.map
//# sourceMappingURL=react.js.map