Dependencies alignment across package

[pegaltier]

Hello, I use many of your package, I appreciate using it so I wanted to thank you for your great contribution!

Recently I have used the tool called npx @e18e/cli analyze (https://github.com/e18e/cli) to audit my project and the tools found 36 duplicate dependencies; many are linked to your packages because they can use a different version of the dependencies (often webpack) you can find below some of the warnings as example; so you can understand more the issue.

I would recommend to:

• take care to align the dependencies between the different package you publish
• webpack could be removed from the deps: already discussed it's included in the project deps but should not
• reconsider the usage of webpack, nowadays there are new standard like vite8/rolldown for instance

│ • [duplicate dependency] ts-loader has 2 installed versions:
│ 9.5.4 via the following 1 package(s) bitget-api@3.1.6
│ 8.4.0 via the following 2 package(s) binance@3.5.4, bybit-api@4.6.1
│ 💡 Suggestions
│ - Consider standardizing on version 8.4.0 as this version is the most commonly used.
│ - Consider upgrading consuming packages as this may resolve this duplicate version.
│
│ • [duplicate dependency] webpack-cli has 2 installed versions:
│ 4.10.0 via the following 3 package(s) bitget-api@3.1.6, bybit-api@4.6.1, gateio-api@1.5.0
│ 5.1.4 via the following 1 package(s) binance@3.5.4
│ 💡 Suggestions
│ - Consider standardizing on version 4.10.0 as this version is the most commonly used.
│ - Consider upgrading consuming packages as this may resolve this duplicate version.
│
│ • [duplicate dependency] ws has 2 installed versions:
│ 8.20.0 via the following 3 package(s) webpack-bundle-analyzer@5.3.0, bitget-api@3.1.6, gateio-api@1.5.0
│ 7.5.10 via the following 3 package(s) binance@3.5.4, bybit-api@4.6.1, webpack-bundle-analyzer@4.10.2
│ 💡 Suggestions
│ - Consider standardizing on version 8.20.0 as this version is the most commonly used.
│ - Consider upgrading consuming packages as this may resolve this duplicate version.
│
│ • [duplicate dependency] escape-string-regexp has 3 installed versions:
│ 4.0.0 via the following 1 package(s) webpack-bundle-analyzer@4.10.2
│ 1.0.5 via the following 1 package(s) figures@3.2.0
│ 5.0.0 via the following 1 package(s) webpack-bundle-analyzer@5.3.0
│ 💡 Suggestions
│ - Consider upgrading consuming packages as this may resolve this duplicate version.
│
│ • [duplicate dependency] html-escaper has 2 installed versions:
│ 2.0.2 via the following 1 package(s) webpack-bundle-analyzer@4.10.2
│ 3.0.3 via the following 1 package(s) webpack-bundle-analyzer@5.3.0
│ 💡 Suggestions
│ - Consider upgrading consuming packages as this may resolve this duplicate version.
│
│ • [duplicate dependency] sirv has 2 installed versions:
│ 2.0.4 via the following 1 package(s) webpack-bundle-analyzer@4.10.2
│ 3.0.2 via the following 1 package(s) webpack-bundle-analyzer@5.3.0
│ 💡 Suggestions
│ - Consider upgrading consuming packages as this may resolve this duplicate version.
│
│ • [duplicate dependency] webpack-bundle-analyzer has 2 installed versions:
│ 4.10.2 via the following 1 package(s) bybit-api@4.6.1
│ 5.3.0 via the following 3 package(s) binance@3.5.4, bitget-api@3.1.6, gateio-api@1.5.0
│ 💡 Suggestions
│ - Consider standardizing on version 5.3.0 as this version is the most commonly used.
│ - Consider upgrading consuming packages as this may resolve this duplicate version.
│

[JJ-Cro]

Hey, thanks for pointing it out. We have this in mind for a long time, but just some different packages have different needs. It is not as easy standardising everything, even though we know we should 😅

We will definitely keep this in mind and see to do it as soon as possible!

[tiagosiebler]

Also wanted to share my thanks for raising this. As @JJ-Cro said, it has been on our mind, but perhaps not enough! We'll figure out a better way to ensure dependency updates of this kind are properly synchronised across SDKs (without going down the monorepo path...)!