[Backend] Drop unused 'stellar-sdk' dependency — code only imports '@stellar/stellar-sdk'

[ogazboiz]

Join the discussion on Telegram

Why this matters

backend/package.json declares two Stellar SDK packages:

\"@stellar/stellar-sdk\": \"^14.5.0\",
...
\"stellar-sdk\": \"^13.3.0\",

But no source file under backend/src imports from stellar-sdk — every import uses @stellar/stellar-sdk. Confirmed by grep -rn \"from 'stellar-sdk'\" backend/src returning nothing.

This is a stale 30+ MB dependency that bloats install time and CI.

Acceptance criteria

• Remove stellar-sdk from backend/package.json (npm uninstall stellar-sdk)
• Confirm npm run build and npm test still pass

Files to touch

• backend/package.json
• package-lock.json (regenerated)

Out of scope

• Bumping @stellar/stellar-sdk itself

[romina-iurchik]

Hi, I'm Romina! This is a clean dependency cleanup I can take on. The old stellar-sdk (v13) is dead weight — every import in backend/src already uses @stellar/stellar-sdk (v14), as the grep in the issue confirms. My plan: run npm uninstall stellar-sdk to drop it from package.json and regenerate package-lock.json, then run npm run build and npm test to make sure nothing relied on it indirectly (e.g. as a transitive or peer dep). If both stay green, the stale 30+ MB package is gone and install/CI get lighter. I'll leave @stellar/stellar-sdk untouched per the out-of-scope note.