@absolutejs/auth 0.24.0 → 0.24.1

package/dist/types.d.ts

@@ -3,7 +3,7 @@ import { Cookie, status as statusType, redirect as redirectType } from 'elysia';
 import { ElysiaCustomStatusResponse } from 'elysia/error';
 import type { AuthIdentityConflict } from './errors';
 import type { AbsoluteAuthSessionStore } from './sessionTypes';
-import type { AuthHtmxConfig } from './ui/types';
+import type { AuthHtmxConfig, AuthHtmxUser } from './ui/types';
 export type AuthIntent = 'login' | 'link_identity' | 'link_connector';
 export type OAuth2ProviderClientConfiguration<Provider extends ProviderOption> = {
     credentials: CredentialsFor<Provider>;
@@ -154,8 +154,12 @@ export type AbsoluteAuthProps<UserType> = {
     /** Enable the built-in HTMX fragment routes (login, identities, connectors,
      *  account, signout, delete-account). Supply provider display data + the
      *  identity/connector data actions; the package owns the route wiring and
-     *  renderers. See @absolutejs/auth/ui to override individual fragments. */
-    htmx?: AuthHtmxConfig;
+     *  renderers. See @absolutejs/auth/ui to override individual fragments.
+     *
+     *  Only available when `UserType` has the fields the fragments render
+     *  (`sub` + optional email/name); users that don't enable HTMX are never
+     *  constrained. */
+    htmx?: UserType extends AuthHtmxUser ? AuthHtmxConfig : never;
     unregisteredSessionDurationMs?: number;
     resolveAuthIntent?: ResolveAuthIntent<UserType>;
     onAuthorizeSuccess?: OnAuthorizeSuccess;

package/package.json

@@ -1,5 +1,5 @@
 {
-	"version": "0.24.0",
+	"version": "0.24.1",
 	"name": "@absolutejs/auth",
 	"description": "An authorization library for absolutejs",
 	"repository": {