Error message update

[karamba228]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
score-site	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 17, 2025 3:38pm

[srossross]

1. Can this come from the backend? the response should be a 404 from the fetchScore
2. please don;t use regex for error handling, use custom error classes

[srossross]

Please instead check the return value of the fetch when it is not a 200 for the error field

[karamba228]

I tried this approach and while it works fine in dev it does not work in prod. React has a security feature that omits showing the actual error message, instead of the error message you will get
An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included in this error instance which may provide additional details about the nature of the error.

[srossross]

Please look at the nextjs docs for handling server errors with error.js - https://nextjs.org/docs/app/api-reference/file-conventions/error#learn-more-about-error-handling

it looks like the functionality is limited to prevent leaking server data in production.

I would instead return { status: "ecosystem_not_found" } not throw an error

then in the page server component you can do

if (status === "not_found") {
      notFound();
}

if (status === "ecosystem_not_found") {
      return ... custom component to tell the user 
}

[srossross]

also, for your own education - please look into if (!(ecosystem in ({} as EcosystemDestination))) { this expression, this is quite flawed this is the equivalent of writing if "foo" in {} which will never be true