[chybisov]

Which Linear task is linked to this PR?

No ticket yet.

Why was it implemented this way?

This PR changes only examples/node. The root workspace does not change.

@lifi/sdk-provider-ethereum 4.2.11 fixes the shared-poll problem with viem 2.57.5 and later. It asks for viem ^2.57.7. This PR moves the Node example to these versions. The example now uses viem 2.57.7 safely. The PR also moves the example to pnpm 12.14.0.

Version changes

Package	Old	New	Reason
@lifi/sdk-provider-ethereum	4.2.10	4.2.11	Provider release with the shared-poll fix
viem	2.57.4	2.57.7	The provider 4.2.11 range (^2.57.7)
ox (transitive)	0.14.54	0.14.56	viem 2.57.7 pins ox 0.14.56 exactly
pnpm (packageManager)	12.11.2	12.14.0	The latest pnpm release

@lifi/sdk stays at 4.12.1. The provider pins it exactly. pnpm outdated in examples/node shows no outdated package.

pnpm

• packageManager is now pnpm@12.14.0+sha512.c18ba6d8…89a6. The hash is the hex form of the dist.integrity value from npm view pnpm@12.14.0. The old 12.11.2 value uses the same method.
• pnpm 12.14.0 was published on 2026-10-15 13:39 UTC. It is older than 24 h.
• The root workspace still uses pnpm 12.11.2. PR chore: bump pnpm to 12.14.0 and refresh release-age excludes #527 moves the root to 12.14.0.

Lockfile

• I removed examples/node/pnpm-lock.yaml and examples/node/node_modules. Then I ran pnpm install with pnpm 12.14.0, from the packageManager field.
• The lockfile now names pnpm 12.14.0 in the packageManagerDependencies record.
• Compared with the first commit, the new lockfile diff has only the pnpm records: pnpm and the 14 @pnpm/exe.* platform packages move from 12.11.2 to 12.14.0. No other package changes.
• Compared with main, the lockfile diff has the three packages in the version table and the pnpm records.
• pnpm why shows one copy of viem (2.57.7), @lifi/sdk (4.12.1), and @lifi/types (18.13.0).

Overrides

The overrides in examples/node/pnpm-workspace.yaml do not change.

• ws@<=8.22.0: still needed. viem 2.57.7 pins ws 8.21.0.
• zod@<4.6.0: no change. zod is an optional peer of abitype and is not installed.
• @lifi/data-types>@lifi/types: still needed. The tree has one copy of @lifi/types.
• axios: no change. axios is not in the tree.

Release-age gate

• Added: none. Removed: none. The example has only the '@lifi/*' scope entry.
• @lifi/sdk-provider-ethereum 4.2.11 (published 2026-10-16 13:58 UTC) is now older than 24 h. The '@lifi/*' entry stays.
• viem 2.57.7 (published 2026-10-14 17:05 UTC), ox 0.14.56 (published 2026-10-11 20:53 UTC), and pnpm 12.14.0 are older than 24 h.

Verification in examples/node (before -> after the pnpm commit)

• pnpm install --frozen-lockfile: pass -> pass
• pnpm exec tsc --noEmit: pass -> pass
• pnpm audit: no known vulnerabilities -> no known vulnerabilities
• pnpm dedupe --check: pass -> pass
• pnpm outdated: none -> none
• The example has no test script. The example:* scripts need PRIVATE_KEY and send real transactions, so I did not run them. An offline tsx script ran createClient and setProviders([EthereumProvider(...)]). It passed with viem 2.57.7 and pnpm 12.14.0.
• The root husky hooks passed (pre-commit and pre-push).

No changeset is needed. This PR changes only an example.

Visual showcase (Screenshots or Videos)

Not applicable.

Checklist before requesting a review

• I have performed a self-review and testing of my code.
• This pull request is focused and addresses a single problem.
• If this PR modifies the SDK API or adds new features that require documentation, I have updated the documentation in the public-docs repository.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8c2570e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

📦 Bundle size

✅ No significant changes. Every check is within budget.

@lifi/sdk

	Import	Base	PR	Change	Budget used
⚪	createClient + getQuote	4.31 kB	4.31 kB	—	▰▰▰▰▰▰▰▱▱▱ 72%
⚪	all exports	16.0 kB	16.0 kB	—	▰▰▰▰▰▰▰▰▱▱ 80%
⚪	CJS (no tree-shaking)	19.4 kB	19.4 kB	—	▰▰▰▰▰▰▰▰▱▱ 81%

Providers

	Import	Base	PR	Change	Budget used
⚪	ethereum (+ viem)	96.9 kB	96.9 kB	—	▰▰▰▰▰▰▰▰▱▱ 84%
⚪	solana	28.3 kB	28.3 kB	—	▰▰▰▰▰▰▰▰▱▱ 83%
⚪	bitcoin	68.1 kB	68.1 kB	—	▰▰▰▰▰▰▰▰▱▱ 83%
⚪	sui	98.2 kB	98.2 kB	—	▰▰▰▰▰▰▰▰▰▱ 89%
⚪	tron	213.1 kB	213.1 kB	—	▰▰▰▰▰▰▰▰▰▱ 92%
⚪	stellar	122.9 kB	122.9 kB	—	▰▰▰▰▰▰▰▰▱▱ 83%
⚪	zcash	6.45 kB	6.45 kB	—	▰▰▰▰▰▰▰▰▱▱ 81%

Full integration

	Import	Base	PR	Change	Budget used
⚪	createClient + all providers	588.2 kB	588.2 kB	—	▰▰▰▰▰▰▰▰▰▱ 87%

How to read this

• Sizes are minified + brotli, measured with size-limit the way an app bundles the import: tree-shaken, with all dependencies included except the ones in the check's ignore list (packages the app already has, such as peers).
• Code behind a dynamic import() is counted too, unless the check's name says otherwise.
• 🟠 / 🟢 mark a change of at least 512 B and at least 1% or 5.00 kB. 🔴 means the check is over its budget.
• Budgets live in .size-limit.json. The base commit is measured with the same checks as the PR.

_{8c2570e merged into 4c5f473 · workflow run}