Better exports

[wighawag]

Is your feature request related to a problem? Please describe.
Currently starknet.js export many of its utilities as object, which prevent best dead code elimination

Describe the solution you'd like
It would be better to expose the utils via package.json exports field

so if you were to export num utils this way in your package.json:

{
  "name": "starknet",
   ...
  "exports": {
    ".": {
      "import": {
        "types": "./dist/index.d.ts",
        "default": "./dist/index.js"
      }
    },
    "./utils": {
      "import": {
        "types": "./dist/utils/index.d.ts",
        "default": "./dist/utils/index.js"
      }
    },
    "./utils/num": {
      "import": {
        "types": "./dist/utils/num.d.ts",
        "default": "./dist/utils/num.js"
      }
    },
  },
...
}

we would then be able to import it this way and benefit from dead code elimination if we were to only use part of the num exports:

import {toBigInt} from 'starknet/utils/num';

Also another bonus is that it will let us access types defined there too

[od-hunter]

Hi @wighawag , can I be assigned this please?
I’m ready to work

[Benjtalkshow]

hello @wighawag
Can i be assigned to this task?
I propose restructuring Starknet.js to export utilities more modularly by utilizing the package.json exports field. This change will allow for better dead code elimination and enhance the ability to import only the needed utilities.

The benefit of doing this are:

1. By exposing individual utilities through the exports field, unused code can be excluded from the final bundle, resulting in smaller and more optimized builds.
2. Type-Safe Imports: Developers will be able to directly access types from each utility, improving code clarity and the developer experience, especially in TypeScript environments.