@zitadel/astro-auth 1.2.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 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
+      (an example is provided in the Appendix below).
+
+      "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. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to 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. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by 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
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   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, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   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/README.md

@@ -0,0 +1,254 @@
+# Astro Auth.js
+
+An [Astro](https://astro.build/) integration for [Auth.js](https://authjs.dev/)
+that provides seamless authentication with multiple providers, session
+management, and UI primitives that feel natural in Astro.
+
+This integration brings the power and flexibility of Auth.js to Astro
+applications with full TypeScript support, SSR-friendly HTTP handling,
+and Astro-native patterns including integrations, endpoints, and components.
+
+### Why?
+
+Modern web applications require robust, secure, and flexible authentication
+systems. While Auth.js provides excellent authentication capabilities,
+integrating it with Astro applications requires careful consideration of
+framework patterns, server-side rendering, and TypeScript integration.
+
+However, a direct integration isn't always straightforward. Different types
+of applications or deployment scenarios might warrant different approaches:
+
+- **Framework Integration:** Auth.js operates at the HTTP level, while Astro
+  uses integrations, endpoints, and components. A proper integration should bridge this
+  gap by providing Astro-native primitives for authentication and authorization
+  while maintaining the full Auth.js ecosystem compatibility.
+- **HTTP Request Handling:** Astro’s server output and adapters (Node, Vercel, etc.)
+  require clean request handling and route injection. Teams need a unified approach that
+  maintains performance while providing seamless Auth.js integration.
+- **Session and Request Lifecycle:** Proper session handling in Astro requires
+  SSR-friendly utilities and components that work across server-rendered pages
+  and client interactions.
+- **Route Protection & UI:** Many applications need fine-grained authorization
+  beyond simple authentication. This calls for cohesive building blocks: server utilities,
+  client helpers, and drop-in UI components.
+
+This integration, `@zitadel/astro-auth`, aims to provide the flexibility to
+handle such scenarios. It allows you to leverage the full Auth.js ecosystem
+while maintaining Astro best practices, ultimately leading to a more
+effective and less burdensome authentication implementation.
+
+## Installation
+
+Install using NPM by using the following command:
+
+```sh
+npm install @zitadel/astro-auth @auth/core
+```
+
+## Usage
+
+To use this integration, add the `@zitadel/astro-auth` integration to your Astro application.
+The integration provides authentication infrastructure with configurable
+endpoints, SSR utilities, and components.
+
+You'll need to configure it with your Auth.js providers and options. The
+integration will then be available throughout your application via Astro’s
+integration system.
+
+First, add the integration to your Astro config:
+
+```ts
+// astro.config.mjs
+import { defineConfig } from 'astro/config';
+import authAstro from '@zitadel/astro-auth';
+
+export default defineConfig({
+  output: 'server',
+  integrations: [
+    authAstro({
+      // Optional:
+      // prefix: '/api/auth',
+      // configFile: './auth.config.ts'
+    }),
+  ],
+});
+```
+
+```ts
+// auth.config.ts
+import { defineConfig } from '@zitadel/astro-auth';
+import Google from '@auth/core/providers/google';
+
+export default defineConfig({
+  providers: [
+    Google({
+      clientId: process.env.GOOGLE_CLIENT_ID,
+      clientSecret: process.env.GOOGLE_CLIENT_SECRET,
+    }),
+  ],
+  secret: process.env.AUTH_SECRET,
+  trustHost: true,
+});
+```
+
+#### Using the Authentication System
+
+The integration provides several functions and hooks for handling
+authentication:
+
+**Functions and Hooks:**
+
+- `getSession(request, config?)`: Retrieves the current Auth.js session (SSR)
+- `<Auth>`: Render-prop component that provides the current session to children
+- `<SignIn provider="...">`: Drop-in button component for starting sign-in
+- `<SignOut>`: Drop-in button component for signing out
+- `signIn(provider, options?, authParams?)`: Client helper for programmatic sign-in
+- `signOut(options?)`: Client helper for programmatic sign-out
+
+**Basic Usage:**
+
+```astro
+---
+// src/pages/index.astro
+import { getSession } from '@zitadel/astro-auth/server';
+import type { Session } from '@auth/core/types';
+
+const session = await getSession(Astro.request);
+---
+
+<html>
+  <body>
+    {session ? (
+      <>
+        <p>Welcome {session.user?.name}</p>
+        <a href="/api/auth/signout">Sign out</a>
+      </>
+    ) : (
+      <a href="/api/auth/signin">Sign in</a>
+    )}
+  </body>
+</html>
+```
+
+Prefer using components? Use the built-ins for a richer experience:
+
+```astro
+---
+// src/pages/index.astro
+import type { Session } from '@auth/core/types';
+import { Auth, SignIn, SignOut } from '@zitadel/astro-auth/components';
+---
+
+<Auth>
+  {(session: Session | null) => (
+    <>
+      {session ? (
+        <>
+          <SignOut>Sign out</SignOut>
+          <p>Logged in as {session.user?.name}</p>
+        </>
+      ) : (
+        <SignIn provider="github">Sign in with GitHub</SignIn>
+      )}
+    </>
+  )}
+</Auth>
+```
+
+Prefer client helpers? Use inline script tags:
+
+```html
+---
+---
+
+<html>
+  <body>
+    <button id="login">Login</button>
+    <button id="logout">Logout</button>
+
+    <script>
+      const { signIn, signOut } = await import("@zitadel/astro-auth/client");
+      document.querySelector("#login").onclick = () => signIn("github");
+      document.querySelector("#logout").onclick = () => signOut();
+    </script>
+  </body>
+</html>
+```
+
+##### Example: Advanced Configuration with Multiple Providers
+
+This example shows how to use the integration with multiple Auth.js
+providers and custom session configuration:
+
+```ts
+// auth.config.ts
+import { defineConfig } from '@zitadel/astro-auth';
+import Google from '@auth/core/providers/google';
+import GitHub from '@auth/core/providers/github';
+
+export default defineConfig({
+  providers: [
+    Google({
+      clientId: process.env.GOOGLE_CLIENT_ID,
+      clientSecret: process.env.GOOGLE_CLIENT_SECRET,
+    }),
+    GitHub({
+      clientId: process.env.GITHUB_CLIENT_ID,
+      clientSecret: process.env.GITHUB_CLIENT_SECRET,
+    }),
+  ],
+  secret: process.env.AUTH_SECRET,
+  trustHost: true,
+  session: {
+    strategy: 'jwt',
+    maxAge: 30 * 24 * 60 * 60, // 30 days
+  },
+  callbacks: {
+    async jwt({ token, user }) {
+      if (user) (token as any).roles = (user as any).roles;
+      return token;
+    },
+    async session({ session, token }) {
+      (session.user as any).roles = (token as any).roles as
+        | string[]
+        | undefined;
+      return session;
+    },
+  },
+});
+```
+
+## Known Issues
+
+- **SSR & Adapter Required:** The integration requires Astro’s server output
+  with an adapter (e.g., `@astrojs/node`, Vercel, etc.). Ensure `output: 'server'`
+  is set and an adapter is configured in `astro.config.mjs`.
+- **Environment Configuration:** The integration relies on `AUTH_SECRET` and,
+  in many hosting scenarios, `AUTH_TRUST_HOST`. Ensure these are correctly set
+  in your environment for production.
+- **Callback URLs:** OAuth providers must be configured with the correct
+  callback URL: `[origin]/api/auth/callback/[provider]` (or your custom `prefix`).
+- **Type Augmentation:** If you attach additional properties (e.g., roles) to
+  the Auth.js user object, extend your app’s types accordingly so consumers of
+  `session.user` remain type-safe.
+- **Redirect Semantics:** OAuth providers expect real browser navigations during
+  sign-in. The client helpers handle this for you—avoid manual `fetch()` calls
+  to provider endpoints unless you know you need credential/email flows.
+
+## Useful links
+
+- **[Auth.js](https://authjs.dev/):** The authentication library that this
+  integration is built upon.
+- **[Astro](https://astro.build/):** The framework this integration targets.
+- **[Auth.js Providers](https://authjs.dev/getting-started/providers):**
+  Complete list of supported authentication providers.
+
+## Contributing
+
+If you have suggestions for how this integration could be improved, or
+want to report a bug, open an issue - we'd love all and any
+contributions.
+
+## License
+
+Apache-2.0

package/dist/api/[...auth].js

@@ -0,0 +1,41 @@
+// src/server.ts
+import { Auth, createActionURL, setEnvDefaults } from "@auth/core";
+import authConfig from "auth:config";
+function AstroAuthHandler(prefix, options = authConfig) {
+  const normalizedPrefix = prefix.endsWith("/") ? prefix.slice(0, -1) : prefix;
+  return async ({ request }) => {
+    const url = new URL(request.url);
+    if (!url.pathname.startsWith(normalizedPrefix + "/")) {
+      return;
+    }
+    return await Auth(request, options);
+  };
+}
+function AstroAuth(options = authConfig) {
+  const config = options ?? authConfig;
+  if (!config) {
+    throw new Error(
+      "Auth configuration not found. Please ensure auth.config is properly configured."
+    );
+  }
+  const { prefix = "/api/auth", ...authOptions } = config;
+  const handler = AstroAuthHandler(prefix, authOptions);
+  return {
+    async GET(context) {
+      return await handler(context);
+    },
+    async POST(context) {
+      return await handler(context);
+    }
+  };
+}
+
+// src/api/[...auth].ts
+var prerender = false;
+var { GET, POST } = AstroAuth();
+export {
+  GET,
+  POST,
+  prerender
+};
+//# sourceMappingURL=[...auth].js.map

package/dist/api/[...auth].js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/server.ts","../../src/api/%5B...auth%5D.ts"],"sourcesContent":["/**\n * > **caution**\n * > `astro-auth` is currently experimental. Be aware of breaking changes between versions.\n *\n *\n * Astro Auth is the unofficial Astro integration for Auth.js.\n * It provides a simple way to add authentication to your Astro site in a few lines of code.\n *\n * ## Installation\n *\n * `astro-auth` requires building your site in `server` mode with a platform adaper like `@astrojs/node`.\n * ```js\n * // astro.config.mjs\n * export default defineConfig({\n *   output: \"server\",\n *   adapter: node({\n *     mode: 'standalone'\n *   })\n * });\n * ```\n *\n * ```bash npm2yarn2pnpm\n * npm install @auth/core @zitadel/astro-auth\n * ```\n */\nimport { Auth, createActionURL, setEnvDefaults } from '@auth/core';\nimport type { APIContext } from 'astro';\nimport authConfig from 'auth:config';\nimport type { AstroAuthConfig } from './types.js';\nimport type { Session } from '@auth/core/types';\n\nfunction AstroAuthHandler(prefix: string, options = authConfig) {\n  const normalizedPrefix = prefix.endsWith('/') ? prefix.slice(0, -1) : prefix;\n  return async ({ request }: APIContext) => {\n    const url = new URL(request.url);\n    // Only handle requests that match our prefix path\n    // Non-matching paths return undefined because this handler is mounted as [...auth]\n    if (!url.pathname.startsWith(normalizedPrefix + '/')) {\n      return;\n    }\n\n    return await Auth(request, options);\n  };\n}\n\n/**\n * Creates a set of Astro endpoints for authentication.\n *\n * @param options - The configuration for authentication providers and other options.\n * @returns An object with `GET` and `POST` methods that can be exported in an Astro endpoint.\n * @throws {Error} When auth configuration is not found or not properly configured.\n *\n * @example\n * ```ts\n * export const { GET, POST } = AstroAuth({\n *   providers: [\n *     GitHub({\n *       clientId: process.env.GITHUB_ID!,\n *       clientSecret: process.env.GITHUB_SECRET!,\n *     }),\n *   ],\n *   debug: false,\n * })\n * ```\n */\nexport function AstroAuth(options = authConfig) {\n  const config = options ?? authConfig;\n  if (!config) {\n    throw new Error(\n      'Auth configuration not found. Please ensure auth.config is properly configured.',\n    );\n  }\n  const { prefix = '/api/auth', ...authOptions } = config;\n\n  const handler = AstroAuthHandler(prefix, authOptions);\n  return {\n    async GET(context: APIContext) {\n      return await handler(context);\n    },\n    async POST(context: APIContext) {\n      return await handler(context);\n    },\n  };\n}\n\n/**\n * Retrieves the current session for a Request.\n *\n * This function extracts session information from the request cookies and\n * validates it against the Auth.js configuration. It returns the session\n * object if valid or null if no valid session exists.\n *\n * @param req - The Request object\n * @param config - The authentication configuration\n * @returns Promise resolving to session data or null\n * @throws {Error} When session validation fails or Auth.js returns an error\n *\n * @example\n * ```ts\n * const session = await getSession(request, authConfig)\n * if (!session) throw new Error (\"Not authenticated\")\n * ```\n */\nexport async function getSession(\n  req: Request,\n  config: AstroAuthConfig,\n): Promise<Session | null> {\n  setEnvDefaults(process.env, config);\n  const url = createActionURL(\n    'session',\n    new URL(req.url).protocol.replace(':', ''),\n    new Headers(req.headers),\n    process.env,\n    config,\n  );\n  const headers = new Headers(req.headers);\n  const response = await Auth(\n    new Request(url, {\n      headers,\n    }),\n    config,\n  );\n  const status = response.status ?? 200;\n  const data = await response.json();\n  if (!data || !Object.keys(data).length) {\n    return null;\n  } else {\n    const astroGlobal = globalThis as unknown as {\n      Astro?: { response?: { headers?: Headers } };\n    };\n    const target =\n      astroGlobal.Astro && astroGlobal.Astro.response\n        ? astroGlobal.Astro.response.headers\n        : undefined;\n    if (target) {\n      const h = response.headers as unknown as {\n        getSetCookie?: () => string[];\n      };\n      if (h && typeof h.getSetCookie === 'function') {\n        const cookies = h.getSetCookie();\n        if (Array.isArray(cookies)) {\n          for (const c of cookies) {\n            target.append('Set-Cookie', c);\n          }\n        }\n      } else {\n        const single = response.headers.get('set-cookie');\n        if (single) {\n          target.append('Set-Cookie', single);\n        }\n      }\n    }\n    if (status === 200) {\n      return data as Session;\n    } else {\n      throw new Error(\n        `[astro-auth] getSession failed: ${status} ${JSON.stringify(data)}`,\n      );\n    }\n  }\n}\n","/* istanbul ignore file */\nimport { AstroAuth } from '../server.js';\n\n// noinspection JSUnusedGlobalSymbols\nexport const prerender = false;\n\nexport const { GET, POST } = AstroAuth();\n"],"mappings":";AAyBA,SAAS,MAAM,iBAAiB,sBAAsB;AAEtD,OAAO,gBAAgB;AAIvB,SAAS,iBAAiB,QAAgB,UAAU,YAAY;AAC9D,QAAM,mBAAmB,OAAO,SAAS,GAAG,IAAI,OAAO,MAAM,GAAG,EAAE,IAAI;AACtE,SAAO,OAAO,EAAE,QAAQ,MAAkB;AACxC,UAAM,MAAM,IAAI,IAAI,QAAQ,GAAG;AAG/B,QAAI,CAAC,IAAI,SAAS,WAAW,mBAAmB,GAAG,GAAG;AACpD;AAAA,IACF;AAEA,WAAO,MAAM,KAAK,SAAS,OAAO;AAAA,EACpC;AACF;AAsBO,SAAS,UAAU,UAAU,YAAY;AAC9C,QAAM,SAAS,WAAW;AAC1B,MAAI,CAAC,QAAQ;AACX,UAAM,IAAI;AAAA,MACR;AAAA,IACF;AAAA,EACF;AACA,QAAM,EAAE,SAAS,aAAa,GAAG,YAAY,IAAI;AAEjD,QAAM,UAAU,iBAAiB,QAAQ,WAAW;AACpD,SAAO;AAAA,IACL,MAAM,IAAI,SAAqB;AAC7B,aAAO,MAAM,QAAQ,OAAO;AAAA,IAC9B;AAAA,IACA,MAAM,KAAK,SAAqB;AAC9B,aAAO,MAAM,QAAQ,OAAO;AAAA,IAC9B;AAAA,EACF;AACF;;;AC/EO,IAAM,YAAY;AAElB,IAAM,EAAE,KAAK,KAAK,IAAI,UAAU;","names":[]}

package/dist/client.d.ts

@@ -0,0 +1,91 @@
+import { L as LiteralUnion, A as AstroSignInOptions, S as SignInAuthorizationParams, a as AstroSignOutParams } from './types-Bvas30QH.js';
+import '@auth/core/types';
+
+/**
+ * Initiates a sign-in flow with the specified authentication provider.
+ *
+ * This function handles authentication for different provider types using
+ * the appropriate mechanism for each. OAuth providers require browser form
+ * submission to properly handle redirect chains, while credential-based
+ * providers can use fetch for JSON responses.
+ *
+ * @typeParam P - The provider identifier type for type-safe provider names
+ * @param providerId - The authentication provider identifier (e.g., 'github',
+ *                     'google', 'credentials')
+ * @param options - Configuration options for the sign-in flow
+ * @param authorizationParams - Additional OAuth authorization parameters to
+ *                              pass to the provider
+ * @returns Promise that resolves to Response for credential providers when
+ *          redirect is false and an error occurs, otherwise void
+ *
+ * @remarks
+ * **Why Different Mechanisms for Different Providers:**
+ *
+ * OAuth Providers (github, google, etc.):
+ * - Auth.js responds with a 302 redirect to the OAuth provider's login page
+ * - Using `fetch()` causes the browser to follow redirects in JS context
+ * - The OAuth provider expects a real browser navigation, not XHR
+ * - Result: fetch completes but no visible navigation occurs
+ * - Solution: Use real form submission to let browser handle redirects
+ *
+ * Credential/Email Providers:
+ * - Auth.js responds with JSON containing success/error information
+ * - These providers need to return Response objects for error handling
+ * - Using `fetch()` allows access to response data and conditional redirects
+ * - Result: Can detect errors and optionally suppress redirect
+ * - Solution: Use fetch with JSON response handling
+ *
+ * **Security Considerations:**
+ * - All requests include CSRF token protection
+ * - Callback URLs are normalized to prevent open redirect attacks
+ * - Only same-origin URLs are allowed for redirects
+ *
+ * **Browser Compatibility:**
+ * - Form submission approach works in all browsers including those that
+ *   restrict fetch() behavior for cross-origin redirects
+ * - Hash-based navigation triggers explicit reload for proper routing
+ *
+ * @example OAuth Provider Sign-In
+ * ```ts
+ * // Triggers form submission and browser navigation to GitHub
+ * await signIn('github')
+ * ```
+ *
+ * @example OAuth with Custom Callback
+ * ```ts
+ * await signIn('google', {
+ *   callbackUrl: '/dashboard'
+ * })
+ * ```
+ *
+ * @example OAuth with Authorization Parameters
+ * ```ts
+ * await signIn('google', undefined, {
+ *   prompt: 'consent',
+ *   login_hint: 'user@example.com'
+ * })
+ * ```
+ *
+ * @example Credential Provider with Error Handling
+ * ```ts
+ * const response = await signIn('credentials', {
+ *   redirect: false
+ * }, {
+ *   username: 'user',
+ *   password: 'pass'
+ * })
+ *
+ * if (response) {
+ *   const data = await response.json()
+ *   if (data.error) {
+ *     console.error('Sign in failed:', data.error)
+ *   }
+ * }
+ * ```
+ *
+ * @public
+ */
+declare function signIn<P extends string | undefined = undefined>(providerId?: LiteralUnion<P extends string ? P | string : string>, options?: AstroSignInOptions, authorizationParams?: SignInAuthorizationParams): Promise<Response | void>;
+declare function signOut(options?: AstroSignOutParams): Promise<void>;
+
+export { signIn, signOut };