docs: improve Node.js/Fetch buyer quickstart with consistent signer usage#4
Open
gilbertsahumada wants to merge 2 commits into
Open
Conversation
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
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 updates the quickstart documentation for buyers to clarify and improve the instructions for using the
x402-fetchandx402-axioslibraries in Node.js. The changes focus on making the wallet/signer creation steps clearer and ensuring that code examples use consistent terminology and correct objects.Documentation improvements:
Node.js (viem)toNode.js - Fetchand added a clear code example for instantiating a signer usingcreateSignerfromx402-fetch, making the process more explicit for users.wrapFetchWithPaymentto usesigner(created withcreateSigner) instead ofaccount, ensuring the example matches the recommended usage and terminology.