@molecule/api-external-auth-supabase 1.0.0

package/LICENSE

@@ -0,0 +1,115 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work.
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship.
+
+      "Contribution" shall mean any work of authorship, including the
+      original version of the Work and any modifications or additions
+      to that Work, that is intentionally submitted to the Licensor for
+      inclusion in the Work by the copyright owner or by an individual or
+      Legal Entity authorized to submit on behalf of the copyright owner.
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by the Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      patent license to make, have made, use, offer to sell, sell, import,
+      and otherwise transfer the Work.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file.
+
+   5. Submission of Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND.
+
+   8. Limitation of Liability. In no event and under no legal theory shall
+      any Contributor be liable to You for damages.
+
+   9. Accepting Warranty or Additional Liability.
+
+   Copyright 2026 Molecule Dev, Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/dist/browser-guard.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=browser-guard.d.ts.map

package/dist/browser-guard.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"browser-guard.d.ts","sourceRoot":"","sources":["../src/browser-guard.ts"],"names":[],"mappings":"AAuBA,OAAO,EAAE,CAAA"}

package/dist/browser-guard.js

@@ -0,0 +1,18 @@
+/**
+ * Browser guard — `@molecule/api-external-auth-supabase` is SERVER-ONLY.
+ *
+ * Generated by scripts/gen-browser-guards.mjs (workspace root) — edit THAT, not this.
+ * Evaluating a server package in a browser bundle is always an import-graph mistake
+ * (node APIs, secrets); without this guard it surfaces as a cryptic downstream crash
+ * ("Buffer is not defined") far from the culprit. Throwing here names the package and
+ * the fix at the exact moment the client bundle evaluates it. jsdom tests and SSR are
+ * unaffected: the throw requires browser globals AND the absence of a node runtime.
+ */
+const g = globalThis;
+if (g.window !== undefined && g.document !== undefined && !g.process?.versions?.node) {
+    throw new Error('@molecule/api-external-auth-supabase is SERVER-ONLY: it was bundled into browser/client code. Import it only ' +
+        'from server code (a server route/function or your API), or dynamic-import it inside ' +
+        'the server handler — never from components or shared client modules, and never ' +
+        'polyfill Buffer/process to silence this.');
+}
+export {};

package/dist/client.d.ts

@@ -0,0 +1,40 @@
+import { type SupabaseClient } from '@supabase/supabase-js';
+/**
+ * Returns the anon-key Supabase client (lazy singleton). Created on first
+ * call from the resolved settings — explicit `configureSupabase()` values
+ * first, env fallbacks second (`SUPABASE_URL` ?? `VITE_SUPABASE_URL`, and
+ * `SUPABASE_ANON_KEY` ?? `VITE_SUPABASE_ANON_KEY` ??
+ * `VITE_SUPABASE_PUBLISHABLE_KEY`).
+ *
+ * The anon key is PUBLIC — this client requires no secret and is constrained
+ * by Row Level Security. Use it for `verifyUserToken()` and for PostgREST
+ * reads/writes that RLS already permits.
+ *
+ * @throws {Error} When neither `configureSupabase()` nor the environment provides a
+ *   URL + anon key — the error names exactly which env keys are missing.
+ */
+export declare const getAnonClient: () => SupabaseClient;
+/**
+ * Whether a service-role key is available (explicitly configured or via
+ * `SUPABASE_SERVICE_ROLE_KEY`). ALWAYS check this before calling
+ * `getServiceClient()` — molecule sandboxes do NOT provision the key by
+ * default, so admin paths must degrade gracefully or ask the user to
+ * connect it.
+ */
+export declare const hasServiceRole: () => boolean;
+/**
+ * Returns the service-role (admin) Supabase client (lazy singleton). Bypasses
+ * Row Level Security — server-only, for admin operations the anon client
+ * cannot perform.
+ *
+ * @throws {Error} When no service-role key is connected (guard with
+ *   `hasServiceRole()`), or when no project URL is configured.
+ */
+export declare const getServiceClient: () => SupabaseClient;
+/**
+ * Test hook: clears the cached clients AND any settings set via
+ * `configureSupabase()`, returning the module to its pristine state. The next
+ * client creation re-reads the environment from scratch.
+ */
+export declare const resetSupabase: () => void;
+//# sourceMappingURL=client.d.ts.map

