refactor(transaction): fix #287 by deleting empty stub file simulateTransaction.ts

[Gezziy]

closes #287

Summary

This PR resolves issue #287 by deleting the empty stub file src/transaction/simulateTransaction.ts. The stub file was misleading developers looking for pre-flight simulation logic and polluting workspace searches. It has been replaced with a comment in src/transaction/index.ts pointing developers to the correct location (src/soroban/simulateTransaction.ts or client.soroban.simulate()).

We have verified that no other files in the codebase import from src/transaction/simulateTransaction.ts.

Changes Made

• [DELETE] src/transaction/simulateTransaction.ts (resolves src/transaction/simulateTransaction.ts Is an Empty Stub File That Misleads Contributors Searching for Simulation Logic #287)
  • Deleted file content:

    /**
     * NOTE: Transaction pre-flight simulation uses the Soroban RPC server
     * and therefore lives in src/soroban/simulateTransaction.ts.
     *
     * This file is intentionally empty — simulation is not a transaction
     * module concern. Access it via client.soroban.simulate().
     *
     * The client wires soroban.simulate() without this module importing
     * anything from soroban/.
     */

• [MODIFY] src/transaction/index.ts (resolves src/transaction/simulateTransaction.ts Is an Empty Stub File That Misleads Contributors Searching for Simulation Logic #287)
  • Added comment at the bottom of the file:

    // NOTE: Transaction pre-flight simulation uses the Soroban RPC server
    // and therefore lives in src/soroban/simulateTransaction.ts.
    // It can be accessed via client.soroban.simulate().

Import Verification

We performed a workspace grep search for simulateTransaction and confirmed that all active imports and invocations reference src/soroban/simulateTransaction.ts or client.soroban.simulate(). No imports are broken by deleting this file.

Testing

Verified that typecheck and build pass successfully:

npm run typecheck && npm run build

Output:

DTS ⚡️ Build success in 3183ms
ESM ⚡️ Build success in 3722ms
CJS ⚡️ Build success in 3722ms

[drips-wave]

@Gezziy Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits