Skip to content

Conversation

@fricoben
Copy link
Contributor

@fricoben fricoben commented Sep 3, 2025

Summary by CodeRabbit

  • Chores

    • Upgraded core frameworks and libraries (e.g., Next.js 14, React 18) and refreshed a wide range of dependencies.
    • Removed an unused personhood SDK dependency.
    • Added Twitter API SDK dependency.
  • Bug Fixes

    • General stability and compatibility improvements resulting from dependency updates.
  • Performance

    • Potential performance gains and smoother UI behavior due to framework and library upgrades.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 3, 2025

Walkthrough

Updated package.json dependency versions across runtime and dev tooling, removed @anima-protocol/personhood-sdk-react, and added twitter-api-sdk. Multiple major version bumps for Next.js, React, StarkNet ecosystem, and related libraries.

Changes

Cohort / File(s) Summary
Runtime dependencies upgrades
package.json
Bumped versions for packages including @avnu/gasless-sdk, @emotion/react, @emotion/styled, @mui/icons-material, @mui/material, @nimiq/style, @starknet-io/get-starknet/core, axios, starknet (to 7.x), starknetkit (to 3.x), tldts (to 6.1.x), next (to 14.x), next-axiom, nextjs-cors, posthog-js, qs, react/react-dom (to 18.3.x), dotenv, ethers, jotai, lottie-react, mongodb, react-loader-spinner, react-icons.
Dev/tooling upgrades
package.json
Updated devDependencies: Babel, @types/*, @typescript-eslint/*, autoprefixer, babel-jest, eslint, eslint-plugin-react, eslint-plugin-react-hooks, jest, postcss, prettier, tailwindcss, ts-jest, typescript.
Dependency removal
package.json
Removed @anima-protocol/personhood-sdk-react from dependencies.
Dependency addition
package.json
Added twitter-api-sdk ^1.2.1.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/update-everything

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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@vercel
Copy link

vercel bot commented Sep 3, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
app-starknet-id Error Error Sep 3, 2025 8:34am
sepolia-app-starknet-id Error Error Sep 3, 2025 8:34am

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (3)
package.json (3)

35-41: Declare required Node.js engine for Next 14/React 18.3.

Add engines to prevent accidental installs on unsupported Node versions (Next 14 requires >=18.17; many toolchains now target Node 20).

   "private": true,
+  "engines": {
+    "node": ">=18.17.0"
+  },

If your deploy target already uses Node 20, prefer ">=20.0.0".


58-59: Update React type packages to match React 18.3.

These are pinned to older 18.0.x; with react/react-dom 18.3.1 you may hit type mismatches.

-    "@types/react": "18.0.17",
-    "@types/react-dom": "18.0.6",
+    "@types/react": "^18.3.5",
+    "@types/react-dom": "^18.3.0",

6-11: Optional: expand lint coverage to .js/.cjs/.mjs.

If the repo still has JS files, the current glob misses them.

-    "lint": "eslint '**/*.{jsx,ts,tsx}'",
+    "lint": "eslint '**/*.{js,jsx,ts,tsx,cjs,mjs}'",
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 7e3c291 and cf2d2f4.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • package.json (1 hunks)
🔇 Additional comments (4)
package.json (4)

13-24: Audit breaking changes across StarkNet stack upgrades.

