pinia-plugin-subscription 0.1.6-beta.0 → 0.1.6

package/CHANGELOG.md

@@ -11,13 +11,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Added `execution` and `hydrationScheduler` support on `PluginSubscriber` / `PluginSubscriberInterface`.
 - Added `createHydrationPlugin()` as the dedicated Nuxt / SSR hydration helper.
 - Added `PluginSubscriptionOptions` for hydration-specific runtime overrides without changing the default `createPlugin()` API.
+- Added optional `hydrate()` and `afterHydration()` lifecycle hooks to the subscriber and base `Store` contract for SSR-safe initialization logic.
 
 ### Changed
 - The execution policy now defaults to the subscriber itself, with framework-specific overrides available only through the hydration helper.
 - `PluginSubscription` resolves hydration timing from the subscriber before falling back to the global runtime scheduler.
+- The base `Store` class now exposes lifecycle stubs so browser-only bootstrap code can be triggered after the plugin is accepted for execution instead of during construction.
 
 ### Fixed
 - Avoided SSR hydration crashes by allowing client-only Pinia plugins to be skipped on the server or deferred on the client.
+- Prevented browser-only initialization from running during server-side store creation by moving hydration bootstrap behind the subscriber lifecycle hooks.
 
 ## [0.1.5]
 

package/README.md

@@ -165,6 +165,9 @@ When `storeOptions.debug` is `true`, setup-context map size transitions are logg
 An object with at least an `invoke(context: PiniaPluginContext, debug?: boolean)` method, plus optional properties:
 
 - `execution?: { environment?: 'both' | 'client' | 'server'; hydration?: 'immediate' | 'defer' }`
+- `hydrationScheduler?: (run: () => void) => void`
+- `hydrate?: (context, debug) => void | Promise<void>` — optional hook for SSR-safe store initialization after the subscriber is accepted for execution
+- `afterHydration?: (context, debug) => void | Promise<void>` — optional lifecycle hook for post-hydration work
 - `resetStoreCallback?: (store?: any) => void`
 - `storeOnActionSubscription?: { store, callback }` (getter)
 - `storeMutationSubscription?: { store, callback }` (getter)
@@ -186,6 +189,7 @@ The project provides an abstract `PluginSubscriber` implementation (see [src/plu
 **Example:**
 
 ```typescript
+import { nextTick } from 'vue'
 import PluginSubscriber from 'pinia-plugin-subscription'
 import StoreExtension from './src/extending-pinia-store/core/StoreExtension'
 import { addStore } from './src/extending-pinia-store/plugins/stores'
@@ -207,6 +211,15 @@ class ExtendingStoreSubscriber extends PluginSubscriber<StoreExtension> {
 
     this.pluginCreated = addStore
   }
+
+  override hydrate() {
+    if (typeof window === 'undefined') {
+      return
+    }
+
+    // Safe browser-only initialization. This is only called when the policy allows it.
+    return this.storeInstance?.hydrate?.()
+  }
 }
 
 export const extendingStoreSubscriber = new ExtendingStoreSubscriber()
@@ -217,6 +230,7 @@ This example shows the recommended pattern for SSR / Nuxt-safe plugins:
 - `execution.environment` restricts the subscriber to `'both'`, `'client'`, or `'server'`
 - `execution.hydration` is `'immediate'` by default and can be set to `'defer'` when the plugin must wait for client hydration
 - `hydrationScheduler` lets you override the runtime scheduling behavior, for example with Nuxt/Vue `nextTick()`
+- `hydrate()` / `afterHydration()` are optional lifecycle hooks for browser-only initialization and post-hydration work; they help keep SSR-sensitive logic out of constructors
 
 ## The `Store` Class — Summary