Skip to content

chore(deps): bump the npm-deps group across 1 directory with 7 updates - #115

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/examples/feepayer/client/npm-deps-7b51ccefc3
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/examples/feepayer/client/npm-deps-7b51ccefc3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the npm-deps group with 7 updates in the /examples/feepayer/client directory:

Package From To
@noble/curves 2.0.1 2.4.0
dotenv 16.6.1 18.0.9
tempo.ts 0.14.0 0.14.2
viem 2.57.4 2.57.16
@types/node 25.2.0 26.6.6
tsx 4.20.6 4.23.15
typescript 5.9.3 7.0.2

Updates @noble/curves from 2.0.1 to 2.4.0

Release notes

Sourced from @​noble/curves's releases.

2.4.0

  • Harden FROST distributed key generation against round-one transcript substitution.
    • This is not a vulnerability; it's protection against those who don't follow the FROST spec. Spec wants user to preserve rounds.
  • FROST: Enforced RFC 9591 point validation for BLS and BN
  • POPRF: replace inversion with const-time version
  • Weierstrass: harden public-key boundaries & infinity handling
    • ECDH and ECDSA now reject the identity even for point types whose generic codec permits it
    • Curves that disallow infinity cannot encode it, while opted-in curves use the canonical SEC 1 0x00 encoding.
  • DER: Bounded ECDSA signature and INTEGER sizes before bigint conversion, preventing malformed inputs from causing disproportionate parsing and allocation work
  • Snapshot all security-sensitive state (passed arguments) to ensure it can't be mutated

Special thanks to Red Team (Rob Hamilton, CalleBTC, Omer Talip) and 1Password's Off-by-1 Labs.

Full Changelog: paulmillr/noble-curves@2.3.0...2.4.0

2.3.0

Security & constant-timeness

  • Hardened constant-time execution from best-effort to actual guarantees: no measurable timing behavior on 200K samples. Scalar multiplication now uses secret-scalar blinding via CSPRNG, un-precomputed points now use a constant-time fixed-window multiply instead of variable-time fallbacks, and modular arithmetic helpers were hardened. New CT benchmarks track timing behavior.
  • General hardening across all modules
  • Fixes from the Trail of Bits review: recovered ECDSA signatures are now bound to their recovery id, non-canonical BLS signature encodings are rejected, Edwards <-> Montgomery conversion helpers were corrected, and FROST DKG round-2 retry handling was hardened.

X25519 hardening

It was possible to execute a remote timing attack on X25519, across many samples, and learn up to 4.036 bits of long-term private key. Other 247 bits were NOT affected.

The impact: mainly fingerprinting (recognition of key across deployments), NOT key recovery, NOT X25519 breakage. Maintainer was also not able to escalate to co-residency (SMT).

Reported and found by:

  • George Stergiopoulos, Department of Informatics, Athens University of Economics and Business, Greece (geostergiop@aueb.gr)
  • Constantinos Patsakis, Department of Informatics, University of Piraeus, 80 Karaoli & Dimitriou str., 18534 Piraeus, Greece (kpatsak@unipi.gr)

Performance

  • ECDSA/EdDSA verification up to +32%, Weierstrass ECDH up to +19%, x25519 getPublicKey 2.7×
  • BLS signatures 2x
  • Init time (first getPublicKey or sign) reduced ~2x for ed25519, p256, p384, p521
  • Also faster verification of recovered signatures, pairing tower / FFT / Pippenger optimizations, and joint-MSM paths in FROST and OPRF
  • getPublicKey / sign got slower because we've decreased window size (W=8 => W=6) and hardened CT execution (see above). Long-running apps that prefer 2.2.0-level speed can restore it with one line: secp256k1.Point.BASE.precompute(8) (likewise for other curves).

Misc

  • Smaller bundles: improved tree-shaking across modules
  • Better error messages and type checks
  • Upgrade noble-hashes to 2.3.0, with performance boost
  • Reduce on-disk size 1831kb → 1548kb (-282kb) by disabling source maps (they became less relevant).

