[Issue #1823]: Fix prod FE error

[rylew1]

Summary

Fixes #1823

Time to review: 5 min

Changes proposed

• Add error handling when we have invalid JSON returned (when API is up but not endpoints are enabled)

Error we can simulate locally (same thing on prod):

Throwing error:  Not Found 404 {
  query: '',
  status: Set(0) {},
  fundingInstrument: Set(0) {},
  eligibility: Set(0) {},
  agency: Set(0) {},
  category: Set(0) {},
  sortby: null,
  page: 1,
  actionType: 'initialLoad'
}
Error fetching opportunities: T [Error]: {"type":"NotFoundError","searchInputs":{"query":"","status":[],"fundingInstrument":[],"eligibility":[],"agency":[],"category":[],"sortby":null,"page":1,"actionType":"initialLoad"},"message":"Unknown Error","status":404}
    at L (/Users/ryan/Desktop/simpler-grants-gov/frontend/.next/server/app/search/page.js:18:93101)
    at /Users/ryan/Desktop/simpler-grants-gov/frontend/.next/server/app/search/page.js:18:92757
    at H.sendRequest (/Users/ryan/Desktop/simpler-grants-gov/frontend/.next/server/app/search/page.js:18:92783)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async H.request (/Users/ryan/Desktop/simpler-grants-gov/frontend/.next/server/app/search/page.js:18:92406)
    at async H.searchOpportunities (/Users/ryan/Desktop/simpler-grants-gov/frontend/.next/server/app/search/page.js:18:93571)
    at async V.fetchOpportunities (/Users/ryan/Desktop/simpler-grants-gov/frontend/.next/server/app/search/page.js:18:94560)
    at async z (/Users/ryan/Desktop/simpler-grants-gov/frontend/.next/server/app/search/page.js:18:152457)
T [Error]: {"type":"NotFoundError","searchInputs":{"query":"","status":[],"fundingInstrument":[],"eligibility":[],"agency":[],"category":[],"sortby":null,"page":1,"actionType":"initialLoad"},"message":"Unknown Error","status":404}
    at L (/Users/ryan/Desktop/simpler-grants-gov/frontend/.next/server/app/search/page.js:18:93101)
    at /Users/ryan/Desktop/simpler-grants-gov/frontend/.next/server/app/search/page.js:18:92757
    at H.sendRequest (/Users/ryan/Desktop/simpler-grants-gov/frontend/.next/server/app/search/page.js:18:92783)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async H.request (/Users/ryan/Desktop/simpler-grants-gov/frontend/.next/server/app/search/page.js:18:92406)
    at async H.searchOpportunities (/Users/ryan/Desktop/simpler-grants-gov/frontend/.next/server/app/search/page.js:18:93571)
    at async V.fetchOpportunities (/Users/ryan/Desktop/simpler-grants-gov/frontend/.next/server/app/search/page.js:18:94560)
    at async z (/Users/ryan/Desktop/simpler-grants-gov/frontend/.next/server/app/search/page.js:18:152457)
[Error: 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 on this error instance which may provide additional details about the nature of the error.] {
  digest: '1277226382'
}

[andycochran]

Was this left in by mistake?

[rylew1]

Yes - I want it to show in server logs. But there's still some problems with this PR so I need to commit some different changes @andycochran

[andycochran]

This won't set the var to falsey?

[rylew1]

I had thought we might be able to just pass the error status code and type to the client error boundary component (error.tsx) - but it appears in a built version of the site it won't even let you pass the error message properly (or at least I need to do some further investigation as to why)

This PR unblocks analytics a bit but there's still a lingering question:

• Why can't the built site make proper calls to the API?

[coilysiren]

Approving again since it looks like Andy originally approved earlier