algorand-typescript

To fix Puya compiler errors in Algorand TypeScript, enforce AVM-compliant patterns by using explicit uint64 or Uint64 types, avoiding JavaScript numbers, and applying clone() for complex values. Proper ABI method conventions and careful array handling also prevent common compilation failures.

You need to use clone() for complex values in Algorand TypeScript when handling arrays or interacting with storage patterns like GlobalState and BoxMap. Cloning ensures correct value semantics and prevents unintended reference mutations within the AVM architecture.

AVM type rules for PuyaTs smart contracts require explicit use of uint64 or Uint64 for numerical values. You must strictly avoid JavaScript numbers to ensure value semantics remain AVM-compliant and to prevent unexpected runtime behavior during contract execution.

To implement storage patterns like GlobalState and BoxMap in PuyaTs, follow explicit storage access rules that include read and write cloning for complex values. You must also account for MBR considerations when managing contract state to ensure transactions succeed.

No, you cannot use standard JavaScript numbers in Algorand TypeScript smart contracts. The PuyaTs syntax enforces AVM-compliant patterns by requiring explicit uint64 or Uint64 types to maintain strict value semantics and prevent compiler errors.

Your Algorand TypeScript contract fails with union type errors because PuyaTs enforces strict value semantics and union avoidance. To resolve this, ensure explicit AVM type usage and apply clone() semantics to complex values before storage access or array manipulation.