@softr/sdk 0.0.99-alpha.0 → 0.0.99-alpha.1

package/skills/softr-sdk/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: core
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 # Softr SDK core
@@ -22,8 +22,6 @@ metadata:
 >
 > **CRITICAL**: The app is already wired. `src/start.ts`, `src/router.tsx` and `src/routes/__root.tsx` register `softrAuthMiddleware` and resolve the session. Do not add a second registration of it. `softrMcpMiddleware` is the one thing an app adds to `src/start.ts` itself — load the `softr-sdk/mcp` sub-skill before doing so.
 >
-> **CRITICAL**: `email.send` lives on `@softr/sdk/server` and only runs inside a `createServerFn` handler. Use `defineEmailAction` from `@softr/sdk` to declare who may send it and the recipients it fixes. An email the app sends itself needs no workflow and no connected mail service. Load the `softr-sdk/email` sub-skill for the full pattern.
->
 > **CRITICAL**: `ai.generate` and `ai.stream` live on `@softr/sdk/server` and only run inside a `createServerFn` handler. Use `defineAiAction` from `@softr/sdk` to declare the action with the model it runs on, an id copied from the `ai_list_models` tool. Softr runs the model on its own keys; never ask the user for an API key for the app's own AI feature. Load the `softr-sdk/ai` sub-skill for the full pattern.
 >
 > **CRITICAL**: `workflow.trigger` lives on `@softr/sdk/server` and only runs inside a `createServerFn` handler. Use `defineWorkflow` from `@softr/sdk` to declare the action, then pass it to `workflow.trigger`. Load the `softr-sdk/workflows` sub-skill for the full pattern.
@@ -34,8 +32,8 @@ Each sub-skill stands alone for its task and repeats the boundary above, so most
 
 | Import | Runs | Holds |
 | --- | --- | --- |
-| `@softr/sdk` | Both | `defineQuery`, `defineMutation`, `defineEmailAction`, `defineAiAction`, `definePage`, `pageHead`, `defineVisibility`, `guardRoute`, `assertRouteAccess`, `isAuthorized`, `checkAccess`, `Audience`, `useCurrentUser`, `useUserTimezone`, `FormattedDate`, `FormattingScope`, `useFormatting`, `formatDate`, `formatDateTime`, `formatNumber`, `formatValue`, `formatField`, `fieldShape`, `registerSoftrFields`, `useOverrides`, `SoftrPwaHead`, `usePwaInstall`, `getSoftrContext`, `initialSoftrContext`, `softrAuthMiddleware`, the error predicates, and every type |
-| `@softr/sdk/server` | Server only | `ds`, `auth`, `email`, `EmailError`, `workflow`, `integration`, `ai` |
+| `@softr/sdk` | Both | `defineQuery`, `defineMutation`, `defineAiAction`, `definePage`, `pageHead`, `defineVisibility`, `guardRoute`, `assertRouteAccess`, `isAuthorized`, `checkAccess`, `Audience`, `useCurrentUser`, `useUserTimezone`, `FormattedDate`, `FormattingScope`, `useFormatting`, `formatDate`, `formatDateTime`, `formatNumber`, `formatValue`, `formatField`, `fieldShape`, `registerSoftrFields`, `useOverrides`, `SoftrPwaHead`, `usePwaInstall`, `usePushNotifications`, `getSoftrContext`, `initialSoftrContext`, `softrAuthMiddleware`, the error predicates, and every type |
+| `@softr/sdk/server` | Server only | `ds`, `auth`, `workflow`, `integration`, `ai` |
 | `@softr/sdk/client` | Browser only | `useFileUpload` |
 | `@softr/sdk/vite` | Build | `softr()`, already in `vite.config.ts` |
 
@@ -49,13 +47,13 @@ Each sub-skill stands alone for its task and repeats the boundary above, so most
 | Fetch records from a datasource | [record-queries/SKILL.md](./record-queries/SKILL.md) |
 | Chart, aggregate or count records | [charts-and-metrics/SKILL.md](./charts-and-metrics/SKILL.md) |
 | Create, update or delete a record | [record-mutations/SKILL.md](./record-mutations/SKILL.md) |
