feat: 🎸 Add currency type

[chef-ryan]

---

PR-Codex overview

This PR introduces a new routing-sdk addon for ton, enhancing the SDK with a Currency type that includes NativeCurrency and Jetton. It also sets up testing and configuration files, and modifies dependencies to support React.

Detailed summary

• Added Currency type in src/currency.ts combining NativeCurrency and Jetton.
• Created Jetton class in src/Jetton.ts extending Token.
• Exported all from src/index.ts.
• Configured vitest for testing in vitest.config.ts.
• Updated tsconfig.json for TypeScript configuration.
• Added test for exports in index.test.ts.
• Updated package.json with new addon details and dependencies.
• Modified tsup.config.ts for build configuration.
• Adjusted package.json in utils to include React as a dependency.

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: a7db6d6

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	Dec 18, 2024 8:42am
blog	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 18, 2024 8:42am
bridge	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 18, 2024 8:42am
games	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 18, 2024 8:42am
gamification	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 18, 2024 8:42am
uikit	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 18, 2024 8:42am
web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 18, 2024 8: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	Source	CI
High CVE	npm/[email protected]	CVE: GHSA-3h5v-q93c-6h6q ws affected by a DoS when handling a request with many HTTP headers (HIGH) Affected versions: >= 7.0.0, < 7.5.10 Patched version: 7.5.10	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: DEBUG Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: key Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Location: Package overview	apps/bridge/package.json pnpm-lock.yaml	🚫
Environment variable access	npm/[email protected]	Env Vars: NODE_ENV Location: Package overview	apps/bridge/package.json pnpm-lock.yaml	🚫
Environment variable access	npm/[email protected]	Env Vars: NODE_ENV Location: Package overview	Source	🚫
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	apps/aptos/package.json pnpm-lock.yaml	🚫
High CVE	npm/[email protected]	CVE: GHSA-c24v-8rfc-w8vw Vite dev server option server.fs.deny can be bypassed when hosted on case-insensitive filesystem (HIGH) Affected versions: >= 4.0.0, <= 4.5.1 Patched version: 4.5.2	Source	🚫
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: TERM Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: DEBUG Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: key Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: VITE_DEBUG_FILTER Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: CI Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: VITE_USER_NODE_ENV Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: BROWSER Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: BROWSER_ARGS Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: NODE_ENV Location: Package overview	Source	🚫
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: TERM Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: key Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: DEBUG Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: VITE_DEBUG_FILTER Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: CI Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: DOTENV_KEY Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: DOTENV_KEY Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: DOTENV_KEY Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: VITE_USER_NODE_ENV Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: VITE_USER_NODE_ENV Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: BROWSER Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: BROWSER Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: BROWSER_ARGS Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: BROWSER_ARGS Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: key Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: VITE_CJS_IGNORE_WARNING Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: VITE_CJS_TRACE Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: WS_NO_BUFFER_UTIL Location: Package overview	Source	🚫
Environment variable access	npm/[email protected]	Env Vars: WS_NO_UTF_8_VALIDATE Location: Package overview	Source	🚫

View full report↗︎

Next steps

What is a CVE?

Contains a high severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

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.

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.

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]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment	0	1.03 MB	vercel-release-bot
npm/[email protected]	filesystem	0	95.7 kB	aleclarson

View full report↗︎