@pylonsync/functions 0.3.273 → 0.3.275

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pylonsync/functions",
-  "version": "0.3.273",
+  "version": "0.3.275",
   "description": "TypeScript function runtime for pylon — defines server-side queries, mutations, and actions.",
   "type": "module",
   "main": "src/index.ts",

package/src/ssr-client-bundler.ts

@@ -910,12 +910,18 @@ async function _doBuildInner(
     // rather than an inline string in CLIENT_RUNTIME_SOURCE that nothing
     // could render. Bun pulls it into the shared chunk via the runtime's
     // static `import { createPylonBoundary } from "./client-boundary"`.
+    //
+    // Resolve THIS module's directory from the standard `import.meta.url`
+    // (via node:url) rather than Bun's `import.meta.dir` — the latter is a
+    // Bun-only extension that `tsc` doesn't know about, so any app that
+    // imports `@pylonsync/functions` and runs `tsc` would otherwise fail
+    // type-checking on this file. `import.meta.url` works in Bun and Node.
+    const urlMod: any = await import("node:url");
+    const fileURLToPath = urlMod.fileURLToPath ?? urlMod.default?.fileURLToPath;
+    const here = path.dirname(fileURLToPath(import.meta.url));
     fs.writeFileSync(
       path.join(stageDir, "client-boundary.ts"),
-      fs.readFileSync(
-        path.join(import.meta.dir, "ssr-client-boundary.ts"),
-        "utf8",
-      ),
+      fs.readFileSync(path.join(here, "ssr-client-boundary.ts"), "utf8"),
       "utf8",
     );
 

package/src/types.ts

@@ -293,6 +293,14 @@ export interface Scheduler {
  * webhook). Available on action ctx only — sending email is external
  * I/O, not allowed in mutation transactions.
  *
+ * This is the APP email channel (`PYLON_EMAIL_*`): arbitrary recipient
+ * and body, so it must be the app's own provider. It is deliberately
+ * separate from Pylon's built-in auth emails (codes / password reset /
+ * invitations), which send via a `PYLON_AUTH_EMAIL_*` channel. On Pylon
+ * Cloud the auth channel may be a shared, locked-down platform key, so
+ * `ctx.email` stays inert until you set `PYLON_EMAIL_*` yourself — the
+ * shared auth key can never be used to send arbitrary mail.
+ *
  * The runtime owns provider config + credentials; functions only
  * supply the (to, subject, body) tuple. Failures are surfaced as
  * thrown errors; on success the return is void.