Create twenty-olives-admire.md#1
Open
Dargon789 wants to merge 382 commits into
Open
Conversation
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
feat(connectors): add getPortoInstance method
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* Bump to latest base account * Remove fastestsmallesttextencoderdecoder * chore: up * chore: changeset --------- Co-authored-by: KodiKraig <cody.craig@aol.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Correct useBlockNumber example in migration docs
…4854) * feat(docs): add useSimulateContract + useWriteContract example * chore: up --------- Co-authored-by: Tom Meagher <tom@meagher.co>
* docs: fix typo showCalls -> sendCalls * docs: correct viem reference urls
…tion (wevm#4866) * feat(react): add functionHooks option to control per-function hook generation * chore: release version 2.8.0 with functionHooks option for react plugin * chore: tweaks --------- Co-authored-by: Tom Meagher <tom@meagher.co>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…ce unnecessary query invalidations (wevm#4872) * fix: compute proper chainId value on useReadConstracts to avoid unnecessary queryKey mutations Derives a unified chainId from contracts when all share the same value, otherwise falls back to the default (chainId from useChainId). This fixes 'queryKey' mutation when connecting or changing network despite all contracts sharing the same chainId, avoid unnecessary mutations and equating to the default behaviour on useReadContract. * refactor: clean up logic --------- Co-authored-by: agsola <git@agsola.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* feat(solid): add important contract related missing primitives * chore: export and type issues * chore: up * chore: changeset * chore: up * chore: up --------- Co-authored-by: tmm <tmm@tmm.dev>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* feat: wallet hooks * Update tidy-timers-tap.md * chore: upgrade viem to 2.48.11 Amp-Thread-ID: https://ampcode.com/threads/T-019e04b0-15f0-729d-8aa1-89d62b582ab9 * test(tempo): add wallet action and hook tests Amp-Thread-ID: https://ampcode.com/threads/T-019e04b0-15f0-729d-8aa1-89d62b582ab9 * chore: update viem version in test snapshots Amp-Thread-ID: https://ampcode.com/threads/T-019e04b0-15f0-729d-8aa1-89d62b582ab9 * chore: bump axios, hono, simple-git, nitropack overrides for security advisories Amp-Thread-ID: https://ampcode.com/threads/T-019e04b0-15f0-729d-8aa1-89d62b582ab9 * ci: bump viem matrix version to 2.48.11 Amp-Thread-ID: https://ampcode.com/threads/T-019e04b0-15f0-729d-8aa1-89d62b582ab9 * test: update blockTimestamp snapshot to bigint format Amp-Thread-ID: https://ampcode.com/threads/T-019e04b0-15f0-729d-8aa1-89d62b582ab9 * ci: bump test job timeout to accommodate tempo browser tests Amp-Thread-ID: https://ampcode.com/threads/T-019e0631-3a5f-726f-b224-7c2df980963c * docs(tempo): add wallet action and hook docs Amp-Thread-ID: https://ampcode.com/threads/T-019e0631-3a5f-726f-b224-7c2df980963c * test: bump tempo hookTimeout to 40s Amp-Thread-ID: https://ampcode.com/threads/T-019e0631-3a5f-726f-b224-7c2df980963c
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…evm#5107) fix(connectors): widen @metamask/connect-evm peer-dep range to ^1.0.0 Allows consumers to pick up non-breaking 1.x releases of @metamask/connect-evm (and the connect-multichain bundle-size improvements they bring in transitively) without manual overrides.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* fix(tempo): hand viem the root account in connector.getClient The Tempo connectors were forwarding the access-key flavored account into viem's transaction prep, which leaked access-key state into call sites that should always operate against the root account. `getClient` now passes `accessKey: false` so viem sees the root account; the SDK provider continues to perform access-key orchestration internally before signing. The `signable` setup parameter is unused after this change and has been removed. Amp-Thread-ID: https://ampcode.com/threads/T-019e1503-5215-736f-a35a-292777404768 * fix(tempo): deprecate `signable` setup parameter instead of removing it Amp-Thread-ID: https://ampcode.com/threads/T-019e1503-5215-736f-a35a-292777404768 * docs: shorten `signable` deprecation comment Amp-Thread-ID: https://ampcode.com/threads/T-019e1503-5215-736f-a35a-292777404768 * refactor(tempo): drop `signable: true` from connectors and tighten changeset Amp-Thread-ID: https://ampcode.com/threads/T-019e1503-5215-736f-a35a-292777404768 * docs: 'access-key' -> 'access key' * docs: split changesets and prefix with `viem/tempo`: Amp-Thread-ID: https://ampcode.com/threads/T-019e1503-5215-736f-a35a-292777404768 * docs: drop `signable` deprecation changeset * chore: bump accounts to 0.10.1 and hono override to 4.12.18 Amp-Thread-ID: https://ampcode.com/threads/T-019e158b-b5d1-746e-8072-aa11a2b0897a * feat(tempo): drop signable, forward config transports to accounts provider Amp-Thread-ID: https://ampcode.com/threads/T-019e158b-b5d1-746e-8072-aa11a2b0897a * revert: restore signable in zone.getSignableConnectorAccount Amp-Thread-ID: https://ampcode.com/threads/T-019e158b-b5d1-746e-8072-aa11a2b0897a * docs: scope signable changeset to @wagmi/core Amp-Thread-ID: https://ampcode.com/threads/T-019e158b-b5d1-746e-8072-aa11a2b0897a * ci: pin foundry to v1.7.1 Amp-Thread-ID: https://ampcode.com/threads/T-019e158b-b5d1-746e-8072-aa11a2b0897a * up * Revert "ci: pin foundry to v1.7.1" Amp-Thread-ID: https://ampcode.com/threads/T-019e158b-b5d1-746e-8072-aa11a2b0897a * ci: pin foundry to v1.7.1 Amp-Thread-ID: https://ampcode.com/threads/T-019e158b-b5d1-746e-8072-aa11a2b0897a * Revert "ci: pin foundry to v1.7.1" Amp-Thread-ID: https://ampcode.com/threads/T-019e158b-b5d1-746e-8072-aa11a2b0897a * ci: pin foundry to nightly-9afdb72 Amp-Thread-ID: https://ampcode.com/threads/T-019e15d2-5a24-771f-8ef1-ac2b5fbc363c * ci: revert foundry pin to nightly Amp-Thread-ID: https://ampcode.com/threads/T-019e15d2-5a24-771f-8ef1-ac2b5fbc363c
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* fix(tempo): always provide JSON-RPC account in connector getClient Amp-Thread-ID: https://ampcode.com/threads/T-019e188c-e68b-7255-b2b9-b7af1af157d4 * refactor(tempo): use viem `parseAccount` for JSON-RPC account Amp-Thread-ID: https://ampcode.com/threads/T-019e188c-e68b-7255-b2b9-b7af1af157d4
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* fix: handle malformed cookie initial state * chore: add changeset * chore: tweaks --------- Co-authored-by: tmm <tmm@tmm.dev>
* refactor(tempo): rename `wallet.send` to `wallet.transfer` - Rename `Actions.wallet.send` to `Actions.wallet.transfer`. - Rename `Hooks.wallet.useSend` to `Hooks.wallet.useTransfer`. - Reshape parameters to match viem's discriminated `editable` union: default mode requires `amount`, `to`, `token`. Pass `editable: true` to open the wallet UI with optional pre-filled fields. - Bump `viem` to 2.49.2 (required for `Actions.wallet.transfer`). - Bump `accounts` peer dep to `~0.12`. - Update site docs and sidebar. Amp-Thread-ID: https://ampcode.com/threads/T-019e294e-3d74-70e5-a770-d4de2687da00 * docs(tempo): use `pathUSD` symbol in `wallet.transfer` JSDoc examples Amp-Thread-ID: https://ampcode.com/threads/T-019e294e-3d74-70e5-a770-d4de2687da00 * test: update viem version snapshots from 2.48.11 to 2.49.2 Amp-Thread-ID: https://ampcode.com/threads/T-019e294e-3d74-70e5-a770-d4de2687da00 * audit * chore: add devalue to minimumReleaseAgeExclude Amp-Thread-ID: https://ampcode.com/threads/T-019e29b7-bf59-70e6-9c62-8933f60f8d70 * chore: format Amp-Thread-ID: https://ampcode.com/threads/T-019e29b7-bf59-70e6-9c62-8933f60f8d70 * Rename wallet actions and update peer dependency Renamed wallet actions and hooks for clarity. Updated peer dependency for accounts.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* bump connect-evm 1.3.0 * bump connect-evm 1.3.1
…r when SDK unloaded (wevm#5128) * fix(connectors): metaMask serves probe methods from EIP-6963 provider when SDK unloaded `metaMask`'s `getProvider`, `isAuthorized`, `getAccounts`, and `getChainId` now short-circuit through the EIP-6963 (MIPD) MetaMask provider that wagmi's config already discovers, when one is announced and the SDK has not yet been loaded. This avoids paying the `@metamask/connect-evm` (and transitive `@metamask/connect-multichain`) chunk download/parse cost on every page load via `reconnect()` for users who have the MetaMask extension installed but have not yet user-initiated a connection through this connector. User-initiated `connect()` is unchanged — it still goes through the SDK, so one-tap flows (`connectAndSign`, `connectWith`), `switchChain` auto-fallback with `chainConfiguration`, MWP/mobile transports, analytics, and event wiring are preserved exactly. Once `connect()` runs and `metamask` is set, all subsequent calls go through the SDK — no provider-instance flip-flop, no event-listener splitting. Falls through to the existing SDK path when MIPD is disabled, no MetaMask EIP-6963 announcement is present (e.g. mobile-web with no in-app browser), or in SSR. The helper accesses `config._internal.mipd` via a narrow runtime cast because the connector-facing `config` type does not expose `_internal`. This avoids touching the shared connector API surface in this PR; if maintainers prefer, the access could be formalized later. * fix(connectors): avoid MetaMask SDK import for extension probes Serve pre-connect MetaMask probe methods from an announced EIP-6963 provider instead of reaching for wagmi core internals. Keep user-initiated connect and all calls after SDK loading on the SDK path to avoid provider flip-flop. Add regression coverage for pre-connect probes, unauthorized reconnect, SDK fallback, and explicit connect. * refactor(connectors): drop redundant watchInjectedMetaMaskProvider call `setup()` already primes the watcher, so the call inside `findInjectedMetaMaskProvider` is a no-op after the first invocation and adds noise to the lifecycle. Drop it and document where the cache gets primed. Per review feedback from @jiexi on wevm#5109. * refactor: wire mipd providers from config to connector fn * docs: up --------- Co-authored-by: Alex Mendonca <alex.mendonca@consensys.net> Co-authored-by: tmm <tmm@tmm.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.