@sayari-accounts/sayari-oauth-sdk

Public npm package for Sayari OAuth SDK consumers.

This package now exposes stable subpath entrypoints for browser and Node integrations while keeping the root import available for browser usage.

Install

npm install @sayari-accounts/sayari-oauth-sdk

Import Paths

Browser applications:

import { createSayariOAuth } from '@sayari-accounts/sayari-oauth-sdk/browser';

Node backends:

import { createSayariOAuthNodeClient } from '@sayari-accounts/sayari-oauth-sdk/node';

Root import remains available and currently maps to the browser SDK:

import { createSayariOAuth } from '@sayari-accounts/sayari-oauth-sdk';

Browser Quick Start

import { createSayariOAuth } from '@sayari-accounts/sayari-oauth-sdk/browser';

const sayari = createSayariOAuth({
  appId: 'your-sayari-app-id',
  providerOrigin: 'https://accounts.sayarisoftware.co.tz',
  authorizeUrl: 'https://accounts.sayarisoftware.co.tz/oauth/authorize',
  redirectUri: 'https://client.example.com/auth/callback'
});

const authorization = await sayari.signIn({
  appName: 'Your App',
  appIcon: 'https://your-cdn.example.com/app-logo.webp',
  scope: 'openid profile email',
  deliveryMethod: 'email'
});

Node Quick Start

import { createSayariOAuthNodeClient } from '@sayari-accounts/sayari-oauth-sdk/node';

Notes

Consumers should use only these public entrypoints:

• @sayari-accounts/sayari-oauth-sdk
• @sayari-accounts/sayari-oauth-sdk/browser
• @sayari-accounts/sayari-oauth-sdk/node

They should not import from internal workspace paths like packages/sayari-oauth-browser.