Skip to content

feat!: upgrade to @seamapi/http v2 and drop @seamapi/types - #19

Merged
razor-x merged 4 commits into
mainfrom
claude/seam-http-client-upgrade-fkdx7f
Aug 13, 2026
Merged

feat!: upgrade to @seamapi/http v2 and drop @seamapi/types#19
razor-x merged 4 commits into
mainfrom
claude/seam-http-client-upgrade-fkdx7f

Conversation

@razor-x

@razor-x razor-x commented Aug 13, 2026

Copy link
Copy Markdown
Member

@seamapi/http v2 vendors the API types directly, so ActionAttempt is now
imported from the package root instead of @seamapi/types/connect, and
@seamapi/types is removed from both peerDependencies and devDependencies.

BREAKING CHANGE: @seamapi/http ^2.5.0 is now required as a peer dependency.
The isUndocumentedApiEnabled option was removed upstream in v2, so it is no
longer accepted by SeamQueryProvider.

SeamHttpEndpoints.fromClient no longer accepts client-construction options in
v2; the endpoint is already bound to the client being passed in, so the
argument is dropped.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01Fomny7NLXuNediSKrgmbTH

@seamapi/http v2 vendors the API types directly, so ActionAttempt is now
imported from the package root instead of @seamapi/types/connect, and
@seamapi/types is removed from both peerDependencies and devDependencies.

BREAKING CHANGE: @seamapi/http ^2.5.0 is now required as a peer dependency.
The isUndocumentedApiEnabled option was removed upstream in v2, so it is no
longer accepted by SeamQueryProvider.

SeamHttpEndpoints.fromClient no longer accepts client-construction options in
v2; the endpoint is already bound to the client being passed in, so the
argument is dropped.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fomny7NLXuNediSKrgmbTH
@vercel

vercel Bot commented Aug 13, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
react-query Ready Ready Preview Aug 13, 2026 10:04pm

Request Review

Passing client-construction options to SeamHttpEndpoints.fromClient throws
SeamHttpInvalidOptionsError ("The client option cannot be used with any other
option, but received: endpoint"), since the endpoint is already bound to the
axios client being handed in. Setting the endpoint prop on SeamQueryProvider
therefore left both clients null.

The endpoint is still applied where it always was, when constructing the
SeamHttp instance, and carries over to the endpoint client through the shared
axios instance.

Resolve tsconfig paths in vitest so tests exercise src rather than resolving
the package self-reference to build output, which is absent in CI.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fomny7NLXuNediSKrgmbTH
This reverts commit 3a3938e.

Keeps the branch scoped to the @seamapi/http v2 upgrade.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fomny7NLXuNediSKrgmbTH
Vitest resolved @seamapi/react-query through the package self-reference in
exports, loading build output instead of src. That output is gitignored and
absent in CI, where npm test runs without a build step.

Mirror the tsconfig paths as explicit Vitest aliases.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fomny7NLXuNediSKrgmbTH
@razor-x
razor-x merged commit 3c48362 into main Aug 13, 2026
14 checks passed
@razor-x
razor-x deleted the claude/seam-http-client-upgrade-fkdx7f branch August 13, 2026 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants