Skip to content

Fix TypeScript peer dependency requirement - #33

Open
huklaa wants to merge 1 commit into
farcasterxyz:mainfrom
huklaa:fix-17-remove-typescript-peer
Open

huklaa wants to merge 1 commit into
farcasterxyz:mainfrom
huklaa:fix-17-remove-typescript-peer

Conversation

@huklaa

@huklaa huklaa commented Sep 27, 2026

Copy link
Copy Markdown

Fixes #17

The published client currently requires consumers to provide exactly TypeScript 5.8.3, even though it runs as JavaScript and TypeScript is only needed to build this package. Move the unchanged compiler version from peerDependencies to devDependencies and update its workspace lockfile classification.

This keeps the fix scoped to the client manifest and lockfile. #32 is a broader workspace/dependency rewrite; this PR does not include its unrelated changes.

Validation on the existing branch:

  • All 23 client tests passed.
  • Client typecheck, ESM/CJS build and npm pack --dry-run passed.
  • Package manifest has no TypeScript peer dependency; git diff --check passed.
  • Current upstream comparison: 0 behind, 1 ahead. Rechecked issue comments, assignees, open PRs and visible candidate branches before submission.

The runtime is Node 24.19.0; the workspace advertises Node 23.x. Tests/build were run with the package npm scripts after dependencies were installed; pnpm 11's install exited on ignored dependency build scripts.

Keep TypeScript as a development-only tool so JavaScript consumers no longer receive peer dependency warnings while preserving the package build and typecheck toolchain.

Fixes farcasterxyz#17
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.

Typescript should be removed from the peer dependencies

1 participant