Pairing with nexdk

beepr does not depend on nexdk, and nexdk does not depend on beepr. beepr keeps its own copy of the event union and handler type, identical to nexdk’s SdkEvent and SdkEventHandler. So a beepr handler can be passed as notify to createSdk:

import { createNotify } from 'beepr'
import { createSdk } from 'nexdk'

const notify = createNotify({
  onRequest: context => console.log('request', context.resource),
  onSuccess: data => console.log('success', data),
  onError: error => console.error('error', error.message),
})

const sdk = createSdk({
  drivers: {},
  notify,
})

The duplication is intentional: it is the price of independence. nexdk exports its own types, so you never need beepr just to type a handler. Use beepr when you want a typed adapter, redaction and composition instead of matching the raw (event, data) pair yourself.

Combine a global and a per-call handler

import { createNotify, mergeEventHandlers } from 'beepr'

const globalNotify = createNotify({ onError: error => console.error(error.message) })
const perCallNotify = createNotify({ onSuccess: () => console.log('Saved') })

const handler = mergeEventHandlers(globalNotify, perCallNotify)
handler?.('success', { id: 1 })