chore: upgrade to ENSv2 (Universal Resolver) - #411
Conversation
|
Someone is attempting to deploy a commit to the EFP Team on Vercel. A member of the Team first needs to authorize it. |
📝 WalkthroughWalkthroughpackage.json now adds ChangesDependency updates
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 62: The package.json bump to "viem": "^2.48.11" may not actually add
ENSv2/Universal Resolver support; confirm whether this version bump was intended
to enable ENSv2 features and either revert or update the dependency to a viem
release that explicitly documents ENSv2/Universal Resolver support. Also confirm
whether accompanying code changes to src/utils/ens.ts (e.g., any functions or
classes that interact with ENS/Universal Resolver) are missing from this PR; if
ENSv2 functionality is expected, add the necessary changes to src/utils/ens.ts
to use the correct viem APIs or update the package.json to the correct version
and note which ENS functions (in src/utils/ens.ts) rely on the newer viem
behavior so reviewers can validate them.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 5560b9c1-ccf1-42d9-9a10-863dfcd6986f
⛔ Files ignored due to path filters (1)
bun.lockbis excluded by!**/bun.lockb
📒 Files selected for processing (1)
package.json
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
🧹 Nitpick comments (1)
package.json (1)
21-21:@noble/hashes@1.8.0 is not a viem peer dependency; viem@2.48.11 already depends on it
viem@2.48.11lists onlytypescriptunderpeerDependencies(no@noble/hashes).viem@2.48.11has@noble/hashes@1.8.0in its regular dependencies, so1.8.0matches whatviemexpects.- No npm security advisories were returned for
@noble/hashesby the query.- If the app doesn’t import
@noble/hashesdirectly, removing it frompackage.json(line 21) would be optional sinceviemwill pull it transitively.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@package.json` at line 21, The dependency "`@noble/hashes`": "1.8.0" in package.json is redundant because viem@2.48.11 already depends on that version; remove the explicit "`@noble/hashes`" entry from package.json (or only keep it if your code imports it directly), then run your package manager install to update the lockfile (npm install / yarn install) and re-run tests/lint to ensure nothing breaks; if you do need it, keep the exact version but otherwise delete the "`@noble/hashes`" entry to avoid duplicate direct dependency declarations.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@package.json`:
- Line 21: The dependency "`@noble/hashes`": "1.8.0" in package.json is redundant
because viem@2.48.11 already depends on that version; remove the explicit
"`@noble/hashes`" entry from package.json (or only keep it if your code imports it
directly), then run your package manager install to update the lockfile (npm
install / yarn install) and re-run tests/lint to ensure nothing breaks; if you
do need it, keep the exact version but otherwise delete the "`@noble/hashes`"
entry to avoid duplicate direct dependency declarations.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 137857cc-f4da-4e9e-ba5d-50829262bf5d
⛔ Files ignored due to path filters (1)
bun.lockbis excluded by!**/bun.lockb
📒 Files selected for processing (1)
package.json
|
Updated to the later version directly on main (+ had to made some other fixes in order for builds to pass), so I am closing the PR. Thank you for reminding us to do that @Dhaiwat10 , much appreciated |
Hey! I'm Dhaiwat from the DevRel team at ENS Labs. We're working on getting active repos and libraries across the ecosystem ready for ENSv2.
Summary
Upgrades this repo to be ENSv2-ready by routing ENS resolution through the Universal Resolver (
0xeeeeeeee14d718c2b47d9923deab1335e144eeee) instead of the legacy ENS Registry.Changes
viemfrom^2.27.3→^2.48.11viemis used for ENS here at src/utils/ens.ts.Why
The current path returns stale results for names managed by the new Universal Resolver. For example,
ur.integration-tests.ethshould resolve to0x2222222222222222222222222222222222222222; legacy resolution returns incorrect values.More details: https://docs.ens.domains/web/ensv2-readiness
Verification
ur.integration-tests.eth→0x2222222222222222222222222222222222222222Summary by CodeRabbit