Peter Smith

@SEEDART007 No - I don't believe it would be possible. There are plenty of other [issues](https://github.com/FuelLabs/fuels-ts/issues) you could pick up 😄

@richardgreg would this be the following utilities from Ethers.js you reference? - [formatUnit](https://docs.ethers.org/v5/api/utils/display-logic/#utils-formatUnits) - [parseUnit](https://docs.ethers.org/v5/api/utils/display-logic/#utils-parseUnits)

@arboleya It doesn't close this issue. #1867 references added the known types from the given generated ABI, and I believe this is referencing _infer_ the types at a class level.

Out of curiosity - how often is the API consumed in this way - whereby, the user isn't using the typegen? ```ts bytecode = fs.readFile(...) new Predicate({ bytecode, ... })...

I'd favour not implementing this change. The typegen is adding known types to the predicate, therefore, this change only benefits users on this alternative instantiation path. IMO the following type...

As part of #2218, I added `https://forum.fuel.network/` to the ignore list due to [flakey responses](https://github.com/FuelLabs/fuels-ts/actions/runs/8997757135/job/24716525725?pr=2218#step:9:274). I researched the solution outlined above and currently the [`textlint-rule-no-dead-link`](https://github.com/textlint-rule/textlint-rule-no-dead-link) does not support this behaviour....

Looks to me the rule `no-dead-link` is not being applied.

@arboleya I added some more context on what I was drawing my conclusion from. I'd like to see some more information on the common errors from contracts, scripts and predicate;...

> The relationship between `fuels` and `@fuels/connectors` looks problematic. > > Because one depends on the other, their cyclic dependency should always hunt us and delay releases. You are right...

@danielbate could you pop my name on this one for me please🥇