chore: revert companion pattern except constants

[lukasaric]

Motivation and Resolution

Use companion pattern instead because of the type safety except constants to avoid build issues.
Tested by linking the newly built version within Starknet Wallet Account (linked it locally, also tested packed variant of project).

Next steps for new PR’s:

• Fix/improve the whole build process so that constants.ts works properly without using enums
• Fix namespaces issues Problems to use RPCSPEC06 and RPCSPEC07 namespaces #1137

RPC version (if applicable)

Usage related changes

n.a

Development related changes

n.a

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

[ivpavici]

@PhilippeR26 when you catch some time, could you test this solution please 🙏

[PhilippeR26]

I tested the cases of #1137 .
Still the same problem.
I see zero improvement.

[lukasaric]

I tested the cases of #1137 . Still the same problem. I see zero improvement.

As I said in the description, this issue is not covered via this PR (that’s a next step for a new follow up PR). I’ll update description to be more clear

[PhilippeR26]

I tested the cases of #1137 . Still the same problem. I see zero improvement.

As I said in the description, this issue is not covered via this PR (that’s a next step for a new follow up PR). I’ll update description to be more clear
🤔
So, what can be tested to verify this PR?

[lukasaric]

I tested the cases of #1137 . Still the same problem. I see zero improvement.

As I said in the description, this issue is not covered via this PR (that’s a next step for a new follow up PR). I’ll update description to be more clear
🤔
So, what can be tested to verify this PR?

Build needs to be tested in projects that are using starknet. I tested with your starknet wallet account repo and it’s working fine, but I wanted to double check with the author :)

[PhilippeR26]

Understood.
I have tested with :

• a node script using constants : ✅
• my most advanced DAPP : the Airdrop demo https://github.com/PhilippeR26/Airdrop-for-Starknet : ✅

[penovicp]

Mentioned a possible documentation issue. In general, double-checking how the documentation is affected might be worthwhile.

Aside from that lgtm

[tabaktoni]

Seems legit

[github-actions]

🎉 This issue has been resolved in version 6.13.1 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