Events

The client fires events whenever auth state changes. Subscribe with client.onX(callback) — every method returns an unsubscribe function.

Event reference

Using them

const unsubscribe = client.onTokenRefreshed((tokens) => {
  // Sync your global axios instance, websocket, etc.
  myWebsocket.updateAuth(tokens.accessToken);
});
 
// Later:
unsubscribe();

Async callbacks

onTokensSet and onTokensRemoved accept Promise-returning callbacks and the client will await them before resolving the originating action. Use this if you need to update other infrastructure (a global HTTP client, a service worker) before signaling success.

client.onTokensSet(async (tokens) => {
  await broadcastToWorkers(tokens.accessToken);
});

Direct emitter access

If you need more control — once(), multiple events at once, custom event names — the lower-level EventEmitter class is exported:

import { createAuthEventEmitter } from '@ackplus/nest-auth-client';
 
const emitter = createAuthEventEmitter();
emitter.once('logout', () => console.log('first logout!'));

You won't typically need this — client.onX() is the public API.

Server events vs client events

Server-side, the event emitter covers auth lifecycle on the backend. Client events are a much smaller surface — they're about local token state, not user lifecycle. If you want to react to "user signed up", listen to the server event in your backend; the client will simply receive the response.

Related

• AuthClient — every method that fires these events.
• Server events.