Skip to content

chore: bump @dynamic-labs-sdk/* to ^1.4.0 and migrate renamed useWalletProviders hook#11

Open
matthew1809 wants to merge 3 commits into
mainfrom
devin/1779700067-bump-sdk-1.3.0
Open

chore: bump @dynamic-labs-sdk/* to ^1.4.0 and migrate renamed useWalletProviders hook#11
matthew1809 wants to merge 3 commits into
mainfrom
devin/1779700067-bump-sdk-1.3.0

Conversation

@matthew1809
Copy link
Copy Markdown
Collaborator

@matthew1809 matthew1809 commented May 25, 2026

Summary

Bumps every @dynamic-labs-sdk/* dependency from ^1.2.1 to ^1.4.0 and regenerates package-lock.json from the public npm registry (no JFrog URLs).

Range covered by this bump (dynamic-js-sdk CHANGELOG):

  • v1.4.0 (2026-05-26): WaaS Tron wired into addTronExtension
  • v1.3.0 (2026-05-22): getCheckoutTransactionQuote no longer requires fromTokenAddress for native tokens; new getWalletOptionsCatalogue on the client; multi-network support in getBalances; WaaS Tron wallet provider extension

One demo-side migration was required: in v1.3.0 the react-hooks hook useWalletProviders was renamed to useAvailableWalletProvidersData (it is no longer exported under the old name). The demo's local src/app/hooks/useWalletProviders.ts wrapper has been updated to re-export the new SDK hook as useWalletProviders so call sites elsewhere in the demo don't need to change.

vite build succeeds; npm run lint reports the same 4 pre-existing custom-rules/ban-ethereum-eth-terms rule-not-found errors as on main (the rule definition isn't installed in this repo) — no new lint errors introduced.

Review & Testing Checklist for Human

  • npm install from a clean clone and confirm the lockfile resolves cleanly against registry.npmjs.org (no JFrog URLs, no auth needed).
  • Run the demo (npm run dev) and spot-check that the wallet picker, login, and a couple of network operations still work after the bump — the useWalletProviders hook is what powers the wallet picker UI.

Notes

  • Lockfile was regenerated with npm install --userconfig=/dev/null --registry=https://registry.npmjs.org/ to bypass the host's JFrog .npmrc; the resulting package-lock.json has zero fbinfra555artifactory/JFrog references.
  • A new transitive @dynamic-labs-sdk/metamask@1.4.0 appears in the lockfile because the SDK now publishes that package; no direct dependency added to package.json.

Link to Devin session: https://app.devin.ai/sessions/5c935c83d66f4f3f82ffc24aab8e9e75
Requested by: @matthew1809

@devin-ai-integration
Copy link
Copy Markdown
Contributor

Original prompt from mfoyle

Check the JS SDK, and ensure the documentation, and the demo apps are up to date according to the latest release.

If anything is out of sync, check if there aren't existing PRs to update and if so, just ensure they have the changes needed and move on.

Provide only very brief, to the point responses.

If there are no PRs to bring docs up to date, create PRs to update them.
If there are no new PRs to be made, just say that and finish.

Interact only with the following repositories:

JS SDK:

Documentation:

Demo apps:

You only need to look in the following repos: dynamic-labs-oss/react-via-js-example-app, dynamic-labs/documentation, dynamic-labs/dynamic-js-sdk, dynamic-labs-oss/vue-via-js-example-app

@devin-ai-integration
Copy link
Copy Markdown
Contributor

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@semgrep-code-dynamic-labs-oss
Copy link
Copy Markdown

Semgrep found 12 block-public-registry-refs-in-package-lock findings:

package-lock.json contains a reference to a public package registry or CDN (https://registry.npmjs.org/@dynamic-labs-sdk/zerodev/-/zerodev-1.4.0.tgz). Dependencies must be resolved through the approved internal JFrog/Artifactory registry. Update your .npmrc to point at the approved registry, delete node_modules and package-lock.json, then re-run npm install and commit the regenerated lockfile.

@devin-ai-integration devin-ai-integration Bot changed the title chore: bump @dynamic-labs-sdk/* to ^1.3.0 chore: bump @dynamic-labs-sdk/* to ^1.4.0 and migrate renamed useWalletProviders hook May 27, 2026
Comment thread src/app/hooks/useWalletProviders.ts Outdated
@@ -1 +1 @@
export { useWalletProviders } from '@dynamic-labs-sdk/react-hooks';
export { useAvailableWalletProvidersData as useWalletProviders } from '@dynamic-labs-sdk/react-hooks';
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

lets not rename it. Keep the original name. This is an example, we shouldnt be doing anything out of the ordinary here

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.

Good call — dropped the local useWalletProviders.ts wrapper and updated the four call sites (AuthRoute, AuthProviderRoute, AttachSourceView, SelectLinkMethodView) to import useAvailableWalletProvidersData directly from @dynamic-labs-sdk/react-hooks. Build passes.

@matthew1809 matthew1809 requested a review from guiMendel May 29, 2026 15:25
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.

3 participants