vimzh cba67a55ed fix(onboarding): fail fast with a clear error when EXA_API_KEY is missing ... The route previously fell back to "x-api-key": process.env.EXA_API_KEY ?? "", so a missing env var produced an outbound call to Exa with an empty key. Exa returned an auth failure, which was then surfaced to the client as a generic 500 "Failed to fetch content from Exa API" — making missing configuration indistinguishable from upstream errors and slowing self-hosted setup. Read EXA_API_KEY once at the top of the handler, log a specific message when it's absent, and return a 500 with a clear "service is not configured" error. The downstream fetch now uses the validated, non-empty key directly.		2026-05-24 11:45:05 +05:30
..
emails/welcome	chore: improve the codebase with react doctor (#917)	2026-05-09 19:12:01 +00:00
og	(probable fix) 500 error on og endpoint	2026-01-23 18:57:14 -07:00
onboarding	fix(onboarding): fail fast with a clear error when EXA_API_KEY is missing	2026-05-24 11:45:05 +05:30