chore: Bump up jotai 2.10.1

[memoyil]

---

PR-Codex overview

This PR focuses on updating the version of the jotai package across multiple files and making minor adjustments to the getOnInit property in some hooks.

Detailed summary

• Updated jotai version to ^2.10.1 in pnpm-workspace.yaml.
• Changed jotai version from ^2.2.2 to ^2.10.1 in packages/ui-wallets/package.json.
• Updated jotai version to catalog: in several package.json files.
• Modified getOnInit property from unstable_getOnInit to getOnInit in apps/web/src/pages/usdv.tsx and apps/web/src/hooks/useUserAcknowledgement.ts.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 87f42c3

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
aptos-web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 21, 2024 10:42am
blog	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 21, 2024 10:42am
bridge	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 21, 2024 10:42am
games	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 21, 2024 10:42am
gamification	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 21, 2024 10:42am
uikit	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 21, 2024 10:42am
web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 21, 2024 10:42am

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	CI
Filesystem access	npm/hardhat@2.22.2	Module: fs-extra Location: Package overview	🚫
Filesystem access	npm/hardhat@2.22.2	Module: fs/promises Location: Package overview	🚫
Filesystem access	npm/hardhat@2.22.2	Module: fs Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: http_proxy Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: DO_NOT_SET_THIS_ENV_VAR____IS_HARDHAT_CI Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: TS_NODE_PROJECT Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: TS_NODE_FILES Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: key Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: HARDHAT_ENABLE_SENTRY Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: GITHUB_ACTIONS Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: DISPLAY Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: WAYLAND_DISPLAY Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: NOW Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: DEPLOYMENT_ID Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: CODEBUILD_BUILD_NUMBER Location: Package overview	🚫

View full report↗︎

Next steps

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/hardhat@2.22.2