Full Changelog: paulmillr/noble-curves@2.2.0...2.3.0

... (truncated)

Changelog

Sourced from @​noble/curves's changelog.

2.4.0 (2026-08-27)

  • Harden FROST distributed key generation against round-one transcript substitution.
    • This is not a vulnerability; it's protection against those who don't follow the FROST spec. Spec wants user to preserve rounds.
  • FROST: Enforced RFC 9591 point validation for BLS and BN
  • POPRF: replace inversion with const-time version
  • Weierstrass: harden public-key boundaries & infinity handling
    • ECDH and ECDSA now reject the identity even for point types whose generic codec permits it
    • Curves that disallow infinity cannot encode it, while opted-in curves use the canonical SEC 1 0x00 encoding.
  • DER: Bounded ECDSA signature and INTEGER sizes before bigint conversion, preventing malformed inputs from causing disproportionate parsing and allocation work
  • Snapshot all security-sensitive state (passed arguments) to ensure it can't be mutated

Special thanks to Red Team (Rob Hamilton, CalleBTC, Omer Talip) and 1Password's Off-by-1 Labs.

2.3.0 (2026-08-06)

Security and constant-timeness

  • Hardened constant-time execution from best-effort to actual guarantees, with no measurable timing behavior across 200,000 samples. Scalar multiplication now uses secret-scalar blinding via CSPRNG, unprecomputed points use a constant-time fixed-window multiply instead of variable-time fallbacks, and modular arithmetic helpers were hardened. New constant-time benchmarks track timing behavior.
  • General hardening across all modules.
  • Applied fixes from the Trail of Bits review: recovered ECDSA signatures are now bound to their recovery ID, non-canonical BLS signature encodings are rejected, Edwards-to-Montgomery conversion helpers were corrected, and FROST DKG round-two retry handling was hardened.

X25519 hardening

It was possible to execute a remote timing attack on X25519 across many samples and learn up to 4.036 bits of a long-term private key. The other 247 bits were not affected.

The impact is primarily fingerprinting—a key can be recognized across deployments—not key recovery or a break of X25519. The maintainer was also unable to escalate the attack to co-residency (SMT).

Reported and found by:

  • George Stergiopoulos, Department of Informatics, Athens University of Economics and Business, Greece (geostergiop@aueb.gr).
  • Constantinos Patsakis, Department of Informatics, University of Piraeus, 80 Karaoli & Dimitriou Street, 18534 Piraeus, Greece (kpatsak@unipi.gr).

Performance

  • Improved ECDSA and EdDSA verification by up to 32%, Weierstrass ECDH by up to 19%, and X25519 getPublicKey by 2.7×.
  • Improved BLS signature performance by 2×.
  • Reduced initialization time for the first getPublicKey or sign call by approximately 2× for Ed25519, P-256, P-384, and P-521.
  • Also improved verification of recovered signatures, pairing tower, FFT, and Pippenger performance, as well as joint-MSM paths in FROST and OPRF.
  • getPublicKey and sign became slower because the window size was decreased from 8 to 6 and constant-time execution was hardened. Long-running applications that prefer 2.2.0-level speed can restore it with secp256k1.Point.BASE.precompute(8), and likewise for other curves.

Miscellaneous

  • Improved tree-shaking for smaller bundles.
  • Improved error messages and type checks.
  • Upgraded noble-hashes to 2.3.0 for improved performance.
  • Reduced on-disk size from 1,831 KB to 1,548 KB by disabling source maps, which have become less relevant.

2.2.0 (2026-04-12)

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​noble/curves since your current version.


Updates dotenv from 16.6.1 to 18.0.9

Changelog

Sourced from dotenv's changelog.

18.0.9 (2026-10-14)

