-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AbstractAddress
is missing toEvmAddress
method
#3484
Comments
I believe it's due to cross-package dependencies. If we redistribute these interfaces to their appropriate packages, then I believe we could potentially remove the |
@xlzy905 in the meantime, a workaround would be to do the following: import { Address } from 'fuels';
// Should have full access to all address methods from here.
const address = Address.fromAddressOrString(myWallet.address);
address.toEvmAddress(); Apologies for this inconvenience. |
Okay. Thank you for your answer |
AbstractAddress
is missing toEvmAddress
method definition
AbstractAddress
is missing toEvmAddress
method definitionAbstractAddress
is missing toEvmAddress
method
fuels-ts SDK Version
0.97.2
Toolchain Versions
active toolchain ---------------- latest-aarch64-apple-darwin (default) forc : 0.49.3 - forc-client - forc-deploy : 0.49.3 - forc-run : 0.49.3 - forc-crypto : 0.49.3 - forc-doc : 0.49.3 - forc-explore : 0.28.1 - forc-fmt : 0.49.3 - forc-lsp : 0.49.3 - forc-tx : 0.49.3 - forc-wallet : not found fuel-core : 0.22.1 fuel-core-keygen : 0.22.1 fuels versions -------------- forc : 0.54.0
Node.js Version
No response
Browser
No response
Operating System
No response
Describe the Problem
When trying to use the toEvmAddress function from the AbstractAddress type, TypeScript throws an error because the function is not defined in the type. This issue occurs during the import process and prevents proper usage of the function in TypeScript.
FUEL_PROVIDER_URL = "https://mainnet.fuel.network/v1/graphql";
Code Snippet
No response
Contract ABI
No response
Errors
No response
The text was updated successfully, but these errors were encountered: