ts-sdk-types

To map Move numeric types like u128 and u256 to TypeScript, you should convert them to `bigint` to avoid precision errors. This ensures correct data representation when handling large balances returned from Move contracts.

Move addresses should be mapped to TypeScript `string` types for your Aptos SDK interactions. This conversion ensures correct data representation and prevents type mismatch errors in view and transaction payloads.

Formatting functionArguments and typeArguments for generic Move functions requires mapping them to correct TypeScript objects like TypeTag. This ensures the transaction payload accurately represents the expected Move data structures.

Your Move u64 balance loses precision because it is not mapped to a TypeScript `bigint`. Converting numeric types like u64, u128, and u256 to `bigint` avoids these precision errors during SDK interactions.

Yes, you can use this type mapping for both view and transaction payloads. It handles the conversion of numeric types to `bigint`, addresses to `string`, and TypeTag objects to ensure correct data representation across all SDK interactions.

The best way to handle TypeTag conversion is to map Move types directly to TypeScript TypeTag objects. This approach guarantees accurate data handling and correct argument formatting for generic Move functions.