Skip to content

refactor(wallets): use @hub3js namespace packages over wallets-core#1445

Merged
llawliet-l-l merged 1 commit into
nextfrom
refactor/RC-327-use-hub3js-xrpl-tvm-sui-stellar-starknet
Jul 22, 2026
Merged

refactor(wallets): use @hub3js namespace packages over wallets-core#1445
llawliet-l-l merged 1 commit into
nextfrom
refactor/RC-327-use-hub3js-xrpl-tvm-sui-stellar-starknet

Conversation

@llawliet-l-l

@llawliet-l-l llawliet-l-l commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Summary

Migrates the repo to consume the standalone @hub3js/* namespace packages instead of @rango-dev/wallets-core's namespaces/* subpaths. Five namespaces move to hub3js (starknet, stellar, sui, ton→tvm, xrpl); utxo and tron stay on @rango-dev/wallets-core

Changes

  • Repoint namespace imports to hub3js: wallets-core/namespaces/{starknet,stellar,sui,ton,xrpl}@hub3js/{starknet,stellar,sui,tvm,xrpl} (ton maps to @hub3js/tvm).
  • Leave wallets-core/namespaces/{utxo,tron}, /legacy, /utils, and /dist/legacy/* on @rango-dev/wallets-core.
  • Update @hub3js/* dependencies to their latest npm versions across 39 package.json files: core@^0.61.0, std@^0.2.0, evm/solana@^0.3.0, starknet/stellar/sui/tvm/xrpl/namespaces@^0.2.0.

Checklist:

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • Implemented a user interface (UI) change, referencing our Figma design to ensure pixel-perfect precision.

Comment thread queue-manager/rango-preset/package.json
Comment thread wallets/provider-all/package.json
Comment thread wallets/provider-binance/package.json
Comment thread wallets/provider-bitget/package.json
Comment thread wallets/provider-braavos/package.json
Comment thread wallets/react/src/hub/helpers.ts
Comment thread widget/embedded/package.json
@arlert-armin

Copy link
Copy Markdown
Contributor

Could you also update the readme as part of this migration? Scope is a single file: wallets/core/readme.md. Everything else should stay as-is — the providers, wallets-react and wallets-shared all still live in this repo, so their readmes shouldn't point away.

Suggestion: add a deprecation banner + an import mapping table to wallets/core/readme.md, pointing at https://github.com/rango-exchange/hub3js

Old New
@rango-dev/wallets-core @hub3js/core
.../store @hub3js/core/store
.../utils @hub3js/core/utils
.../namespaces/common @hub3js/namespaces + @hub3js/std
.../namespaces/evm @hub3js/evm
.../namespaces/solana @hub3js/solana
.../namespaces/starknet @hub3js/starknet
.../namespaces/stellar @hub3js/stellar
.../namespaces/sui @hub3js/sui
.../namespaces/ton @hub3js/tvm
.../namespaces/xrpl @hub3js/xrpl
.../namespaces/tron, /utxo, /cosmos, /legacy not migrated yet — still served from this package

Two notes that affect the wording:

  • The deprecation isn't complete yet. @hub3js/tron and @hub3js/utxo only exist as 0.0.0-experimental-* on npm, there's no @hub3js/cosmos, and legacy has no counterpart — meanwhile 216 imports of @rango-dev/wallets-core/legacy and 82 of .../namespaces/utxo are still in the tree. So the banner should read "moved, migration in progress" rather than implying the package is dead.
  • @hub3js/tvm is the TON package (used by provider-tonconnect and wallets/react), not Tron — easy to get backwards in a mapping table.

@arlert-armin arlert-armin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@llawliet-l-l
llawliet-l-l force-pushed the refactor/RC-327-use-hub3js-xrpl-tvm-sui-stellar-starknet branch from 4dd7f9f to b0446d2 Compare July 22, 2026 14:10
@llawliet-l-l
llawliet-l-l merged commit 7ec3407 into next Jul 22, 2026
8 checks passed
@llawliet-l-l
llawliet-l-l deleted the refactor/RC-327-use-hub3js-xrpl-tvm-sui-stellar-starknet branch July 22, 2026 14:19
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