Repository navigation
Replace legacy Wallets Kit v1 references in current tutorials #2609
Description
Activity
Fresh Raven re-check on 2026-07-15 narrows this issue: the former Spanish
i18n/es/.../dapp-frontend.mdxpath is no longer present onmain, so that translation residual is resolved by removal. The English Example Application tutorial still installs@creit.tech/stellar-wallets-kitand retains that scope inssr.noExternal(docs/build/apps/example-application-tutorial/overview.mdx, current lines 199 and 254). Remaining requested action is English-only: update or explicitly pin/label that example.Shipped a docs-side stopgap in #2659: pinned the tutorial's Wallets Kit install to
@^1so it stops breaking against the v1 companion app.Keeping this open for the durable fix — migrating both this tutorial and
stellar/basic-payment-appto the Kit v2 API (StellarWalletsKit.init/defaultModules) in lockstep, which is the cross-repo work.One correction for the record: the npm scope is not legacy-v1-only — v2.5.0 also publishes to
@creit.tech, which is exactly why the unpinned install broke.- added a commit that references this issue
on Jul 21, 2026 You're right, and our issue was wrong on that point. We re-checked the npm registry:
@creit.tech/stellar-wallets-kithas dist-taglatest=2.5.0(published 2026-06-29), so the dotted npm scope is emphatically not v1-only and "legacy scope" was the wrong diagnosis. The actual defect is the one you identified — an unpinned install resolving to v2 against tutorial code written for the v1 constructor API.We've corrected our record and the matching record we filed against the dapp skill, so neither now describes this as a scope problem.
The
@^1pin in #2659 looks like the right interim state. Agreed the durable fix is migrating this tutorial andstellar/basic-payment-apptoStellarWalletsKit.init/defaultModulesin lockstep — happy to re-verify once that lands.
Metadata
Metadata
Assignees
Type
Projects
- Status
Finding
Two current Docs tutorial surfaces still teach the legacy Wallets Kit v1 package
or API. The English Example Application tutorial installs
@creit.tech/stellar-wallets-kitand includes that legacy scope in its Vite SSRconfiguration. The Spanish
dapp-frontendtranslation goes further: it installsand imports the legacy scope and uses
new StellarWalletsKit(...)withallowAllModules().The current maintained package is the JSR v2 package
@creit-tech/stellar-wallets-kit(latest 2.5.0). Its current initializationguidance uses static
StellarWalletsKit.init(...)withdefaultModules()orexplicitly selected modules. The English
dapp-frontendsource no longer has aWallets Kit example, so the Spanish page is also an untranslated obsolete
section rather than a current English counterpart.
Evidence
Live source re-check on 2026-07-14:
The Wallet Integration page at
https://developers.stellar.org/docs/tools/developer-tools/wallets was separately
checked. It only links to the maintained Kit site and contains no package or
API example; it is deliberately excluded from this finding.
Additional recorded evidence:
Recommendation
Update the Example Application tutorial's dependency and Vite configuration to
the current supported Wallets Kit path, and either remove the obsolete Spanish
Wallets Kit section or translate a current v2 example. A retained example should
use the JSR v2 package and static initialization with
defaultModules()orexplicit module selection; if either tutorial must remain a v1 historical
example, label it clearly as legacy and pin that version rather than presenting
it as current integration guidance.
Source Record
This was found by the downstream Raven eval/improvements loop and recorded as sd-035 (stellar-docs, discovered 2026-07-11).
Public source record: improvements/stellar-docs/sd-035-wallets-kit-jsr-package-api-drift.md
Immutable source snapshot: b9098a92cab9
Resolution Handoff
When a fix is deployed, please link the resolving issue or PR to the source record above and notify Raven through:
https://github.com/kalepail/stellar-raven/issues/new?template=upstream-improvement-ready.yml&title=%5Bupstream-ready%5D%20sd-035%3A%20
Include the finding id, resolving issue/PR, deployed version or timestamp, and the smallest live recheck. Raven independently verifies the upstream surface before changing the finding to
fixed-upstream; issue closure or a merged PR alone is not treated as proof. After a distinct reviewer repeats the live check, the active finding is retired to Raven's resolved ledger while the immutable snapshot remains available.