package/dist/client.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"client.d.ts","sourceRoot":"","sources":["../src/client.ts"],"names":[],"mappings":"AAAA,OAAO,EAAgB,KAAK,cAAc,EAAE,MAAM,uBAAuB,CAAA;AAgBzE;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,aAAa,QAAO,cAiBhC,CAAA;AAED;;;;;;GAMG;AACH,eAAO,MAAM,cAAc,QAAO,OAAoD,CAAA;AAEtF;;;;;;;GAOG;AACH,eAAO,MAAM,gBAAgB,QAAO,cAgBnC,CAAA;AAED;;;;GAIG;AACH,eAAO,MAAM,aAAa,QAAO,IAIhC,CAAA"}

package/dist/client.js

@@ -0,0 +1,84 @@
+import { createClient } from '@supabase/supabase-js';
+import { resolveSettings, state } from './state.js';
+/**
+ * Server-appropriate client options: no session persistence, no background
+ * token refresh, no URL-fragment session detection.
+ */
+const SERVER_CLIENT_OPTIONS = {
+    auth: {
+        persistSession: false,
+        autoRefreshToken: false,
+        detectSessionInUrl: false,
+    },
+};
+/**
+ * Returns the anon-key Supabase client (lazy singleton). Created on first
+ * call from the resolved settings — explicit `configureSupabase()` values
+ * first, env fallbacks second (`SUPABASE_URL` ?? `VITE_SUPABASE_URL`, and
+ * `SUPABASE_ANON_KEY` ?? `VITE_SUPABASE_ANON_KEY` ??
+ * `VITE_SUPABASE_PUBLISHABLE_KEY`).
+ *
+ * The anon key is PUBLIC — this client requires no secret and is constrained
+ * by Row Level Security. Use it for `verifyUserToken()` and for PostgREST
+ * reads/writes that RLS already permits.
+ *
+ * @throws {Error} When neither `configureSupabase()` nor the environment provides a
+ *   URL + anon key — the error names exactly which env keys are missing.
+ */
+export const getAnonClient = () => {
+    if (state.anonClient)
+        return state.anonClient;
+    const { url, anonKey } = resolveSettings();
+    if (!url || !anonKey) {
+        const missing = [
+            ...(url ? [] : ['SUPABASE_URL (or VITE_SUPABASE_URL)']),
+            ...(anonKey
+                ? []
+                : ['SUPABASE_ANON_KEY (or VITE_SUPABASE_ANON_KEY / VITE_SUPABASE_PUBLISHABLE_KEY)']),
+        ];
+        throw new Error(`@molecule/api-supabase is not configured: missing ${missing.join(' and ')}. ` +
+            'Set the env var(s) in the Environment panel or call configureSupabase({ url, anonKey }).');
+    }
+    state.anonClient = createClient(url, anonKey, SERVER_CLIENT_OPTIONS);
+    return state.anonClient;
+};
+/**
+ * Whether a service-role key is available (explicitly configured or via
+ * `SUPABASE_SERVICE_ROLE_KEY`). ALWAYS check this before calling
+ * `getServiceClient()` — molecule sandboxes do NOT provision the key by
+ * default, so admin paths must degrade gracefully or ask the user to
+ * connect it.
+ */
+export const hasServiceRole = () => Boolean(resolveSettings().serviceRoleKey);
+/**
+ * Returns the service-role (admin) Supabase client (lazy singleton). Bypasses
+ * Row Level Security — server-only, for admin operations the anon client
+ * cannot perform.
+ *
+ * @throws {Error} When no service-role key is connected (guard with
+ *   `hasServiceRole()`), or when no project URL is configured.
+ */
+export const getServiceClient = () => {
+    if (state.serviceClient)
+        return state.serviceClient;
+    const { url, serviceRoleKey } = resolveSettings();
+    if (!serviceRoleKey) {
+        throw new Error('SUPABASE_SERVICE_ROLE_KEY is not connected. Ask the user to add it in the Environment panel — never assume it exists.');
+    }
+    if (!url) {
+        throw new Error('@molecule/api-supabase is not configured: missing SUPABASE_URL (or VITE_SUPABASE_URL). ' +
+            'Set the env var in the Environment panel or call configureSupabase({ url }).');
+    }
+    state.serviceClient = createClient(url, serviceRoleKey, SERVER_CLIENT_OPTIONS);
+    return state.serviceClient;
+};
+/**
+ * Test hook: clears the cached clients AND any settings set via
+ * `configureSupabase()`, returning the module to its pristine state. The next
+ * client creation re-reads the environment from scratch.
+ */
+export const resetSupabase = () => {
+    state.settings = {};
+    state.anonClient = null;
+    state.serviceClient = null;
+};