You bumped get-starknet/core, @starknet-react/* to 5.x, starknet 7.x, and starknetkit 3.x. These contain breaking API/behavior changes (wallet detection, provider/account shapes, connectors).

  • Re-run wallet connect, network switch, and account deployment flows locally.
  • Check for Node polyfill needs in the browser bundle (Buffer/crypto) introduced by web3 libs.

I can help generate a migration checklist if desired.

Also applies to: 44-47


29-29: dotenv usage is correctly scoped
dotenv is only required in tests/utils/apiWrappers/identity.test.ts (a Node context), with no imports in client modules. No changes needed.


48-48: Verify no client-side imports of twitter-api-sdk. A scan returned no import or require references for this package—manually confirm it’s only used in API routes or server components to avoid bundling it into client-side code.


51-67: No updates required for @typescript-eslint or Jest setup. The installed @typescript-eslint/parser & plugin v5.62.0 both support TypeScript <6.0.0 (so TS 5.9 is within range) and ESLint ^8.57.1 satisfies their peer-dependency. babel-jest is used (no ts-jest present), and eslint-config-next v14 supports TS 5.9.

Comment on lines 12 to 49
"dependencies": {
"@anima-protocol/personhood-sdk-react": "^0.4.4",
"@avnu/gasless-sdk": "^0.1.6",
"@emotion/react": "^11.10.0",
"@emotion/styled": "^11.10.0",
"@mui/icons-material": "^5.8.4",
"@mui/material": "^5.10.1",
"@nimiq/style": "^0.8.4",
"@starknet-io/get-starknet": "^4.0.6",
"@starknet-io/get-starknet-core": "^4.0.6",
"@avnu/gasless-sdk": "^0.1.8",
"@emotion/react": "^11.14.0",
"@emotion/styled": "^11.14.1",
"@mui/icons-material": "^5.18.0",
"@mui/material": "^5.18.0",
"@nimiq/style": "^0.8.5",
"@starknet-io/get-starknet": "^4.0.7",
"@starknet-io/get-starknet-core": "^4.0.7",
"@starknet-io/types-js": "^0.7.10",
"@starknet-react/chains": "^3.1.0",
"@starknet-react/core": "^3.7.4",
"@vercel/analytics": "^0.1.5",
"@walnuthq/sdk": "^1.1.10",
"axios": "^1.4.0",
"@starknet-react/chains": "^5.0.1",
"@starknet-react/core": "^5.0.1",
"@vercel/analytics": "^0.1.11",
"@walnuthq/sdk": "^1.1.11",
"axios": "^1.11.0",
"big.js": "^6.2.2",
"bn.js": "^5.2.1",
"dotenv": "^16.3.1",
"eslint-config-next": "^13.4.7",
"ethers": "^6.12.1",
"jotai": "^2.5.0",
"lottie-react": "^2.4.0",
"mongodb": "^4.12.1",
"next": "^14.2.3",
"next-axiom": "^1.9.1",
"nextjs-cors": "^2.1.2",
"posthog-js": "^1.68.4",
"qs": "^6.12.1",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"react-icons": "^4.4.0",
"bn.js": "^5.2.2",
"dotenv": "^16.6.1",
"eslint-config-next": "^13.5.11",
"ethers": "^6.15.0",
"jotai": "^2.13.1",
"lottie-react": "^2.4.1",
"mongodb": "^4.17.2",
"next": "^14.2.32",
"next-axiom": "^1.9.2",
"nextjs-cors": "^2.2.0",
"posthog-js": "^1.261.4",
"qs": "^6.14.0",
"react": "^18.3.1",
"react-dom": "^18.3.1",
"react-icons": "^4.12.0",
"react-loader-spinner": "5.4.5",
"starknet": "^6.24.1",
"starknet": "^7.6.4",
"starknetid.js": "4.0.1",
"starknetkit": "^2.12.1",
"tldts": "^6.1.20",
"starknetkit": "^3.0.3",
"tldts": "^6.1.86",
"twitter-api-sdk": "^1.2.1"
},
Copy link
Contributor

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Confirm removal of @anima-protocol/personhood-sdk-react across codebase.

Double-check there are no lingering imports to avoid runtime build errors.


🏁 Script executed:

#!/bin/bash
rg -n "@anima-protocol/personhood-sdk-react" -C2

Length of output: 1891


Remove lingering @anima-protocol/personhood-sdk-react references

  • Uninstall the package (npm uninstall @anima-protocol/personhood-sdk-react), remove it from package.json, and regenerate your lockfile to clear it from package-lock.json.
  • In components/identities/actions/clickable/clickablePersonhoodIcon.tsx, delete:
    import "@anima-protocol/personhood-sdk-react/style.css";
    import { Personhood, StarknetSignature } from "@anima-protocol/personhood-sdk-react";
🤖 Prompt for AI Agents
In package.json (lines 12-49) and
components/identities/actions/clickable/clickablePersonhoodIcon.tsx, remove all
traces of @anima-protocol/personhood-sdk-react: run npm uninstall
@anima-protocol/personhood-sdk-react (or yarn remove), remove its dependency
entry from package.json if present, run npm install to regenerate
package-lock.json, and in the TSX file delete the two import lines importing the
package and its style; then run a clean build to ensure no residual references
remain.

"react-icons": "^4.4.0",
"bn.js": "^5.2.2",
"dotenv": "^16.6.1",
"eslint-config-next": "^13.5.11",
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Align eslint-config-next with Next 14.

Version 13.x of eslint-config-next can conflict with Next 14 rules/peers. Bump to the 14.x line.

-    "eslint-config-next": "^13.5.11",
+    "eslint-config-next": "^14.2.0",
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"eslint-config-next": "^13.5.11",
"eslint-config-next": "^14.2.0",
🤖 Prompt for AI Agents
In package.json around line 30, the eslint-config-next dependency is pinned to
the 13.x line; update the version string to the 14.x line (e.g. replace
"eslint-config-next": "^13.5.11" with "eslint-config-next": "^14.0.0") and then
run your package manager (npm install or yarn install) to refresh lockfile and
node_modules so peer rules align with Next 14.

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.

2 participants