-| Send an email from the app: a form that emails the owner, a confirmation, staff emailing a client | [email/SKILL.md](./email/SKILL.md) |
 | Trigger a Softr workflow | [workflows/SKILL.md](./workflows/SKILL.md) |
 | Sign a visitor in, out, or up | [auth/SKILL.md](./auth/SKILL.md) |
 | Ask an AI model: a summary, an extraction from a document, a classification, a draft, a chat | [ai/SKILL.md](./ai/SKILL.md) |
-| Call a connected third-party API (Slack, Stripe, Gmail from the user's own mailbox, …), or an AI model on the user's own provider account | [integrations/SKILL.md](./integrations/SKILL.md) |
+| Call a connected third-party API (Slack, Stripe, Gmail, …), or an AI model on the user's own provider account | [integrations/SKILL.md](./integrations/SKILL.md) |
 | Open the app to AI assistants over MCP | [mcp/SKILL.md](./mcp/SKILL.md) |
 | Let visitors install the app on their home screen | [pwa/SKILL.md](./pwa/SKILL.md) |
+| Let visitors turn on push notifications | [push-notifications/SKILL.md](./push-notifications/SKILL.md) |
 | Show a date, a time or a number | [formatting/SKILL.md](./formatting/SKILL.md) |
 
 ## Quick Decision Tree
@@ -79,9 +77,6 @@ Drawing a chart, a stat tile, or any aggregated number?
 Submitting a form, editing a record, or deleting one?
   load softr-sdk/record-mutations
 
-Sending an email when a form is submitted or a button is pressed?
-  load softr-sdk/email — no workflow, no connected mail service
-
 Triggering a Softr workflow from a button or form?
   load softr-sdk/workflows
 
@@ -103,6 +98,9 @@ Opening the app to an AI assistant over MCP?
 Adding an install button, or making the app installable?
   load softr-sdk/pwa
 
+Letting visitors turn on push notifications, or "notify users when …"?
+  load softr-sdk/push-notifications
+
 Showing a date, a time or a number on a page?
   load softr-sdk/formatting
 

package/skills/softr-sdk/ai/SKILL.md

@@ -13,7 +13,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 **Boundary.** `ai` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler — importing it into a component fails the build. `defineAiAction` and every type come from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/auth/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 **Boundary.** `auth` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler — importing it into a component fails the build.

package/skills/softr-sdk/charts-and-metrics/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 **Boundary.** `ds` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler or a server-side route hook — importing it into a component fails the build. `defineQuery` and every type come from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/current-user/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 # The current user

package/skills/softr-sdk/file-uploads/SKILL.md

@@ -7,7 +7,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 **Boundary.** `upload` lives on `@softr/sdk/server` and runs inside server functions. `useFileUpload` and `FileItem` live on `@softr/sdk` and run in components. `FileAttachment` comes from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/formatting/SKILL.md

@@ -8,7 +8,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 # Dates, times and numbers

package/skills/softr-sdk/integrations/SKILL.md

@@ -7,7 +7,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 **Boundary.** `integration` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler — importing it into a component fails the build. `defineIntegration` and every type come from `@softr/sdk` and can be imported anywhere.
@@ -16,8 +16,6 @@ metadata:
 
 `integration.createFetcher` calls a third-party API through Softr's authenticated proxy. It adds the connected account's credentials automatically — you never set API keys or auth headers yourself. **Every call acts as that one account, whoever the visitor is**, so take what a call reaches, such as a customer or a channel, from the session or a record the server read, never from the arguments the browser sends.
 
-An email the app sends is the `email` sub-skill, with nothing to connect. Send through a connected Gmail or Outlook only when the user wants the email to come from their own mailbox.
-
 ## Setup
 
 ```ts

package/skills/softr-sdk/mcp/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 **Boundary.** `softrMcpMiddleware` lives on `@softr/sdk` and is registered once, in `src/start.ts`. The actions you hand it are the same `defineQuery` / `defineMutation` values the app's own pages use — declared wherever they already live, not duplicated for MCP.

package/skills/softr-sdk/push-notifications/SKILL.md

@@ -0,0 +1,140 @@
+---
+name: push-notifications
+description: >-
+  Let signed-in visitors turn on push notifications: usePushNotifications for
+  the prompt, its states and the Studio texts, the PushNotifications and
+  PushPrompt types, and how to check that push is on for the app. Notifications
+  are sent by Softr Workflows, never by app code; the service worker is already
+  served, never write one.
+metadata:
+  type: sub-skill
+  library: softr-sdk
+  library_version: 0.0.97
+---
+
+# Push notifications
+
+The builder turns push on in Studio, under Users → Notifications, for desktop, mobile or both, and writes the prompt's texts there. Notifications are sent by a Softr Workflow's "Send notification" action, which the builder sets up in Studio. What the app adds is one thing: a prompt that lets the signed-in visitor turn notifications on in this browser.
+
+> **CRITICAL**: Never write a service worker, a `public/sw.js`, or any `navigator.serviceWorker`, `PushManager` or `Notification` code of your own. The app already serves its service worker, and `usePushNotifications()` registers it, subscribes and unsubscribes.
+>
+> **CRITICAL**: Never send a push from app code. Sending is a Softr Workflow's "Send notification" action. When the builder asks for "notify X when Y", point them to that workflow; when Y is something the app does, the app triggers the workflow (load the Softr SDK `workflows` guidance). The app itself adds only the prompt.
+
+## Setup
+
+```ts
+import { usePushNotifications } from '@softr/sdk'
+import type { PushNotifications, PushPrompt } from '@softr/sdk'
+```
+
+```ts
+type PushPrompt = {
+  title: string | null              // what the builder wrote in Studio; any of these may be missing
+  message: string | null
+  enableButtonLabel: string | null
+}
+
+type PushNotifications =
+  | { status: 'unavailable' }       // loading, signed out, push off, this device type off, or no browser support
+  | { status: 'install-first'; prompt: PushPrompt }   // iPhone and iPad: push works only in the installed app
+  | {
+      status: 'ask'
+      prompt: PushPrompt
+      dismissed: boolean            // skipped recently, within the builder's skip days; hide the prompt
+      subscribe: () => Promise<void>  // call from a click
+      dismiss: () => void
+    }
+  | { status: 'subscribed'; unsubscribe: () => Promise<void> }
+  | { status: 'blocked' }           // blocked in the browser; only the visitor can undo it there
+```
+
+## Is push on for the app?
+
+Ask the running app for `/_softr/push.json`: `200` means push is on, `404` means it is off in Studio or the plan does not include it. Do not build a prompt against a `404`: push has to be turned on first. A change in Studio can take up to two minutes to reach the app.
+
+Push works only on the published app. Inside the Studio preview the hook always says `unavailable`, so the prompt never shows there. That is expected, not a bug to fix.
+
+## Core Patterns
+
+### The prompt
+
+Render it once, in `RootDocument` in `src/routes/__root.tsx`, so it shows on every page and the browser stays registered for the visitor. Use the prompt component the template ships when it has one. It already handles each status.
+
+Call `usePushNotifications()` in that one component only. Each call keeps state of its own: a second call, in a header or on a settings page, does not see a subscribe made through the first, so the prompt would stay on screen after the visitor said yes.
+
+`subscribe()` rejects when the browser or Softr refuses. Catch it and tell the visitor, so the button never fails in silence.
+
+```tsx
+function EnableNotifications() {
+  const push = usePushNotifications()
+  if (push.status !== 'ask' || push.dismissed) return null
+  return (
+    <div role="dialog">
+      <p>{push.prompt.title ?? 'Turn on notifications'}</p>
+      <p>{push.prompt.message ?? 'Get notified about updates.'}</p>
+      <button onClick={() => push.subscribe().catch(() => toast.error('Notifications could not be turned on.'))}>
+        {push.prompt.enableButtonLabel ?? 'Turn on'}
+      </button>
+      <button onClick={push.dismiss}>Not now</button>
+    </div>
+  )
+}
+```
+
+Fall back to your own wording only where the builder left a text empty. On `install-first`, point the visitor to installing the app (load the Softr SDK `pwa` guidance); do not ask for permission.
+
+### Signing out
+
+Nothing to add. The browser is unsubscribed when the visitor signs out, so the next person on the device gets nothing meant for them.
+
+## Common Mistakes
+
+### CRITICAL Asking for permission on page load
+
+Wrong:
+
+```tsx
+useEffect(() => { push.status === 'ask' && push.subscribe() }, [push.status])
+```
+
+Correct:
+
+```tsx
+<button onClick={() => push.subscribe().catch(() => toast.error('Notifications could not be turned on.'))}>
+  {push.prompt.enableButtonLabel ?? 'Turn on'}
+</button>
+```
+
+Browsers ignore or block a permission request that no click started, and a visitor who blocks it can only undo that in the browser's settings.
+
+Source: packages/sdk/src/push.ts
+
+### HIGH Showing the prompt whatever the status
+
+Wrong:
+
+```tsx
+const push = usePushNotifications()
+return <button onClick={() => push.subscribe()}>Turn on notifications</button>
+```
+
+Correct:
+
+```tsx
+const push = usePushNotifications()
+if (push.status !== 'ask' || push.dismissed) return null
+return (
+  <button onClick={() => push.subscribe().catch(() => toast.error('Notifications could not be turned on.'))}>
+    {push.prompt.enableButtonLabel ?? 'Turn on'}
+  </button>
+)
+```
+
+The hook says `unavailable` when push is off in Studio, for this device type, or for a signed-out visitor. A prompt that skips the check shows in all of those, and on iPhone it asks for something the browser cannot give.
+
+Source: packages/sdk/src/push.ts
+
+## References
+
+- [SKILL.md](../SKILL.md): the entrypoints and which one each export lives on
+- [pwa/SKILL.md](../pwa/SKILL.md): installing the app, which iPhone and iPad need before push

package/skills/softr-sdk/pwa/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 # Installing the app

package/skills/softr-sdk/record-mutations/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 **Boundary.** `ds` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler — importing it into a component fails the build. `defineMutation` and every type come from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/record-queries/SKILL.md

@@ -10,7 +10,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 **Boundary.** `ds` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler or a server-side route hook — importing it into a component fails the build. The same holds for any helper that calls `ds`: declare it inside the handler. A function at module level that calls `ds` keeps the server-only import in the browser bundle, and every page stops loading until it moves. `defineQuery` and every type come from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/region-visibility/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 **Boundary.** `Audience` and `defineVisibility` come from `@softr/sdk` and work anywhere.

package/skills/softr-sdk/routes-and-visibility/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 **Boundary.** `definePage`, `pageHead`, the access functions and the error predicates come from `@softr/sdk` and work anywhere.

package/skills/softr-sdk/workflows/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.99-alpha.0
+  library_version: 0.0.98
 ---
 
 **Boundary.** `workflow` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler — importing it into a component fails the build. `defineWorkflow` and every type come from `@softr/sdk` and can be imported anywhere.
@@ -18,8 +18,6 @@ metadata:
 
 `workflow.trigger` fires a Softr workflow and waits for it to finish. It resolves to `void`.
 
-An email the app sends itself, when a form is submitted or a button is pressed, needs no workflow: load the `email` sub-skill. Fire a workflow for what the workflow's own steps do, such as updating a CRM or posting to a connected service.
-
 ## Setup
 
 ```ts
@@ -33,15 +31,15 @@ import { workflow } from '@softr/sdk/server'
 Every trigger needs a workflow action: which workflow, which trigger step, who may run it, and any data that is always sent. The workflow must have a **Run custom workflow** trigger — no other trigger type can be fired from app code.
 
 ```ts
-const syncNewLead = defineWorkflow({
-  id: 'syncNewLead',
+const sendWelcomeEmail = defineWorkflow({
+  id: 'sendWelcomeEmail',
   workflowId: 'c9d8e7f6-a5b4-4c3d-8e2f-1a0b9c8d7e6f',
   triggerId: '926da496-749f-4006-999c-197d8a556122',
   permissions: { userGroupTypes: ['LOGGED_IN_USERS'] },
   body: {
     email: '{LOGGED_IN_USER:EMAIL}',  // resolved server-side from the signed-in user
     name: '{LOGGED_IN_USER:NAME}',
-    source: 'website',                // any hardcoded value — always sent, never overridden at runtime
+    plan: 'enterprise',               // any hardcoded value — always sent, never overridden at runtime
   },
 })
 ```
@@ -72,7 +70,7 @@ These placeholders are resolved server-side when the workflow runs:
 const runWorkflow = createServerFn({ method: 'POST' })
   .validator(z.object({ message: z.string() }))
   .handler(async ({ data }) => {
-    await workflow.trigger(syncNewLead, { message: data.message })
+    await workflow.trigger(sendWelcomeEmail, { message: data.message })
   })
 ```
 
@@ -84,7 +82,7 @@ const runWorkflow = createServerFn({ method: 'POST' })
 
 ```ts
 const run = createServerFn({ method: 'POST' }).handler(async () => {
-  await workflow.trigger(syncNewLead)
+  await workflow.trigger(sendWelcomeEmail)
 })
 ```
 
@@ -96,11 +94,11 @@ Omit the second argument when the action's `body` already carries everything the
 
 ```ts
 // Wrong: calling from a click handler
-<button onClick={() => workflow.trigger(syncNewLead)}>Run</button>
+<button onClick={() => workflow.trigger(sendWelcomeEmail)}>Run</button>
 
 // Correct: server function, called from the button
 const run = createServerFn({ method: 'POST' }).handler(() =>
-  workflow.trigger(syncNewLead),
+  workflow.trigger(sendWelcomeEmail),
 )
 // …
 const submit = useServerFn(run)

package/dist/core/email.d.ts

@@ -1,48 +0,0 @@
-import { EmailAction } from "../action.js";
-
-//#region src/core/email.d.ts
-declare const EMAIL_ERROR_CODES: readonly ["NOT_FOUND", "INVALID_INPUT", "PLAN_RESTRICTED", "CREDITS_EXHAUSTED", "RATE_LIMITED", "DAILY_LIMIT_REACHED", "SENDER_UNAVAILABLE", "PROVIDER_REJECTED", "UNAVAILABLE", "TIMEOUT"];
-type EmailErrorCode = (typeof EMAIL_ERROR_CODES)[number];
-interface EmailSendInit {
-  /** Ignored when the action declares its own. */
-  to?: ReadonlyArray<string>;
-  /** Ignored when the action declares its own `cc` or `to`. */
-  cc?: ReadonlyArray<string>;
-  /** Ignored when the action declares its own `bcc` or `to`. */
-  bcc?: ReadonlyArray<string>;
-  /** Ignored when the action declares its own. */
-  replyTo?: string;
-  subject: string;
-  /** Plain text or HTML. */
-  body: string;
-}
-interface EmailSent {
-  /** Null when the mail provider did not report one; the email was still sent. */
-  messageId: string | null;
-}
-/**
- * Thrown when Softr did not send the email. `code` says why:
- *
- * - `NOT_FOUND`: no such action, or the caller is not in its audience.
- * - `INVALID_INPUT`: the call's inputs were refused; the message says which.
- * - `PLAN_RESTRICTED`: the workspace's plan does not include sending this email.
- * - `CREDITS_EXHAUSTED`: the workspace has no workflow credits left.
- * - `RATE_LIMITED`: the app sent too many emails lately; try again later.
- * - `DAILY_LIMIT_REACHED`: Softr's own address sent the workspace's emails for today.
- * - `SENDER_UNAVAILABLE`: the chosen sender is missing or not confirmed, or the action leaves `to` open and would send from Softr's address.
- * - `PROVIDER_REJECTED`: the mail provider refused the email.
- * - `UNAVAILABLE`: Softr could not send it right now, or could not be reached.
- * - `TIMEOUT`: no answer in time. It may still have been sent.
- */
-declare class EmailError extends Error {
-  readonly status: number;
-  readonly code: EmailErrorCode;
-  constructor(status: number, code: EmailErrorCode, message: string);
-}
-/** Sends one email through the action. Never retries by itself. */
-declare function sendEmail(action: EmailAction, init: EmailSendInit): Promise<EmailSent>;
-declare const email: {
-  send: typeof sendEmail;
-};
-//#endregion
-export { EmailError, EmailErrorCode, EmailSendInit, EmailSent, email };

package/dist/core/email.js

@@ -1,100 +0,0 @@
-import { assert } from "../assertions.js";
-import { softrApiUrl } from "../softr-api.js";
-import { fetch } from "../fetch.js";
-import { sessionConfig } from "../auth/config.js";
-import { readSessionToken } from "../auth/session.js";
-
-//#region src/core/email.ts
-/** Longer than Softr waits for the send itself, so its own timeout answers first. */
-const TIMEOUT_MS = 12e4;
-const EMAIL_ERROR_CODES = [
-	"NOT_FOUND",
-	"INVALID_INPUT",
-	"PLAN_RESTRICTED",
-	"CREDITS_EXHAUSTED",
-	"RATE_LIMITED",
-	"DAILY_LIMIT_REACHED",
-	"SENDER_UNAVAILABLE",
-	"PROVIDER_REJECTED",
-	"UNAVAILABLE",
-	"TIMEOUT"
-];
-/**
-* Thrown when Softr did not send the email. `code` says why:
-*
-* - `NOT_FOUND`: no such action, or the caller is not in its audience.
-* - `INVALID_INPUT`: the call's inputs were refused; the message says which.
-* - `PLAN_RESTRICTED`: the workspace's plan does not include sending this email.
-* - `CREDITS_EXHAUSTED`: the workspace has no workflow credits left.
-* - `RATE_LIMITED`: the app sent too many emails lately; try again later.
-* - `DAILY_LIMIT_REACHED`: Softr's own address sent the workspace's emails for today.
-* - `SENDER_UNAVAILABLE`: the chosen sender is missing or not confirmed, or the action leaves `to` open and would send from Softr's address.
-* - `PROVIDER_REJECTED`: the mail provider refused the email.
-* - `UNAVAILABLE`: Softr could not send it right now, or could not be reached.
-* - `TIMEOUT`: no answer in time. It may still have been sent.
-*/
-var EmailError = class extends Error {
-	status;
-	code;
-	constructor(status, code, message) {
-		super(message);
-		this.name = "EmailError";
-		this.status = status;
-		this.code = code;
-	}
-};
-/** Sends one email through the action. Never retries by itself. */
-async function sendEmail(action, init) {
-	const { to, cc, bcc, replyTo, subject, body } = init;
-	const sessionToken = readSessionToken();
-	let res;
-	try {
-		res = await fetch(`${softrApiUrl("SOFTR_PLATFORM_API_URL")}/v1/vibe/applications/${sessionConfig().applicationId}/actions/${action.id}/email`, {
-			method: "POST",
-			headers: {
-				...sessionToken ? { Authorization: `Bearer ${sessionToken}` } : {},
-				"Content-Type": "application/json"
-			},
-			body: JSON.stringify({ input: {
-				to,
-				cc,
-				bcc,
-				replyTo,
-				subject,
-				body
-			} }),
-			signal: AbortSignal.timeout(TIMEOUT_MS)
-		});
-	} catch (error) {
-		if (error instanceof DOMException && error.name === "TimeoutError") throw new EmailError(504, "TIMEOUT", `Email "${action.id}" got no answer in time. It may still have been sent.`);
-		throw new EmailError(502, "UNAVAILABLE", `Email "${action.id}" could not reach Softr: ${error instanceof Error ? error.message : String(error)}`);
-	}
-	if (res.ok) {
-		const sent = await res.json();
-		assert(typeof sent === "object" && sent !== null && "messageId" in sent && (typeof sent.messageId === "string" || sent.messageId === null), "the send answered without a messageId");
-		return { messageId: sent.messageId };
-	}
-	const { code, message } = await readFailure(res, `Email "${action.id}" failed with HTTP ${res.status}`);
-	throw new EmailError(res.status, code, message);
-}
-/** The code and message of a send Softr refused, read from its answer; `fallbackMessage` when it sent none. */
-async function readFailure(res, fallbackMessage) {
-	const failure = await res.json().catch(() => null);
-	const known = typeof failure === "object" && failure !== null ? failure : {};
-	return {
-		code: ("code" in known ? EMAIL_ERROR_CODES.find((errorCode) => errorCode === known.code) : void 0) ?? codeOfStatus(res.status),
-		message: "message" in known && typeof known.message === "string" && known.message !== "" ? known.message : fallbackMessage
-	};
-}
-function codeOfStatus(status) {
-	switch (status) {
-		case 400: return "INVALID_INPUT";
-		case 404: return "NOT_FOUND";
-		case 429: return "RATE_LIMITED";
-		default: return "UNAVAILABLE";
-	}
-}
-const email = { send: sendEmail };
-
-//#endregion
-export { EmailError, email };