package/dist/config.d.ts

@@ -0,0 +1,13 @@
+import type { SupabaseSettings } from './types.js';
+/**
+ * Explicitly sets (part of) the Supabase connection settings, overriding the
+ * corresponding environment-variable fallbacks.
+ *
+ * Merges with any previously configured settings, so it can be called with
+ * just the piece that changed (e.g. only `serviceRoleKey` once the user
+ * connects it). Invalidates the cached client singletons so the next
+ * `getAnonClient()` / `getServiceClient()` call reflects the new settings.
+ * Use `resetSupabase()` for a full clean slate.
+ */
+export declare const configureSupabase: (settings: SupabaseSettings) => void;
+//# sourceMappingURL=config.d.ts.map

package/dist/config.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"config.d.ts","sourceRoot":"","sources":["../src/config.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,YAAY,CAAA;AAElD;;;;;;;;;GASG;AACH,eAAO,MAAM,iBAAiB,GAAI,UAAU,gBAAgB,KAAG,IAI9D,CAAA"}

package/dist/config.js

@@ -0,0 +1,16 @@
+import { state } from './state.js';
+/**
+ * Explicitly sets (part of) the Supabase connection settings, overriding the
+ * corresponding environment-variable fallbacks.
+ *
+ * Merges with any previously configured settings, so it can be called with
+ * just the piece that changed (e.g. only `serviceRoleKey` once the user
+ * connects it). Invalidates the cached client singletons so the next
+ * `getAnonClient()` / `getServiceClient()` call reflects the new settings.
+ * Use `resetSupabase()` for a full clean slate.
+ */
+export const configureSupabase = (settings) => {
+    state.settings = { ...state.settings, ...settings };
+    state.anonClient = null;
+    state.serviceClient = null;
+};

package/dist/index.d.ts

