@samva/vite 0.3.0 → 0.5.0

package/AGENTS.md

@@ -7,13 +7,24 @@ programmatic template builds and `@samva/vite/emit` only for module-preview inte
 The CLI loads `@samva/vite/build` from the current project. Keep these authoring dependencies in the
 project lockfile so local preview, check, and build use the same compiler version as the project.
 
+This package is plain TypeScript like `@samva/markup`, and adds no runtime framework of its own to
+a template project. `@samva/vite/build` and the preview surfaces answer with discriminated results
+carrying an `ok` field, and `@samva/vite/emit` passes the compiler's better-result `Result`
+through. A missing `vite`, or an entry that does not default-export a template definition, throws.
+
 Hosted synchronization is ordinary Git. A CLI-created project has a repository-local Samva
 credential helper, and `samva templates publish` accepts only a clean exact commit reachable from
 the fetched `origin` default branch. Publish creates an immutable receipt; it does not push or
 rewrite history.
 
 Template discovery is `.tsx` only. The local email editor writes the canonical TSX entry with a
-revision check and a fresh comparison against disk; SMS and WhatsApp stay read-only. Every discovered entry is imported once through the dev
+revision check and a fresh comparison against disk; SMS and WhatsApp stay read-only. A change
+published without a client is what the editor reads as a foreign edit, so nothing the editor itself
+did may reach it that way. A save and a fixture switch both run in the store's mutation queue, so no
+rebuild can straddle one and publish the difference anonymously; the editor's write comes back
+through the file watcher like any other edit, and a changed file that still holds the bytes its
+entry was built from re-evaluates nothing. Watcher events arrive in bursts and one rebuild re-reads
+the whole project, so a rebuild that has not started yet covers every event queued before it. Every discovered entry is imported once through the dev
 server's own SSR graph, and a default export that is a template definition takes the email lane —
 compiled and rendered through `compileEmailProject`, so a local render cannot drift from a published
 one. Email requires an executable definition. Structured SMS/WhatsApp entries emit SML, and

package/dist/build.js

@@ -152,8 +152,15 @@ const createTemplateBuildSession = async (dir, options = {}) => {
 		}
 		return { files: entries };
 	};
+	const fileEvents = /* @__PURE__ */ new Set([
+		"add",
+		"change",
+		"unlink"
+	]);
 	const subscribe = (listener) => {
-		const onChange = (_event, path) => listener(path);
+		const onChange = (event, path) => {
+			if (fileEvents.has(event)) listener(path);
+		};
 		server.watcher.on("all", onChange);
 		return () => server.watcher.off("all", onChange);
 	};