TokenManager

TokenManager is the abstract base class that manages the WooCommerce session-token lifecycle — issuing, refreshing, persisting, and clearing the auth / session / refresh tokens. It extends AsyncTokenManager from @woographql/session-utils and leaves storage to the subclass: each generated app ships a concrete manager (client, server, and/or middleware) that implements the storage primitives against cookies or localStorage.

It is exported from both entry points — @woographql/next (client-safe) and @woographql/next/server — because both the browser and server managers extend it.

import { TokenManager } from '@woographql/next';
// or, server-side:
import { TokenManager } from '@woographql/next/server';

A subclass implements the storage primitives; the base class provides the token lifecycle on top of them.

You rarely construct TokenManager directly — the install scaffolds a concrete subclass (e.g. a cookie-backed server manager). Extend it by implementing the storage primitives:

import { TokenManager } from '@woographql/next';

export class ClientTokenManager extends TokenManager {
  async getItem(key: string) {
    return localStorage.getItem(key);
  }
  async saveItem(key: string, value: string) {
    localStorage.setItem(key, value);
  }
  async saveItems(items: Record<string, string>) {
    for (const [k, v] of Object.entries(items)) localStorage.setItem(k, v);
  }
  async removeItem(key: string) {
    localStorage.removeItem(key);
  }
  async clear() {
    /* remove the managed keys */
  }
}

The concrete class is then handed to useTokenManager on the client, or to withTokenManager / withMiddlewareTokenManager on the server.

• useTokenManager — Bind a client TokenManager to the React session
• withTokenManager — Request-scoped server manager for route handlers
• withMiddlewareTokenManager — Attach credentials to proxied requests in middleware
• Library API — Overview of the runtime exports