@@ -0,0 +1,86 @@
+/**
+ * External authentication provider using Supabase — first-class support for
+ * apps imported into molecule.dev that were built on Supabase (Lovable and
+ * similar).
+ *
+ * Implements the `@molecule/api-external-auth` contract: the exported
+ * `provider` verifies a user's Supabase JWT server-side via the anon client's
+ * `auth.getUser(token)`. Two tiers:
+ *
+ * - **No-secret tier** (works out of the box): token verification and
+ *   RLS-constrained PostgREST access via `getAnonClient()` — both using only
+ *   the PUBLIC anon key (`SUPABASE_ANON_KEY` / `VITE_SUPABASE_ANON_KEY` /
+ *   `VITE_SUPABASE_PUBLISHABLE_KEY`). No secret required.
+ * - **Connected tier**: once the user supplies `SUPABASE_SERVICE_ROLE_KEY`,
+ *   `getServiceClient()` returns an admin client that bypasses Row Level
+ *   Security. Gate every admin path with `hasServiceRole()`.
+ *
+ * Settings come from `configureSupabase()` or, lazily at first client
+ * creation, from env: `SUPABASE_URL` ?? `VITE_SUPABASE_URL`,
+ * `SUPABASE_ANON_KEY` ?? `VITE_SUPABASE_ANON_KEY` ??
+ * `VITE_SUPABASE_PUBLISHABLE_KEY`, `SUPABASE_SERVICE_ROLE_KEY`.
+ * `resetSupabase()` clears cached clients + settings (test hook).
+ *
+ * @example
+ * ```ts
+ * // bonds.ts — wire the provider at startup:
+ * import { setProvider } from '@molecule/api-external-auth'
+ * import { provider } from '@molecule/api-external-auth-supabase'
+ *
+ * setProvider(provider)
+ *
+ * // Then server routes verify the token the frontend already sends:
+ * import { verifyUserToken } from '@molecule/api-external-auth'
+ *
+ * app.get('/api/me', async (req, res) => {
+ *   const token = req.headers.authorization?.replace(/^Bearer /, '') ?? ''
+ *   const user = await verifyUserToken(token)
+ *   if (!user) {
+ *     res.status(401).json({ error: 'Invalid or expired session.' })
+ *     return
+ *   }
+ *   res.json({ userId: user.userId, email: user.email })
+ * })
+ * ```
+ *
+ * @example
+ * ```ts
+ * // Admin operations need the service-role key — ALWAYS gate on hasServiceRole():
+ * import { getServiceClient, hasServiceRole } from '@molecule/api-external-auth-supabase'
+ *
+ * if (hasServiceRole()) {
+ *   const admin = getServiceClient()
+ *   await admin.from('profiles').update({ suspended: true }).eq('id', targetId)
+ * } else {
+ *   // Degrade: store the flag in the provisioned DATABASE_URL Postgres,
+ *   // or ask the user to connect SUPABASE_SERVICE_ROLE_KEY in the
+ *   // Environment panel.
+ * }
+ * ```
+ *
+ * @remarks
+ * - The anon key is PUBLIC (it ships in the browser bundle of every Supabase
+ *   app) — `provider.verifyUserToken()` and `getAnonClient()` need NO secret.
+ *   Do not treat a missing service-role key as "Supabase is unusable".
+ * - `SUPABASE_SERVICE_ROLE_KEY` is NOT provisioned in molecule sandboxes and
+ *   never will be by default. Check `hasServiceRole()` and degrade gracefully
+ *   or ask the user to connect it in the Environment panel — never assume it
+ *   exists. Migrations/DDL against the user's hosted Supabase database cannot
+ *   run from the sandbox.
+ * - New server-side tables belong in the provisioned `DATABASE_URL` Postgres,
+ *   NOT in the user's hosted Supabase — unless the user has connected
+ *   Supabase credentials that allow it.
+ * - This package is SERVER-ONLY. It throws immediately if bundled into
+ *   browser/client code — import it only from server code, and never polyfill
+ *   `Buffer`/`process` to silence the guard.
+ *
+ * @see https://www.npmjs.com/package/@supabase/supabase-js
+ *
+ * @module
+ */
+export * from './browser-guard.js';
+export * from './client.js';
+export * from './config.js';
+export * from './provider.js';
+export * from './types.js';
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+EG;AAEH,cAAc,oBAAoB,CAAA;AAClC,cAAc,aAAa,CAAA;AAC3B,cAAc,aAAa,CAAA;AAC3B,cAAc,eAAe,CAAA;AAC7B,cAAc,YAAY,CAAA"}

package/dist/index.js

