fix: create client with url #101
Merged
Conversation
This file contains 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
janndriessen
commented
Dec 12, 2024
| ): Promise<WrappedToken> { | ||
| // eslint-disable-next-line @typescript-eslint/no-non-null-assertion | ||
| const publicClient = createClient(chainId)! | ||
| const publicClient = createClientWithUrl(chainId, rpcUrl)! |
There was a problem hiding this comment.
The issue was the createClient would try to use a internal env var which is not available when used from clients like the API. So now we're passing the RPC URL.
|
🎉 This PR is included in version 3.18.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Updates create client to use a RPC URL as argument to be able to pass in the needed transport url (and not rely on an env var).