Changed

  • Permit DOTENV_PATH being empty string with the CLI (#1076)

18.0.8 (2026-10-14)

Changed

  • Fast parser should strip appended extra quotes (#1073)
  • Type detail improvement (#1074)

18.0.7 (2026-10-09)

Changed

  • Treat undefined settings like quiet: true as null rather than falsey (#1070)
  • CLI should honor DOTENV_QUIET setting in .env file (#1071)

18.0.6 (2026-10-06)

Changed

  • Use smarter parseBoolean not Boolean() to fix override (#1069)

18.0.5 (2026-09-30)

Changed

  • Fix missing typescript module declaration (#1068)
  • Improve performance for large .env files (#1066)

18.0.4 (2026-09-25)

Changed

  • import dotenv/config should default quiet: true (#1063)

18.0.3 (2026-09-22)

Changed

  • Patch DOTENV_QUIET setting when inside .env file (#1059)

18.0.2 (2026-09-21)

Changed

  • Patch additional edge cases for the fast parser (#1056)

... (truncated)

Commits
  • 8d1ab85 18.0.9
  • 59a40ce changelog
  • 88228bd Merge pull request #1076 from Enesuygurs/fix/cli-empty-dotenv-path
  • bc6ef94 fix(cli): load the default .env when DOTENV_PATH is empty
  • 6d6e6c5 Merge pull request #1075 from kory-kaai/test/fast-parser-branch-coverage
  • 10218f1 test(parse-fast): cover the size-dependent and export-prefix branches
  • e2fe95e 18.0.8
  • 7aa712a type detail improvement
  • 53405b0 Merge pull request #1074 from himanshu748/codex/fix-dotenv-populate-undefined...
  • 0b4843a changelog
  • Additional commits viewable in compare view

Updates tempo.ts from 0.14.0 to 0.14.2

Release notes

Sourced from tempo.ts's releases.

tempo.ts@0.14.2

Patch Changes

tempo.ts@0.14.1

Patch Changes

Changelog

Sourced from tempo.ts's changelog.

0.14.2

Patch Changes

0.14.1

Patch Changes

Commits

Updates viem from 2.57.4 to 2.57.16

Release notes

Sourced from viem's releases.

viem@2.57.16

Patch Changes

  • #5395 c60ca26e030706610bcf61689331008a30a3db2a Thanks @​jxom! - viem/tempo: gatewayActions paid in the Gateway currency the Client account held most of, threw Gateway.InsufficientFundsError (with the account's balances) when it couldn't pay, and explained how to pay in Gateway.PaymentRequiredError.

  • #5392 9348d386a9f62fd6713124e25360d6040e4a34cf Thanks @​gakonst! - Stopped retrying JSON-RPC method-not-found (-32601) and method-not-supported (-32004) errors from non-2xx HTTP responses, since a retry gets the same refusal.

  • #5392 9348d386a9f62fd6713124e25360d6040e4a34cf Thanks @​gakonst! - Reduced per-request overhead of the http, webSocket and ipc transports by building the onFetchRequest Request only when the hook is set and the TimeoutError only when a request times out, and fetched the withdrawal receipt once in the ZKsync finalizeWithdrawal and isWithdrawalFinalized actions.

  • #5392 9348d386a9f62fd6713124e25360d6040e4a34cf Thanks @​gakonst! - Cached signature hashes in toSignatureHash, so selector lookups in decodeFunctionData, decodeEventLog, decodeErrorResult and encodeFunctionData no longer hash every ABI item on each call.

  • #5391 721d6824516514195c0a98971731c6d81b2f9032 Thanks @​jxom! - viem/tempo: Added experimental Gateway and gatewayActions (client.ai, client.bucket, client.compute, client.kv), with standalone Actions.ai, Actions.bucket, Actions.compute, and Actions.kv, with client.gateway.getCapabilities, Actions.gateway.getCapabilities and defaults for every option (gatewayActions()), for wallet-paid inference (including streamed text), object storage, metered and streamed CPU and GPU compute, and key-value state on a Tempo Gateway paid with a local Client account through the optional mppx peer dependency, with Tempo Wallet through the Accounts SDK, or with an app-supplied payment-aware fetch.

viem@2.57.15

Patch Changes

  • #5339 a864b864b8b9031d970910fb8247471924d09280 Thanks @​mortezashojaei! - Fixed getAbiItem to throw AbiItemAmbiguityError for overloads that JavaScript cannot distinguish, such as bytes vs bytes32, uint256 vs int256, and uint256[] vs uint256[2], while resolving distinguishable values by byte length and integer range.

  • #5321 af062571382ec3631cf1901aeda9b58a87c8fad5 Thanks @​evanaronson! - Removed a trailing slash to the ZKsync explorer URL.

  • #5358 179a53682d9bf2ac2b7a65a86ec312fca0c7c9a8 Thanks @​Turkchain1919! - Added Turkchain Mainnet (Chain ID: 1919) to the supported chains.

  • #5375 bb12b94649962cd7f03c339c226399c614b49805 Thanks @​jxom! - Fixed decodeEventLog and parseEventLogs to decode anonymous event logs when eventName names the event or every event in abi is anonymous, as with getLogs and watchEvent given a single anonymous event.

  • #5364 8f2a79ba8b4d235a24c4c101f4ef04a824c3e429 Thanks @​jxom! - ccip: Applied the HTTP transport timeout (including its override) and 10 MiB response cap to CCIP-Read gateway requests, refused non-HTTP(S) gateway URLs (including data: URLs, which previously worked), and limited one lookup to 4 nested callbacks, 4 nested local batches, 256 gateway requests and 16 concurrent requests.

  • #5372 f32ef6c41e623683b99989422eac7ac6cea5c107 Thanks @​jxom! - Fixed estimateGas and estimateContractGas returning a gas limit filled by eth_fillTransaction that ignored blockNumber, blockTag, and stateOverride.

  • #5360 41801d827e339b96d1b4dd775f4dd379f17cc610 Thanks @​jxom! - Raised the default expiring nonce validBefore from 25 to 270 seconds, capped Relay.feePayer expiring nonce windows at 300 seconds, added Transaction.expiringNonceMaxExpiry, and replaced the random expiring nonce validAfter with a random nonce discriminator.

  • #5360 41801d827e339b96d1b4dd775f4dd379f17cc610 Thanks @​jxom! - Fixed sponsored prepareTransactionRequest fills keeping a requested feeToken that the fee payer did not sign, which made the fee payer signature invalid.

  • #5378 cbdd61078378012368464c9b0e4a76804a5ea987 Thanks @​mmv08! - Fixed fillTransaction and prepareTransactionRequest returning gasPrice next to EIP-1559 fees on Anvil, which made estimateGas and sendTransaction fail on Anvil 1.8.5 and later with "both gasPrice and (maxFeePerGas or maxPriorityFeePerGas) specified".

  • #5346 7156f80f77c47c0a3f9df479b0a6e856029edb3b Thanks @​KieranAltman! - Updated HashKey Chain and HashKey Chain Testnet display names, native currency name, and block explorer URLs.

  • #5373 ddc2d365d093793f9d8f5818743f169c98eed8d7 Thanks @​jxom! - Added an optional nonce to NonceManager reset parameters, which sendTransaction and sendTransactionSync now set to the consumed nonce when a send fails after consume returned.

  • #5371 035c519b6b6b3f179fa741953751a501f05132a2 Thanks @​jxom! - Fixed parseTransaction to accept an EIP-7702 authorization yParity from 2 to 255 so a serialized transaction parses back, and made recoverAuthorizationAddress throw InvalidYParityError (and verifyAuthorization return false) for a yParity other than 0 or 1, which EIP-7702 treats as having no authority.

  • #5318 57db085e896dfee3a3387fb7573bf7f7ebc6170d Thanks @​jxom! - Fixed parseTransaction not raising TipAboveFeeCapError when the encoded maxFeePerGas is zero.

  • #5377 42c41ca3c42792e56a2e1f64d3007c28adc9fbba Thanks @​mmv08! - Fixed sendTransactionSync and writeContractSync failing at once and freeing the nonce when the node had accepted the transaction but stopped waiting for its receipt (eth_sendRawTransactionSync error code 4), even if the error had no transaction hash, and stopped fallback from sending that transaction to the next node.

  • #5388 141f8c0ed7f5fdeafbfc514131781638e9340bd9 Thanks @​jxom! - Added Account.serialize and Account.deserialize to viem/tempo, which store a configurable account (TIP-1107) as JSON and rebuild it with passkey owners that sign, and Account.AddressMismatchError for a version-zero config that does not derive the stored address. Added a keyAuthorization option to access key accounts, which attaches a signed key authorization to the account's transactions until the chain registers the access key.

  • #5318 57db085e896dfee3a3387fb7573bf7f7ebc6170d Thanks @​jxom! - Fixed maxPriorityFeePerGas above a maxFeePerGas of 0n not raising TipAboveFeeCapError or MaxFeePerGasTooLowError (including in actions that validate requests before calling the node, such as call and estimateGas), and fixed fee error messages dropping 0n values.

  • #5370 18b6b9041ef9d19421d182e6b0ca4b1caf5be09e Thanks @​jxom! - Fixed validateTypedData (and so hashTypedData and signTypedData) accepting field types that are not EIP-712 types, such as uint7, uint264, uint08, int0 or bytes0, and field types that reference a struct missing from types, including in structs only referenced as array elements; it now throws InvalidTypedDataTypeError.

... (truncated)

Commits
  • 98aa491 chore: raise viem/ens size limit (#5398)
  • 71241b2 chore: version package (#5393)
  • e1329c9 fix(tempo): check Gateway chain and refresh balances before payment errors (#...
  • c60ca26 feat(tempo): fund-aware Gateway payments and InsufficientFundsError (#5395)
  • 264ab41 docs(tempo): use code groups with viem.config in Gateway guides (#5394)
  • 721d682 feat(tempo): add experimental Gateway actions (#5391)
  • 9348d38 perf: skip retries for method refusals and trim per-request overhead (#5392)
  • 5711b7e chore: version package (#5363)
  • dbf8ae6 test: stabilize sendTransactionSync timeout and watchBlocks catch-up test...
  • 141f8c0 feat(tempo): add Account.serialize, Account.deserialize and keyAuthorization ...
  • Additional commits viewable in compare view

Updates @types/node from 25.2.0 to 26.6.6

Commits

Updates tsx from 4.20.6 to 4.23.15

Release notes

Sourced from tsx's releases.

v4.23.15

4.23.15 (2026-09-20)

Bug Fixes

  • exclude bare builtins from namespace inheritance (38e1588)
  • expose require.cache and require.extensions to tsImport CommonJS modules (2da3407)
  • make namespaced register() overloads portable for declaration emit (562c434)

This release is also available on:

v4.23.14

4.23.14 (2026-09-20)

Bug Fixes

  • restore the CJS bridge namespace for Node 24 require(esm) under tsImport() (#802) (6e5236b)

This release is also available on:

v4.23.13

4.23.13 (2026-08-30)

Bug Fixes

  • cache: bound shared transform cache memory (#835) (28e1f12)

This release is also available on:

v4.23.12

4.23.12 (2026-08-10)

Bug Fixes

  • shim import.meta when tokens are split by comments or newlines (#829) (ed9d330), closes #828

This release is also available on:

... (truncated)

Commits
  • ca66105 test: fix drive-less file URLs in ESM resolver fixtures
  • 2da3407 fix: expose require.cache and require.extensions to tsImport CommonJS modules
  • 38e1588 fix: exclude bare builtins from namespace inheritance
  • 562c434 fix: make namespaced register() overloads portable for declaration emit
  • edfb1f0 build: upgrade pkgroll and externalize CJS loader reference
  • 70e7828 test: upgrade tinyspy for disposable API
  • 9ed2022 ci: avoid duplicate release notifications
  • 872e77f refactor: use disposables for cleanup
  • 6e5236b fix: restore the CJS bridge namespace for Node 24 require(esm) under tsImport...
  • 28e1f12 fix(cache): bound shared transform cache memory (#835)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for tsx since your current version.


Updates typescript from 5.9.3 to 7.0.2

Release notes

Sourced from typescript's releases.

TypeScript 7.0.2

https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/

This tag was originally released at: https://github.com/microsoft/typescript-go/releases/tag/typescript%2Fv7.0.2

TypeScript 6.0.3

For release notes, check out the release announcement blog post.

Downloads are available on:

TypeScript 6.0

For release notes, check out the release announcement blog post.

Downloads are available on:

TypeScript 6.0.1 RC

For release notes, check out the release announcement blog post.

Downloads are available on:

TypeScript 6.0 Beta

For release notes, check out the release announcement.

Downloads are available on:

Commits
  • 1e4744d Merge branch 'main' into ts7-release
  • a5a219cmicrosoft/typescript-go#4558
  • ecfe30d Update status localization
  • 5de25b5 Hide executable name in TypeScript status
  • d7ce74a Show bundled TypeScript version for packaged servers
  • 29be66a Correct TS 7 release version to 7.0.2
  • ed2bd1b Merge branch 'main' into ts7-release
  • 8873075 Bump the github-actions group across 1 directory with 3 updates (microsoft/ty...
  • 9427131 Set up stable / nightly extension split, other prep (microsoft/typescript-go#...
  • d4eaca5microsoft/typescript-go#4549
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.


@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 29, 2026
@github-actions

github-actions Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

⚠️ Changelog not found.

A changelog entry is required before merging.

Add changelog

@socket-security

socket-security Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​@​types/​node@​25.2.0 ⏵ 26.6.6100 +110081 +194 +1100
Updatednpm/​tsx@​4.20.6 ⏵ 4.23.15100 +110081 +190100
Updatednpm/​tempo.ts@​0.14.0 ⏵ 0.14.28110085 -992 -1100
Updatednpm/​@​noble/​curves@​2.0.1 ⏵ 2.4.010010010082 -2100
Updatednpm/​typescript@​5.9.3 ⏵ 7.0.29910089 -1100100 +10
Updatednpm/​dotenv@​16.6.1 ⏵ 18.0.99910010095 -1100
Updatednpm/​viem@​2.57.4 ⏵ 2.57.1697100100 +198 +1100

View full report

@dependabot dependabot Bot changed the title chore(deps): bump the npm-deps group in /examples/feepayer/client with 7 updates chore(deps): bump the npm-deps group across 1 directory with 7 updates Oct 1, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/examples/feepayer/client/npm-deps-7b51ccefc3 branch 2 times, most recently from 71c1b52 to 396871d Compare October 8, 2026 10:45
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/examples/feepayer/client/npm-deps-7b51ccefc3 branch 2 times, most recently from 29111e9 to b2ba70d Compare October 16, 2026 21:31
"typescript": "^5.3.3"
"@types/node": "^26.6.5",
"tsx": "^4.23.15",
"typescript": "^7.0.2"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔴 After this bump, maintainers running pnpm check (tsc --noEmit) are likely to get config and type errors that TypeScript 5.9.3 does not raise. The unchanged tsconfig.json sets "moduleResolution": "node" (node10). TS 6.0 deprecated that and TS 7 removes it. It also omits types, which now defaults to [], so process in config.ts no longer resolves. Fix: migrate tsconfig.json in this PR. Use "moduleResolution": "bundler" (or "module"/"moduleResolution": "nodenext") and add "types": ["node"], then confirm pnpm check passes. Otherwise keep typescript on ^5.x.

Why this was flagged

The trigger is running the check script (tsc --noEmit, package.json:9) after a fresh install from the lockfile, which now pins typescript 7.0.2. examples/feepayer/client/tsconfig.json is not touched by this diff and still has "moduleResolution": "node", the node10 mode. TypeScript 6.0 deprecated it and 7.0 turns that into an error that the compiler option was removed. TS 6+ also defaults compilerOptions.types to [], so @ types/node no longer loads automatically. The process.env reads in config.ts (lines 14-27) would then fail with "Cannot find name 'process'". On the base branch, TS 5.9.3 accepts this tsconfig and loads @ types/node automatically, so check passes. skipLibCheck: true does not help because both errors come from the config and from the project's own sources, not from .d.ts files. I could not run tsc 7 in this environment, but the behavior follows TypeScript's published 6.0/7.0 deprecation schedule.

Verification: When anyone runs pnpm check (tsc --noEmit, package.json:9) after installing from the new lockfile, the type-check that passes on the base will fail. The lockfile pins typescript: specifier: ^7.0.2, version: 7.0.2 (pnpm-lock.yaml:30-32, 430). examples/feepayer/client/tsconfig.json is not touched by this diff and still has "moduleResolution": "node" (node10).

"typescript": "^5.3.3"
"@types/node": "^26.6.5",
"tsx": "^4.23.15",
"typescript": "^7.0.2"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔴 After the move to TypeScript 7, pnpm check probably reports "Cannot find name 'process'" and similar errors across both client files. TypeScript 6 and later default types to [], so @ types/node is no longer loaded automatically. The unchanged tsconfig.json sets lib: ["ES2022"] with no types entry, so process, console and btoa have no declarations. Fix: add "types": ["node"] to compilerOptions in tsconfig.json, or pin typescript to ^5. Fixing moduleResolution alone leaves these errors in place.

Why this was flagged

A maintainer runs the check script (tsc --noEmit, package.json:9) after installing from the new lockfile, which pins typescript 7.0.2. examples/feepayer/client/tsconfig.json sets "lib": ["ES2022"] and has no types field. Under TypeScript 5.9.3 every @ types/* package was included automatically, so @ types/node supplied globals like process. Starting with TypeScript 6.0, types defaults to [], so those globals are gone. The globals in question are used at config.ts:14-27 (process.env), config.ts:48 (btoa) and client.ts:8-72 (console). ES2022 lib does not declare any of them, because lib.dom is not included. The likely result is TS2580/TS2304 errors in both source files, where the base branch type-checks cleanly. This is separate from the filed moduleResolution: "node" findings and needs a different fix (types: ["node"]). Fixing only moduleResolution would still leave these errors. No CI job runs this client, so nothing catches the break before merge.

Verification: examples/feepayer/client/tsconfig.json is unchanged and sets "lib": ["ES2022"] with no types field. On TypeScript 5.9.3, @ types/node supplied process.env.* at config.ts:14-27, btoa(...) at config.ts:48 and console in client.ts:8-72. Starting with TypeScript 6.0, types defaults to [], and TypeScript 7 keeps that default, so @ types/node is no longer loaded.

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/examples/feepayer/client/npm-deps-7b51ccefc3 branch from b2ba70d to 3dd7ade Compare October 21, 2026 16:44

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code review found no new issues

No new issues were found in this update; 2 findings from earlier reviews are still open above.

Still open from earlier reviews (2):

If you have decided not to act on one of these findings, resolve its thread (a reply alone leaves it open) and the next review stops counting it. To review this commit again now, use Re-run on its "Claude Code Review" check.

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/examples/feepayer/client/npm-deps-7b51ccefc3 branch from 3dd7ade to a80303a Compare October 29, 2026 10:45

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code review found no new issues

No new issues were found in this update; 2 findings from earlier reviews are still open above.

Still open from earlier reviews (2):

If you have decided not to act on one of these findings, resolve its thread (a reply alone leaves it open) and the next review stops counting it. To review this commit again now, use Re-run on its "Claude Code Review" check.

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/examples/feepayer/client/npm-deps-7b51ccefc3 branch from a80303a to bb44920 Compare November 4, 2026 23:27

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code review found no new issues

No new issues were found in this update; 2 findings from earlier reviews are still open above.

Still open from earlier reviews (2):

If you have decided not to act on one of these findings, resolve its thread (a reply alone leaves it open) and the next review stops counting it. To review this commit again now, use Re-run on its "Claude Code Review" check.

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/examples/feepayer/client/npm-deps-7b51ccefc3 branch from bb44920 to 78e99f3 Compare November 5, 2026 10:45
Bumps the npm-deps group with 7 updates in the /examples/feepayer/client directory:

| Package | From | To |
| --- | --- | --- |
| [@noble/curves](https://github.com/paulmillr/noble-curves) | `2.0.1` | `2.4.0` |
| [dotenv](https://github.com/motdotla/dotenv) | `16.6.1` | `18.0.9` |
| [tempo.ts](https://github.com/tempoxyz/tempo-ts) | `0.14.0` | `0.14.2` |
| [viem](https://github.com/wevm/viem) | `2.57.4` | `2.57.16` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `25.2.0` | `26.6.6` |
| [tsx](https://github.com/privatenumber/tsx) | `4.20.6` | `4.23.15` |
| [typescript](https://github.com/microsoft/TypeScript) | `5.9.3` | `7.0.2` |



Updates `@noble/curves` from 2.0.1 to 2.4.0
- [Release notes](https://github.com/paulmillr/noble-curves/releases)
- [Changelog](https://github.com/paulmillr/noble-curves/blob/main/CHANGELOG.md)
- [Commits](paulmillr/noble-curves@2.0.1...2.4.0)

Updates `dotenv` from 16.6.1 to 18.0.9
- [Changelog](https://github.com/motdotla/dotenv/blob/master/CHANGELOG.md)
- [Commits](motdotla/dotenv@v16.6.1...v18.0.9)

Updates `tempo.ts` from 0.14.0 to 0.14.2
- [Release notes](https://github.com/tempoxyz/tempo-ts/releases)
- [Changelog](https://github.com/tempoxyz/tempo-ts/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tempoxyz/tempo-ts/compare/tempo.ts@0.14.0...tempo.ts@0.14.2)

Updates `viem` from 2.57.4 to 2.57.16
- [Release notes](https://github.com/wevm/viem/releases)
- [Commits](https://github.com/wevm/viem/compare/viem@2.57.4...viem@2.57.16)

Updates `@types/node` from 25.2.0 to 26.6.6
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `tsx` from 4.20.6 to 4.23.15
- [Release notes](https://github.com/privatenumber/tsx/releases)
- [Changelog](https://github.com/privatenumber/tsx/blob/master/release.config.cjs)
- [Commits](privatenumber/tsx@v4.20.6...v4.23.15)

Updates `typescript` from 5.9.3 to 7.0.2
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Commits](microsoft/TypeScript@v5.9.3...v7.0.2)

---
updated-dependencies:
- dependency-name: "@noble/curves"
  dependency-version: 2.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-deps
- dependency-name: "@types/node"
  dependency-version: 26.6.2
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: npm-deps
- dependency-name: dotenv
  dependency-version: 18.0.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: npm-deps
- dependency-name: tempo.ts
  dependency-version: 0.14.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-deps
- dependency-name: tsx
  dependency-version: 4.23.15
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-deps
- dependency-name: typescript
  dependency-version: 7.0.2
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: npm-deps
- dependency-name: viem
  dependency-version: 2.56.8
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/examples/feepayer/client/npm-deps-7b51ccefc3 branch from 78e99f3 to a4d1d8f Compare November 12, 2026 10:45

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code review found no new issues

No new issues were found in this update; 2 findings from earlier reviews are still open above.

Still open from earlier reviews (2):

If you have decided not to act on one of these findings, resolve its thread (a reply alone leaves it open) and the next review stops counting it. To review this commit again now, use Re-run on its "Claude Code Review" check.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants