fix(landing): resolve error-page crash on invalid /models and /integrations routes

[waleedlatif1]

Summary

• Invalid URLs under /models/* and /integrations/* were rendering "Application error: a client-side exception has occurred" instead of the styled 404.
• Root cause is a React/Next.js interaction: React skips SSR on server errors and re-renders on the client (React 18 RFC, vercel/next.js#63980, #82456). Root-layout scripts — including the runtime env script that populates window.__ENV — get inserted into the DOM but are not executed on that client re-render. Any client module that reads env at module evaluation (lib/auth/auth-client.ts → getBaseUrl()) throws and cascades the render into the error overlay.

Changes

1. lib/auth/auth-client.ts — fall back to window.location.origin when getBaseUrl() throws on the client. Auth endpoints are same-origin, so this is the correct baseURL on the client. Server-side still throws on genuine misconfig, so webhooks/callbacks continue to surface misconfiguration loudly.
2. Three loading.tsx files at /models/[provider], /models/[provider]/[model], and /integrations/[slug] — establishes a Suspense boundary below the root layout so a page-level notFound() stops invalidating the layout's SSR output. This is the fix endorsed by Next.js maintainer lubieowoce in #63980.

Type of Change

• Bug fix

Testing

Tested manually — invalid /models/* and /integrations/* URLs now render the styled 404 without the client-side exception overlay. Valid pages unchanged.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 21, 2026 7:29pm

[cursor]

PR Summary

Medium Risk
Touches auth client initialization by changing how baseURL is derived; mistakes could break sign-in flows or point auth calls at the wrong origin. The new loading.tsx Suspense boundaries are low risk but affect route rendering behavior.

Overview
Fixes a landing-page crash where invalid /models/* and /integrations/* URLs could trigger a client-side exception instead of the styled 404.

Updates lib/auth/auth-client.ts to compute the auth baseURL via getAuthBaseUrl(), falling back to window.location.origin on the client when getBaseUrl() throws (while still surfacing misconfiguration on the server).

Adds loading.tsx to the /models/[provider], /models/[provider]/[model], and /integrations/[slug] routes to introduce a lower-level Suspense boundary, preventing server errors/notFound() from invalidating the root layout render.

^{Reviewed by Cursor Bugbot for commit 51b5ee9. Configure here.}

[greptile-apps]

Greptile Summary

This PR fixes a client-side crash on invalid /models/* and /integrations/* routes by (1) adding a fallback to window.location.origin in getAuthBaseUrl() when window.__ENV is not populated during client-side re-render, and (2) adding loading.tsx files to establish Suspense boundaries so page-level notFound() no longer invalidates the root layout's SSR output.

Confidence Score: 5/5

Safe to merge — targeted, well-scoped bug fix with no new risk surface.

All four changed files are correct and minimal. The auth fallback only activates on the client when the env script hasn't run (the exact crash scenario), and the server-side path still throws on genuine misconfiguration. The loading.tsx files are boilerplate Suspense boundaries that follow existing project patterns. No P0/P1 issues found.

No files require special attention.

Important Files Changed

Filename	Overview
apps/sim/lib/auth/auth-client.ts	Adds getAuthBaseUrl() wrapper that falls back to window.location.origin on the client when getBaseUrl() throws due to missing window.__ENV; server-side behaviour preserved.
apps/sim/app/(landing)/integrations/[slug]/loading.tsx	New loading.tsx establishing a Suspense boundary for the integration detail route; minimal and correct.
apps/sim/app/(landing)/models/[provider]/loading.tsx	New loading.tsx establishing a Suspense boundary for the model provider route; minimal and correct.
apps/sim/app/(landing)/models/[provider]/[model]/loading.tsx	New loading.tsx establishing a Suspense boundary for the model detail route; minimal and correct.

Sequence Diagram

sequenceDiagram
    participant Browser
    participant NextJS as Next.js (SSR)
    participant RootLayout as Root Layout
    participant Page as [slug]/page.tsx
    participant Loading as [slug]/loading.tsx (new)

    Browser->>NextJS: GET /models/invalid-provider
    NextJS->>RootLayout: Render layout (runs env script)
    RootLayout->>Loading: Render Suspense boundary (loading.tsx)
    Loading-->>Browser: Show spinner immediately
    NextJS->>Page: Render page → notFound() thrown
    Note over Page,Loading: notFound() is caught at Suspense boundary,<br/>not propagated to root layout
    Page-->>Browser: Render styled 404 page

    Note over Browser,Loading: Before fix: notFound() escaped Suspense,<br/>invalidated SSR, client re-render skipped env script,<br/>getBaseUrl() threw → crash overlay

Loading

_{Reviews (3): Last reviewed commit: "improvement(landing): use emcn Loader in..." | Re-trigger Greptile}

[waleedlatif1]

@cursor review

[waleedlatif1]

@greptile

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 7dfbe69. Configure here.}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 51b5ee9. Configure here.}