@@ -0,0 +1,85 @@
+/**
+ * External authentication provider using Supabase — first-class support for
+ * apps imported into molecule.dev that were built on Supabase (Lovable and
+ * similar).
+ *
+ * Implements the `@molecule/api-external-auth` contract: the exported
+ * `provider` verifies a user's Supabase JWT server-side via the anon client's
+ * `auth.getUser(token)`. Two tiers:
+ *
+ * - **No-secret tier** (works out of the box): token verification and
+ *   RLS-constrained PostgREST access via `getAnonClient()` — both using only
+ *   the PUBLIC anon key (`SUPABASE_ANON_KEY` / `VITE_SUPABASE_ANON_KEY` /
+ *   `VITE_SUPABASE_PUBLISHABLE_KEY`). No secret required.
+ * - **Connected tier**: once the user supplies `SUPABASE_SERVICE_ROLE_KEY`,
+ *   `getServiceClient()` returns an admin client that bypasses Row Level
+ *   Security. Gate every admin path with `hasServiceRole()`.
+ *
+ * Settings come from `configureSupabase()` or, lazily at first client
+ * creation, from env: `SUPABASE_URL` ?? `VITE_SUPABASE_URL`,
+ * `SUPABASE_ANON_KEY` ?? `VITE_SUPABASE_ANON_KEY` ??
+ * `VITE_SUPABASE_PUBLISHABLE_KEY`, `SUPABASE_SERVICE_ROLE_KEY`.
+ * `resetSupabase()` clears cached clients + settings (test hook).
+ *
+ * @example
+ * ```ts
+ * // bonds.ts — wire the provider at startup:
+ * import { setProvider } from '@molecule/api-external-auth'
+ * import { provider } from '@molecule/api-external-auth-supabase'
+ *
+ * setProvider(provider)
+ *
+ * // Then server routes verify the token the frontend already sends:
+ * import { verifyUserToken } from '@molecule/api-external-auth'
+ *
+ * app.get('/api/me', async (req, res) => {
+ *   const token = req.headers.authorization?.replace(/^Bearer /, '') ?? ''
+ *   const user = await verifyUserToken(token)
+ *   if (!user) {
+ *     res.status(401).json({ error: 'Invalid or expired session.' })
+ *     return
+ *   }
+ *   res.json({ userId: user.userId, email: user.email })
+ * })
+ * ```
+ *
+ * @example
+ * ```ts
+ * // Admin operations need the service-role key — ALWAYS gate on hasServiceRole():
+ * import { getServiceClient, hasServiceRole } from '@molecule/api-external-auth-supabase'
+ *
+ * if (hasServiceRole()) {
+ *   const admin = getServiceClient()
+ *   await admin.from('profiles').update({ suspended: true }).eq('id', targetId)
+ * } else {
+ *   // Degrade: store the flag in the provisioned DATABASE_URL Postgres,
+ *   // or ask the user to connect SUPABASE_SERVICE_ROLE_KEY in the
+ *   // Environment panel.
+ * }
+ * ```
+ *
+ * @remarks
+ * - The anon key is PUBLIC (it ships in the browser bundle of every Supabase
+ *   app) — `provider.verifyUserToken()` and `getAnonClient()` need NO secret.
+ *   Do not treat a missing service-role key as "Supabase is unusable".
+ * - `SUPABASE_SERVICE_ROLE_KEY` is NOT provisioned in molecule sandboxes and
+ *   never will be by default. Check `hasServiceRole()` and degrade gracefully
+ *   or ask the user to connect it in the Environment panel — never assume it
+ *   exists. Migrations/DDL against the user's hosted Supabase database cannot
+ *   run from the sandbox.
+ * - New server-side tables belong in the provisioned `DATABASE_URL` Postgres,
+ *   NOT in the user's hosted Supabase — unless the user has connected
+ *   Supabase credentials that allow it.
+ * - This package is SERVER-ONLY. It throws immediately if bundled into
+ *   browser/client code — import it only from server code, and never polyfill
+ *   `Buffer`/`process` to silence the guard.
+ *
+ * @see https://www.npmjs.com/package/@supabase/supabase-js
+ *
+ * @module
+ */
+export * from './browser-guard.js';
+export * from './client.js';
+export * from './config.js';
+export * from './provider.js';
+export * from './types.js';

package/dist/provider.d.ts

@@ -0,0 +1,17 @@
+/**
+ * External authentication provider implementation using Supabase.
+ *
+ * Verifies Supabase user JWTs via the anon client's `auth.getUser(token)` —
+ * the anon key is PUBLIC, so verification requires NO secret.
+ *
+ * @see https://www.npmjs.com/package/@supabase/supabase-js
+ *
+ * @module
+ */
+import type { ExternalAuthProvider } from '@molecule/api-external-auth';
+/**
+ * External authentication provider backed by Supabase. Wire it at startup:
+ * `setProvider(provider)` from `@molecule/api-external-auth`.
+ */
+export declare const provider: ExternalAuthProvider;
+//# sourceMappingURL=provider.d.ts.map

package/dist/provider.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"provider.d.ts","sourceRoot":"","sources":["../src/provider.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH,OAAO,KAAK,EAAE,oBAAoB,EAAoB,MAAM,6BAA6B,CAAA;AAIzF;;;GAGG;AACH,eAAO,MAAM,QAAQ,EAAE,oBAiBtB,CAAA"}

