WeSearch

How to Build an API-First Front End with OpenAPI, Orval, TanStack Query, Zod

The React Systems Newsletter· ·6 min read · 0 reactions · 0 comments · 41 views
How to Build an API-First Front End with OpenAPI, Orval, TanStack Query, Zod
TL;DR · WeSearch summary

The article discusses the importance of adopting an API-first approach in frontend development using tools like OpenAPI, Orval, TanStack Query, and Zod. It highlights how treating OpenAPI as a development asset rather than mere documentation can streamline the integration process between frontend and backend teams. By generating TypeScript models and API clients from OpenAPI specifications, developers can work more efficiently and reduce mismatches between expected and actual data structures.

Key facts
About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.

Original article
Hacker News (Newest) · The React Systems Newsletter
Read full at Hacker News (Newest) →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherHacker News (Newest)
Canonical URLhttps://reactdevelopment.substack.com/p/how-to-build-an-api-first-frontend
Publication timeWed, 27 May 2026 02:31:34 +0000
Retrieval time2026-05-27T02:37:56.185Z
Last seen2026-05-27T02:37:56.185Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Clusterm3mzJG0SxYZK · 2 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

How to Build an API-First Frontend with OpenAPI, Orval, TanStack Query, Zod, and Next.jsThe React Systems NewsletterMay 27, 2026ShareFrontend development has a repetitive problem that almost every team eventually rediscovers.You receive an API endpoint.Thanks for reading! Subscribe for free to receive new posts and support my work.SubscribeYou write:request functionsresponse typesReact hooksloading statesmutation handlersmocksvalidation logicThen the backend changes one field.Now:generated screenshots failUI forms breakstale interfaces lie to TypeScriptQA opens twelve ticketsThe larger the application becomes, the worse this cycle gets.The irony is that modern teams already possess something capable of solving a large part of this problem:the API contract.That contract usually exists as…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (Newest).

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments