feat: New chains support for TWAP

[denis-orbs]

---

PR-Codex overview

This PR focuses on enhancing the TWAP_SUPPORTED_CHAINS in the utils.ts file, updating dependencies, and making adjustments to package versions across various files.

Detailed summary

• Updated TWAP_SUPPORTED_CHAINS to include ChainId.ARBITRUM_ONE, ChainId.BASE, and ChainId.LINEA.
• Increased versions for @orbs-network/twap-ui and @orbs-network/twap-ui-pancake to 0.11.8.
• Adjusted @reduxjs/toolkit version details in multiple files.
• Updated ts-node version details in multiple files.

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

[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	Dec 16, 2024 7:59am
blog	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 16, 2024 7:59am
bridge	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 16, 2024 7:59am
games	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 16, 2024 7:59am
gamification	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 16, 2024 7:59am
uikit	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 16, 2024 7:59am
web	❌ Failed (Inspect)			Dec 16, 2024 7:59am

[vercel]

@denis-orbs is attempting to deploy a commit to the PancakeSwap Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3709a34

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

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@orbs-network/[email protected]	Transitive: environment, eval, network	+20	19.5 MB	denis-orbs
npm/@orbs-network/[email protected]	environment, network Transitive: eval	+35	67.3 MB	denis-orbs
npm/[email protected]	environment	+1	591 kB	acemarke

🚮 Removed packages: npm/@orbs-network/[email protected], npm/@orbs-network/[email protected], npm/@testing-library/[email protected], npm/@testing-library/[email protected], npm/@testing-library/[email protected], npm/@testing-library/[email protected]

View full report↗︎

[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	Source	CI
Environment variable access	npm/[email protected]	Env Vars: NODE_ENV Location: Package overview	apps/gamification/package.json apps/web/package.json packages/uikit/package.json pnpm-lock.yaml	🚫

View full report↗︎

Next steps

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]