fix: export abi types

[tabaktoni]

Motivation and Resolution

...

RPC version (if applicable)

...

Usage related changes

• Change 1.
• ...

Development related changes

• Change 1.
• ...

Checklist:

• Performed a self-review of the code
• Rebased to the last commit of the target branch (or merged it into my branch)
• Linked the issues which this PR resolves
• Documented the changes in code (API docs will be generated automatically)
• Updated the tests
• All tests are passing

[PhilippeR26]

Seems that rpc spec 0.6 is identical to rpc spec 0.7 about contract types.
In this case, for any src/utils code , is it better to use the internal rpcspec_06, or to use the rpcspec 0.7 of the types-js library?

[tabaktoni]

Seems that rpc spec 0.6 is identical to rpc spec 0.7 about contract types. In this case, for any src/utils code , is it better to use the internal rpcspec_06, or to use the rpcspec 0.7 of the types-js library?

Yea, abi didn't change, I would recommend using rpcspec 0.7 as it is the latest one, and 0.6 will be deprecated at some point. I updated this one for convenience.

[PhilippeR26]

So, you should also add exports to these functions in the types-js lib (I have seen you commit this), and publish in npm.

[tabaktoni]

So, you should also add exports to these functions in the types-js lib.

Yes it is added

[PhilippeR26]

OK for me