docs: add programmable token transfers, non-EVM messaging, and Next.j…#165
Merged
docs: add programmable token transfers, non-EVM messaging, and Next.j…#165
Conversation
…s configs - Rename "Simple Message" to "Arbitrary Messaging (Data Only)" - Add explicit "Programmable Token Transfer" section (data + tokens) - Add cross-chain token transfer examples (EVM→Solana, EVM→Aptos) - Add EVM↔Aptos messaging examples - Link to central docs for non-EVM message building details - Clarify SDK auto-populates extraArgs for token-only transfers - Add Webpack EVM-only, Next.js EVM-only, and Next.js multi-chain configs - Add @noble/hashes version conflict section and troubleshooting
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
👋 aelmanaa, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
andrevmatos
approved these changes
Mar 3, 2026
Coverage Report |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request significantly improves the documentation for using the Chainlink CCIP SDK in browser environments and clarifies cross-chain messaging and token transfer usage. The updates focus on polyfill and dependency guidance for different bundlers, handling of dependency version conflicts, and clearer examples for cross-chain operations. The most important changes are grouped below.
Browser SDK Setup & Polyfill Guidance:
bufferpolyfill is required: only for Solana, TON, and Sui chains, not for EVM- or Aptos-only projects. Added detailed tables and bundler-specific notes (Vite, Webpack, Next.js) for polyfill requirements.resolve.aliasfor@noble/hashesand when to include polyfills for EVM-only vs. multi-chain projects. [1] [2] [3]"ERR_PACKAGE_PATH_NOT_EXPORTED"and"Buffer is not defined", with actionable solutions and cross-references to relevant sections.Dependency Version Conflict Resolution:
ethersand@mysten/suifor@noble/hashes, providing override/resolution instructions for npm, yarn, and pnpm, and emphasizing the need for a bundler alias to avoid runtime errors. [1] [2] [3] [4]tsconfig.jsonpaths.Cross-Chain Messaging & Token Transfer Examples:
extraArgsfor token-only transfers.extraArgs), and provided links to in-depth tutorials for Solana and Aptos message construction. [1] [2] [3] [4] [5] [6] [7] [8]General Improvements & Clarifications:
These changes make the SDK documentation more robust, developer-friendly, and accurate for multi-chain and cross-environment use cases.