package/dist/provider.js

@@ -0,0 +1,36 @@
+/**
+ * External authentication provider implementation using Supabase.
+ *
+ * Verifies Supabase user JWTs via the anon client's `auth.getUser(token)` —
+ * the anon key is PUBLIC, so verification requires NO secret.
+ *
+ * @see https://www.npmjs.com/package/@supabase/supabase-js
+ *
+ * @module
+ */
+import { getAnonClient } from './client.js';
+/**
+ * External authentication provider backed by Supabase. Wire it at startup:
+ * `setProvider(provider)` from `@molecule/api-external-auth`.
+ */
+export const provider = {
+    async verifyUserToken(token) {
+        if (!token)
+            return null;
+        const client = getAnonClient();
+        try {
+            const { data, error } = await client.auth.getUser(token);
+            if (error || !data.user)
+                return null;
+            return { userId: data.user.id, email: data.user.email ?? undefined };
+        }
+        catch (_error) {
+            // Intentionally ignored: supabase-js reports auth/transport failures via
+            // the returned `error` (handled above); a throw here is a defensive
+            // catch for unexpected library failures, and the contract is "a token
+            // that cannot be verified is unverified (null)" — callers map null to
+            // 401, they do not need a stack trace for a bad token.
+            return null;
+        }
+    },
+};

package/dist/state.d.ts

@@ -0,0 +1,37 @@
+/**
+ * INTERNAL shared state for the Supabase integration — deliberately NOT
+ * re-exported from the package barrel (`src/index.ts`), so none of this leaks
+ * into the public API. Holds the configured settings, the lazily created
+ * client singletons, and the env-fallback resolution.
+ */
+import type { SupabaseClient } from '@supabase/supabase-js';
+import type { SupabaseSettings } from './types.js';
+/**
+ * Mutable module state: explicit settings plus the cached client singletons.
+ */
+export interface SupabaseState {
+    /**
+     * Settings supplied via `configureSupabase()`. Take precedence over env.
+     */
+    settings: SupabaseSettings;
+    /**
+     * Cached anon-key client (lazy singleton).
+     */
+    anonClient: SupabaseClient | null;
+    /**
+     * Cached service-role client (lazy singleton).
+     */
+    serviceClient: SupabaseClient | null;
+}
+/**
+ * The single shared state instance.
+ */
+export declare const state: SupabaseState;
+/**
+ * Resolves the effective settings: explicit `configureSupabase()` values
+ * first, then environment variables. Called lazily at first client creation
+ * (and by `hasServiceRole()`), never at module load — so env vars set after
+ * import are picked up.
+ */
+export declare const resolveSettings: () => SupabaseSettings;
+//# sourceMappingURL=state.d.ts.map

package/dist/state.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"state.d.ts","sourceRoot":"","sources":["../src/state.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,uBAAuB,CAAA;AAE3D,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,YAAY,CAAA;AAElD;;GAEG;AACH,MAAM,WAAW,aAAa;IAC5B;;OAEG;IACH,QAAQ,EAAE,gBAAgB,CAAA;IAE1B;;OAEG;IACH,UAAU,EAAE,cAAc,GAAG,IAAI,CAAA;IAEjC;;OAEG;IACH,aAAa,EAAE,cAAc,GAAG,IAAI,CAAA;CACrC;AAED;;GAEG;AACH,eAAO,MAAM,KAAK,EAAE,aAInB,CAAA;AAED;;;;;GAKG;AACH,eAAO,MAAM,eAAe,QAAO,gBAWlC,CAAA"}

package/dist/state.js

@@ -0,0 +1,25 @@
+/**
+ * The single shared state instance.
+ */
+export const state = {
+    settings: {},
+    anonClient: null,
+    serviceClient: null,
+};
+/**
+ * Resolves the effective settings: explicit `configureSupabase()` values
+ * first, then environment variables. Called lazily at first client creation
+ * (and by `hasServiceRole()`), never at module load — so env vars set after
+ * import are picked up.
+ */
+export const resolveSettings = () => {
+    const env = process.env;
+    return {
+        url: state.settings.url ?? env.SUPABASE_URL ?? env.VITE_SUPABASE_URL,
+        anonKey: state.settings.anonKey ??
+            env.SUPABASE_ANON_KEY ??
+            env.VITE_SUPABASE_ANON_KEY ??
+            env.VITE_SUPABASE_PUBLISHABLE_KEY,
+        serviceRoleKey: state.settings.serviceRoleKey ?? env.SUPABASE_SERVICE_ROLE_KEY,
+    };
+};

