Based on this discussion: https://twitter.com/Freol/status/1768590666320290195 Let's implement a `near2ts` NPM package that would just take contract ABI (when available), and generate TypeScript types using `json2ts` or similar tool. See [this script](https://github.com/Protocol-Pawns/chess-on-chain/blob/master/abi-gen.sh) as a reference. I see the following usages: 1. In `package.json`, developers would use `near2ts` as `devDependency` and write custom `script` to call: ```sh near2ts ./contract.abi.json ``` 2. Users needing one-off generation of the types for an already published contract which has NEAR ABI support, so they can just run `near2ts` via `npx`: ```sh npx near2ts devhub.near ``` The challenge with the second command is that you would also need to specify a network/RPC, so it might be too heavy of a lift and maybe it is easier to rely on [near.cli.rs](https://near.cli.rs): ```sh near contract download-abi devhub.near save-to-file devhub_near.abi.json network-config mainnet now npx near2ts ./devhub_near.abi.json ``` Once you implement it, tweet about it, leave a comment here and in [Telegram @NEAR_Tools_Community_Group](https://t.me/NEAR_Tools_Community_Group) once you complete it, so we can bring more awareness to this tool in the ecosystem.