@vue-solana/nuxt 4.1.1 → 4.1.3

package/README.md

@@ -64,6 +64,8 @@ New to Solana? Start with the official docs and the project concepts guide:
 | Solana client | Provided through `@vue-solana/core`                               |
 | Clusters      | `mainnet` (alias `mainnet-beta`), `devnet`, `testnet`, `localnet` |
 
+<br>
+
 ## Install
 
 ```sh
@@ -117,6 +119,8 @@ Nuxt module options are stored in public runtime config, so they must be JSON-se
 | `iosWallet`    | JSON-serializable iOS wallet options or `false`                      | Enabled on iOS browsers              | Configures or disables iOS browser wallet universal links (Phantom, Solflare, Backpack).      |
 | `clientPlugin` | `boolean`                                                            | `true`                               | Set to `false` to skip the module's runtime plugin and install `createSolanaPlugin` yourself. |
 
+<br>
+
 For development, use `devnet` and request free test SOL from the official faucet:
 
 ```txt
@@ -250,6 +254,8 @@ The module auto-imports these composables from direct `@vue-solana/vue/*` subpat
 | `useSolanaSendTransaction()`         | Plans, signs, submits, and confirms one transaction through the client.                                                                      |
 | `useSolanaSendTransactions()`        | Sends a batch of transactions (parallel or sequential) through the client.                                                                   |
 
+<br>
+
 The default client built by the module composes `solanaRpc()` followed by `rpcAirdrop()` when no `commitment` is configured (a configured `commitment` builds the same stack explicitly so it reaches the RPC layer); `solanaRpc()` installs `rpcTransactionPlanner()`, `rpcTransactionPlanSigningExecutor()`, and `rpcTransactionPlanSendingExecutor()` itself. The old custom fallback sender is not used. `useSolanaSendTransaction()` and `useSolanaSendTransactions()` therefore use the official client-sending capability, but the module does not configure a payer because `payer` and `payerSecretKey` are omitted from `ModuleOptions`. Their `sent` status is reached after the official executor completes its send-and-confirm operation at `confirmed` commitment.
 
 The runtime plugin is client-only. Auto-imported composables can be called during SSR and return inert state until hydration provides the real client context. Trigger RPC and wallet work from client lifecycle hooks or user actions.
@@ -350,7 +356,7 @@ const { publicKey, connected, canSignMessage, connect, disconnect } = useSolanaW
 
 Browser extension wallets are discovered through the Solana Wallet Standard. Android Mobile Wallet Adapter wallets are registered through `@solana-mobile/wallet-standard-mobile` on supported Android Chrome clients and exposed through the same wallet list. iOS Phantom, Solflare, and Backpack entries are exposed through wallet-specific universal links on iOS browsers. Wallet actions work after selecting a discovered wallet or configuring a custom `SolanaWallet`.
 
-Selected discovered wallets are persisted under `localStorage["vue-solana:selected-wallet"]` as non-sensitive identity metadata: `name`, and `platform`/`source` when available. On reload, Vue Solana restores the selected wallet if the same wallet is discovered again. Set `solana.autoConnect: true` to opt into calling `connect()` for that restored wallet; arbitrary installed wallets are never auto-connected. Calling `selectWallet(null)` or `setWallet(customWallet)` clears the stored selection.
+Selected discovered wallets are persisted under `localStorage["vue-solana:selected-wallet"]` as non-sensitive identity metadata: `name`, `platform`/`source` when available, and `connected: true` while the wallet is connected. On reload, Vue Solana restores the selected wallet if the same wallet is discovered again. A wallet the user left connected is restored after a reload even without `autoConnect`, through a silent connect (`connect({ silent: true })`) that does not prompt or launch a wallet app for wallets that honour the Wallet Standard `silent` hint (a wallet that ignores it can prompt on page load); an explicit `disconnect()` forgets that session. Set `solana.autoConnect: true` to also connect a restored wallet that was only selected; arbitrary installed wallets are never auto-connected. Calling `selectWallet(null)` or `setWallet(customWallet)` clears the stored selection.
 
 ## Message Signing
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vue-solana/nuxt",
-  "version": "4.1.1",
+  "version": "4.1.3",
   "description": "Nuxt module for Solana applications.",
   "license": "MIT",
   "keywords": [
@@ -45,7 +45,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@vue-solana/vue": "4.1.1"
+    "@vue-solana/vue": "4.1.3"
   },
   "peerDependencies": {
     "nuxt": "^3.0.0 || ^4.0.0"