@playstack/auth-authjs

@playstack/auth-authjs connects successful Auth.js provider callbacks to application-owned Playstack authentication. It does not configure providers, replace Auth.js routing, or create a second identity database.

Install

After confirming preview access, install the package at your application's shared Playstack version:

npm install --save-exact @playstack/auth-authjs@0.1.0-beta.1

Check the peer requirements below before choosing a runtime or provider.

Configure the bridge

import { createAuthJsBridge } from '@playstack/auth-authjs'

const bridge = createAuthJsBridge({
  normalizeProfile: ({ provider, providerAccountId, profile }) => ({
    providerId: provider,
    providerUserId: providerAccountId,
    email: profile.email,
    emailVerified: profile.email_verified === true,
    raw: profile,
  }),
  authenticate: (profile) => auth.authenticateProfile(profile),
  resolveAccount: (userId) => activeAccountFor(userId),
  onAuthenticated: (user) => accounts.ensurePersonalAccount(user.id),
})

Attach bridge.callbacks to either an Auth.js Pages Router configuration or App Router factory. The bridge requires JWT sessions because its callback owns the encrypted Playstack principal.

CredentialService.authenticateProfile() is the canonical destination for the normalized result. Use authenticateProvider() only when Playstack also owns the authorization-code exchange. Both paths share the same verified-email, identity-linking, reservation, transaction, and event rules.

Boundary

Provider normalization and verified-email policy remain explicit. The session callback adds only session.playstack, an exact AuthSessionView without provider tokens or raw profile data. Provider handlers, cookies, middleware, and application module augmentation remain application-owned.

API entry points and requirements

Reference snapshot: @playstack/auth-authjs@0.1.0-beta.1. Import only the entry point your runtime needs. Paths below are relative to the installed package; use Go to Definition in your editor to inspect exact parameters, return types and overloads. Do not import the declaration-file paths directly.

Node.js engine requirement: >=20. This is not a claim that every entry point works in browsers or Workers.

Peer dependencies

Keep existing framework versions that satisfy these ranges. Install optional peers only when using the corresponding adapter. The package manager resolves ordinary dependencies separately.

For a complete first program, start with Getting started. For API lookup and partial-example conventions, see Reading the reference. Provider failures, lifecycle requirements and application responsibilities remain described in the guide above; types alone do not establish production safety.