Complete RPC migration: update package imports and add notes for unsupported features

Co-authored-by: tamirms <1445829+tamirms@users.noreply.github.com>

Author: Copilot

docs/build/apps/example-application-tutorial/manage-trust.mdx

@@ -146,8 +146,8 @@ import {
   Networks,
   Operation,
   Asset,
-} from "stellar-sdk";
-import { Server } from "stellar-sdk/rpc";
+} from "@stellar/stellar-sdk";
+import { Server } from "@stellar/stellar-sdk/rpc";
 import { error } from "@sveltejs/kit";
 
 // We are setting a very high maximum fee, which increases our transaction's

docs/build/apps/example-application-tutorial/querying-data.mdx

@@ -22,8 +22,8 @@ import {
   Networks,
   StrKey,
   Asset,
-} from "stellar-sdk";
-import { Server } from "stellar-sdk/rpc";
+} from "@stellar/stellar-sdk";
+import { Server } from "@stellar/stellar-sdk/rpc";
 
 const rpcUrl = "https://soroban-testnet.stellar.org";
 const server = new Server(rpcUrl);
@@ -38,11 +38,11 @@ const server = new Server(rpcUrl);
 
 // We'll import some type definitions that already exists within the
 // We'll import some type definitions that already exists within the
-// `stellar-sdk` package, so our functions will know what to expect.
-/** @typedef {import('stellar-sdk').ServerApi.AccountRecord} AccountRecord */
-/** @typedef {import('stellar-sdk').ServerApi.PaymentOperationRecord} PaymentOperationRecord */
-/** @typedef {import('stellar-sdk').Transaction} Transaction */
-/** @typedef {import('stellar-sdk').ServerApi.PaymentPathRecord} PaymentPathRecord */
+// `@stellar/stellar-sdk` package, so our functions will know what to expect.
+/** @typedef {import('@stellar/stellar-sdk').ServerApi.AccountRecord} AccountRecord */
+/** @typedef {import('@stellar/stellar-sdk').ServerApi.PaymentOperationRecord} PaymentOperationRecord */
+/** @typedef {import('@stellar/stellar-sdk').Transaction} Transaction */
+/** @typedef {import('@stellar/stellar-sdk').ServerApi.PaymentPathRecord} PaymentPathRecord */
 ```
 
 **Source:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/rpcQueries.js
@@ -254,23 +254,37 @@ export async function findStrictSendPaths({
   sourceAmount,
   destinationPublicKey,
 }) {
-  let asset =
-    sourceAsset === "native"
-      ? Asset.native()
-      : new Asset(sourceAsset.split(":")[0], sourceAsset.split(":")[1]);
-  let response = await server
-    .strictSendPaths(asset, sourceAmount.toString(), destinationPublicKey)
-    .call();
-  if (response.records.length > 0) {
-    return response.records;
-  } else {
-    throw error(400, { message: "no strict send paths available" });
-  }
+  // Note: RPC does not provide direct path finding endpoints like Horizon.
+  // For production applications, consider using:
+  // 1. External indexing services that provide path finding
+  // 2. Stellar DEX aggregators
+  // 3. Build your own path finding using getLedgerEntries to query offers
+  
+  throw error(501, { 
+    message: "Path finding not directly available in RPC. Consider using external indexing services or DEX aggregators." 
+  });
+  
+  // Alternative: You could implement basic path finding by querying offers:
+  // const offers = await server.getLedgerEntries({
+  //   keys: [/* offer keys */]
+  // });
+  // // Then process offers to find paths
 }
 ```
 
 **Source:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/rpcQueries.js
 
+:::note
+
+RPC does not provide direct path finding capabilities like Horizon's `strictSendPaths` and `strictReceivePaths`. For production applications requiring path finding, consider:
+
+- Using external indexing services
+- Integrating with DEX aggregators  
+- Building custom path finding logic using `getLedgerEntries` to query offers
+- Using [Hubble](../../../data/analytics/hubble/README.mdx) for DEX analytics
+
+:::
+
 ## findStrictReceivePaths
 
 Find the available strict receive paths between a source account and receiving asset/amount.
@@ -292,23 +306,24 @@ export async function findStrictReceivePaths({
   destinationAsset,
   destinationAmount,
 }) {
-  let asset =
-    destinationAsset === "native"
-      ? Asset.native()
-      : new Asset(
-          destinationAsset.split(":")[0],
-          destinationAsset.split(":")[1],
-        );
-  let response = await server
-    .strictReceivePaths(sourcePublicKey, asset, destinationAmount.toString())
-    .call();
-  if (response.records.length > 0) {
-    return response.records;
-  } else {
-    throw error(400, { message: "no strict receive paths available" });
-  }
+  // Note: RPC does not provide direct path finding endpoints like Horizon.
+  // For production applications, consider using:
+  // 1. External indexing services that provide path finding
+  // 2. Stellar DEX aggregators
+  // 3. Build your own path finding using getLedgerEntries to query offers
+  
+  throw error(501, { 
+    message: "Path finding not directly available in RPC. Consider using external indexing services or DEX aggregators." 
+  });
+  
+  // Alternative: You could implement basic path finding by querying offers:
+  // const offers = await server.getLedgerEntries({
+  //   keys: [/* offer keys */]
+  // });
+  // // Then process offers to find paths
 }
 ```
+```
 
 **Source:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/rpcQueries.js