package/dist/types.d.ts

@@ -0,0 +1,35 @@
+/**
+ * Type definitions for the Supabase external-auth bond.
+ *
+ * @module
+ */
+/**
+ * Connection settings for the Supabase integration.
+ *
+ * Every field is optional — anything not set explicitly via
+ * {@link configureSupabase} falls back to environment variables, read lazily
+ * at first client creation (never at module load):
+ *
+ * - `url`: `SUPABASE_URL` ?? `VITE_SUPABASE_URL`
+ * - `anonKey`: `SUPABASE_ANON_KEY` ?? `VITE_SUPABASE_ANON_KEY` ??
+ *   `VITE_SUPABASE_PUBLISHABLE_KEY`
+ * - `serviceRoleKey`: `SUPABASE_SERVICE_ROLE_KEY`
+ */
+export interface SupabaseSettings {
+    /**
+     * The Supabase project URL (e.g. `https://abcd1234.supabase.co`).
+     */
+    url?: string;
+    /**
+     * The PUBLIC anon (publishable) key. Safe to expose in browsers — it grants
+     * only what Row Level Security allows. Sufficient for verifying user JWTs.
+     */
+    anonKey?: string;
+    /**
+     * The SECRET service-role key. Bypasses Row Level Security — server-only,
+     * never exposed to clients. Not provisioned in molecule sandboxes by
+     * default; check {@link hasServiceRole} before relying on it.
+     */
+    serviceRoleKey?: string;
+}
+//# sourceMappingURL=types.d.ts.map

package/dist/types.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"types.d.ts","sourceRoot":"","sources":["../src/types.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH;;;;;;;;;;;GAWG;AACH,MAAM,WAAW,gBAAgB;IAC/B;;OAEG;IACH,GAAG,CAAC,EAAE,MAAM,CAAA;IAEZ;;;OAGG;IACH,OAAO,CAAC,EAAE,MAAM,CAAA;IAEhB;;;;OAIG;IACH,cAAc,CAAC,EAAE,MAAM,CAAA;CACxB"}

package/dist/types.js

@@ -0,0 +1,6 @@
+/**
+ * Type definitions for the Supabase external-auth bond.
+ *
+ * @module
+ */
+export {};

package/package.json

@@ -0,0 +1,52 @@
+{
+  "name": "@molecule/api-external-auth-supabase",
+  "version": "1.0.0",
+  "description": "External authentication provider using Supabase for molecule.dev — verifies Supabase user JWTs server-side with the public anon key",
+  "type": "module",
+  "main": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "scripts": {
+    "build": "tsc",
+    "test": "vitest run",
+    "test:watch": "vitest"
+  },
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    }
+  },
+  "files": [
+    "dist"
+  ],
+  "keywords": [
+    "molecule",
+    "external-auth",
+    "supabase",
+    "auth",
+    "provider"
+  ],
+  "license": "Apache-2.0",
+  "dependencies": {
+    "@supabase/supabase-js": "2.111.0"
+  },
+  "peerDependencies": {
+    "@molecule/api-external-auth": "^1.0.0"
+  },
+  "devDependencies": {
+    "@molecule/api-external-auth": "1.0.0",
+    "@types/node": "26.1.2",
+    "typescript": "6.0.3",
+    "vitest": "4.1.10"
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/molecule-dev/molecule.git",
+    "directory": "packages/api/bonds/external-auth/supabase"
+  },
+  "homepage": "https://github.com/molecule-dev/molecule/tree/main/packages/api/bonds/external-auth/supabase",
+  "bugs": "https://github.com/molecule-dev/molecule/issues",
+  "publishConfig": {
+    "access": "public"
+  }
+}