@wtfalch/email 0.1.0 → 0.1.1

package/dist/postmaster/apply.d.ts

@@ -1,4 +1,3 @@
-import 'server-only';
 import type { Instance } from './instance.js';
 export interface Applied {
     /** For the audit row's `targetType`. */

package/dist/postmaster/apply.js

@@ -1,4 +1,3 @@
-import 'server-only';
 import { MailWriteRefused, newAccount, withAlias, withoutAlias, withoutAppPassword, } from './writes.js';
 /**
  * The four writes `/email` makes, each as one round trip against the mail

package/dist/postmaster/browser-refusal.js

@@ -0,0 +1,21 @@
+"use strict";
+/**
+ * What a browser bundle gets instead of the administration client.
+ *
+ * This entry reaches a mail server with an administrator credential that, on
+ * Stalwart 0.16, cannot be scoped and is as powerful as the whole account. It
+ * must never end up in something a browser downloads.
+ *
+ * **Why the `browser` condition and not `server-only`.** `server-only` throws
+ * in any environment without React's `react-server` condition, which includes
+ * plain Node — and this entry exists partly so a provisioning CLI can use it,
+ * so that guard broke the legitimate caller while blocking the illegitimate
+ * one. The `browser` condition in the exports map is the tool that tells them
+ * apart: a bundler targeting a browser resolves here, while Node and a React
+ * Server Components build resolve the real module.
+ *
+ * It throws at import rather than exporting stubs, so the failure is at build
+ * or first load with a sentence saying what to do, not a runtime mystery
+ * about a client that never answers.
+ */
+throw new Error('@wtfalch/email/postmaster is server-side only: it holds an administrator credential for a mail server and must not be bundled for a browser. Call it from a Server Component, a Server Action, a route handler or a Node script, and render the results with @wtfalch/email/postmaster/react.');

package/dist/postmaster/index.d.ts

@@ -1,12 +1,3 @@
-/**
- * `server-only`, and it is load-bearing rather than decorative. This module
- * reaches a mail server with an administrator credential that, on Stalwart
- * 0.16, cannot be scoped and is as powerful as the whole account. Nothing
- * about living in its own entry stops a client component importing it —
- * bundlers follow imports, not entry names — so the guard that actually
- * fails such a build is this line.
- */
-import 'server-only';
 /**
  * Administer a Stalwart mail server over its JMAP management API: the
  * domain, the mailboxes, their aliases, their app passwords and their

package/dist/postmaster/index.js

@@ -1,12 +1,3 @@
-/**
- * `server-only`, and it is load-bearing rather than decorative. This module
- * reaches a mail server with an administrator credential that, on Stalwart
- * 0.16, cannot be scoped and is as powerful as the whole account. Nothing
- * about living in its own entry stops a client component importing it —
- * bundlers follow imports, not entry names — so the guard that actually
- * fails such a build is this line.
- */
-import 'server-only';
 /**
  * Administer a Stalwart mail server over its JMAP management API: the
  * domain, the mailboxes, their aliases, their app passwords and their

package/dist/postmaster/instance.d.ts

@@ -1,4 +1,3 @@
-import 'server-only';
 import { StalwartClient } from './client.js';
 /**
  * A mail instance and the credential this program acts on it with.

package/dist/postmaster/instance.js

@@ -1,4 +1,3 @@
-import 'server-only';
 import { StalwartClient, authFor } from './client.js';
 /**
  * An instance from a URL and one opaque secret, with the scheme chosen from

package/dist/postmaster/load.d.ts

@@ -1,4 +1,3 @@
-import 'server-only';
 import type { Instance } from './instance.js';
 import { type Overview, type Person } from './overview.js';
 /**

package/dist/postmaster/load.js

@@ -1,4 +1,3 @@
-import 'server-only';
 import { resolveMx } from 'node:dns/promises';
 import { overview, } from './overview.js';
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wtfalch/email",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "The wtfalch estate: reading a mailbox over JMAP, and administering the Stalwart server it lives on. Two entries with no code in common.",
   "license": "MIT",
   "type": "module",
@@ -23,6 +23,7 @@
     },
     "./mailbox/mail.css": "./dist/mailbox/mail.css",
     "./postmaster": {
+      "browser": "./dist/postmaster/browser-refusal.js",
       "types": "./dist/postmaster/index.d.ts",
       "default": "./dist/postmaster/index.js"
     },
@@ -64,10 +65,6 @@
     "typescript": "^5.9.0",
     "vitest": "^4.1.6"
   },
-  "dependencies": {
-    "jmap-jam": "^0.13.6",
-    "server-only": "^0.0.1"
-  },
   "sideEffects": false,
   "publishConfig": {
     "access": "public"
@@ -82,6 +79,9 @@
     "stalwart",
     "rfc8621"
   ],
+  "dependencies": {
+    "jmap-jam": "^0.13.6"
+  },
   "scripts": {
     "build": "rm -rf dist && tsc -p tsconfig.build.json && cp src/mailbox/react/mail.css dist/mailbox/mail.css",
     "typecheck": "tsc --noEmit",