Getting rid of the Long dependency

[pyramation]

Getting rid of the Long dependency. It’s a fragile implementation and causes various issues in the module system. We can use BigInt for the objects these days and accept bigint | number | string in fromPartial.

[pyramation]

• [ ] investigate compat https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt
• [ ] https://github.com/cosmos/cosmjs/issues/1144

[webmaster128]

CosmJS depends on BigInt already through the @noble/hashes dependency. We'll not go backwards from here. The only environment that is struggeling with BigInt is React Native, but there seem to be ways to solve it. But this needs to be solved by the React Native community.

[pyramation]

Info about BigInt issues with babel for reference: https://stackoverflow.com/questions/57902010/how-to-use-bigint-exponentiation-with-babel

[pyramation]

when we get rid of the Long dependency, let's also make to

• [ ] remove the lines added from this commit

[webmaster128]

Could we start by using BigInt/Long as a configurable option? Then we can try it out and always go back if we run into trouble. Also different Telescope users might have different demands.

[pyramation]

Could we start by using BigInt/Long as a configurable option? Then we can try it out and always go back if we run into trouble. Also different Telescope users might have different demands.

absolutely. BigInt is the plan here :)

my general approach has been, let's keep the default output the same, and add everything as an option. Then we can use the options, once they're stable, we can change the defaults.

[webmaster128]

We now use telescope for the code-generation in cosmjs-types 0.6 and 0.7, which will be used automatically with the next CosmJS 0.30.

Personally I think getting looking into this feature would be a great step forward to reduce the dependency hell around long and @types/long.

[pyramation]

yes! I'm guessing we should look at:

1. what BigInt does to the encoders/decoders, etc
2. what settings do we need to be aware of for BigInt with babel, next, cra, and other builders/bundlers

cc @Zetazzz

[liangping]

That's great