Skip to content

Update the InfuraProvider and BrowserProvider tutorial for ethers v6#2809

Open
aproskill81 wants to merge 1 commit intoMetaMask:mainfrom
aproskill81:fix/ethers-v6-send-transaction-tutorial
Open

Update the InfuraProvider and BrowserProvider tutorial for ethers v6#2809
aproskill81 wants to merge 1 commit intoMetaMask:mainfrom
aproskill81:fix/ethers-v6-send-transaction-tutorial

Conversation

@aproskill81
Copy link
Copy Markdown

@aproskill81 aproskill81 commented Mar 30, 2026

Description

This PR updates the use-ethers.js-infuraprovider-or-web3provider tutorial to use ethers v6 syntax.

The tutorial currently tells users to install ethers without pinning an older version, which resolves to the latest release. However, the examples on the page still use legacy ethers v5 APIs. As a result, users following the tutorial as written can run into runtime errors when they copy the sample code.

This change aligns the tutorial with the current ethers package by updating the examples and terminology to ethers v6 and by keeping the complete sample consistent with Sepolia.


Note

Low Risk
Low risk because changes are limited to documentation/code samples, but incorrect v6 API usage could mislead readers if not verified end-to-end.

Overview
Updates the use-ethers.js-infuraprovider-or-web3provider tutorial to ethers v6 syntax and terminology, including renaming Web3Provider references to BrowserProvider throughout.

Refreshes the embedded React code snippets to v6 APIs (e.g., new ethers.BrowserProvider(...), ethers.parseEther, provider.send('eth_requestAccounts', []), and getBlockNumber() without parameters) and keeps the complete sample aligned to the Sepolia network.

Written by Cursor Bugbot for commit 510d6a3. This will update automatically on new commits. Configure here.

@aproskill81 aproskill81 requested review from a team as code owners March 30, 2026 08:17
@vercel
Copy link
Copy Markdown

vercel bot commented Mar 30, 2026

@aproskill81 is attempting to deploy a commit to the Consensys Team on Vercel.

A member of the Team first needs to authorize it.

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.

1 participant