Skip to content

feat: migrate starknetkit to starknet v9 and align connector types#252

Draft
dmcrodrigues wants to merge 1 commit intodevelopfrom
codex/starknetkit-starknet-v9
Draft

feat: migrate starknetkit to starknet v9 and align connector types#252
dmcrodrigues wants to merge 1 commit intodevelopfrom
codex/starknetkit-starknet-v9

Conversation

@dmcrodrigues
Copy link

Issue / feature description

Migrate starknetkit to Starknet v9 and align connector typing with the newer
starknet-react/starknet-start expectations, while keeping behavior and code
patterns unchanged.

Changes

  • Pin @starknet-io/get-starknet and @starknet-io/get-starknet-core to 4.0.8.
  • Update starknet dev dependency from ^8.5.2 to pinned 9.1.1.
  • Update starknet peer dependency from ^8.0.0 to >=9.0.0.
  • Align connector account(...) signatures to ProviderInterface plus optional
    PaymasterInterface across connector implementations.
  • Remove ProviderOptions usage from connector type definitions.
  • Update pnpm-lock.yaml to match pinned dependency versions and Starknet v9
    resolution.
  • Apply minimal type-safety follow-ups required by current TS settings (import type usage and required modal props), without changing runtime behavior.
  • Validate with:
    • pnpm install --frozen-lockfile --ignore-scripts
    • pnpm run check
    • pnpm run build

Checklist

  • Rebased to the last commit of the target branch (or merged)
  • Code self-reviewed
  • Code self-tested
  • Tests updated (if needed)
  • All tests are passing locally

@dmcrodrigues dmcrodrigues self-assigned this Feb 11, 2026
Copy link
Member

@Cussone Cussone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. It's best to test it manually so we are 100% sure there is no weird stuff. We can release it under a tag.

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