SSR

Supported

Yes, the library supports SSR, but you should treat each request as a separate manager lifecycle.

For real-world integrations, look at:

• Vite demo app
• After.js / Razzle example
• NextJS example

Recommended pattern

Create a new manager per request and destroy it at the end:

const manager = new Manager();

try {
  await manager.init();
  // render request
} finally {
  manager.destroy();
}

Why destroy() matters

GC handles unreachable objects, but it does not unsubscribe listeners registered on long-lived resources for you.

Examples that need cleanup:

• process.on(...)
• global event emitters
• sockets
• intervals
• database or cache subscriptions

manager.destroy() gives you explicit teardown and triggers:

• onDestroy
• cleanup returned from init
• internal store cleanup

On the server the manager arms no destroy timers (destroyTimers only apply in the browser): stores live exactly as long as the request, and destroy() is the only teardown.

Practical guidance

Do:

• create one manager per request
• call manager.destroy() in finally
• keep SSR initState request-scoped
• disable persist on the server when needed

Do not:

• share request stores across requests
• keep request-local stores in module-level singletons
• rely on GC as a replacement for explicit teardown