@m4l-jweb/build 1.2.0 → 1.2.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@m4l-jweb/build",
-  "version": "1.2.0",
+  "version": "1.2.1",
   "description": "m4l-jweb: the CLI that builds and packages a device repo into installable Max for Live devices.",
   "type": "module",
   "license": "MIT",
@@ -34,6 +34,6 @@
     "archiver": "^7.0.1",
     "esbuild": "^0.25.0",
     "typescript": "^5.7.0",
-    "@m4l-jweb/wrapper": "1.2.0"
+    "@m4l-jweb/wrapper": "1.2.1"
   }
 }

package/src/chains.mjs

@@ -112,42 +112,6 @@ export function claimAppMessages(ctx, routeId, unmatchedOutlet) {
 export const AUDIO_IN = "obj-plugin";
 export const AUDIO_OUT = "obj-plugout";
 
-/**
- * A [buffer~] name that is unique PER DEVICE INSTANCE.
- *
- * THE BUG THIS EXISTS TO KILL. Buffer names are GLOBAL to Max, and they used to be
- * generated from the device name alone (`buf-<device>-<slot>`) and frozen into the
- * patcher at BUILD time. So two copies of one device - a drum rack on two tracks, which
- * is the normal case, not an exotic one - named their buffers identically, and Max gave
- * both to whichever loaded last. One rack's samples silently became the other's. No
- * error, no console line: just the wrong sound.
- *
- * A name minted by the wrapper after load cannot reach a box frozen at build time (a
- * buffer takes its name from its creation argument and there is no documented runtime
- * rename), so the scoping has to be a load-time substitution Max itself performs.
- *
- * `#0` WAS TRIED AND DOES NOT WORK (spike run 2026-07-17 in Live; see
- * doc/MAX-FACTS.md). `#0` is documented for abstractions, and an .amxd device patcher turned out
- * not to count as one: the token stayed literal in every instance, so writer and
- * reader still agreed on one global name and the collision survived, silently.
- *
- * `---` IS THE MECHANISM BUILT FOR THIS. Max for Live replaces a leading `---` in a
- * name with an id unique to the DEVICE instance - and the scope is the whole device,
- * subpatchers and [poly~] voices included, not one patcher. That kills the `#0`/`#1`
- * hand-off the first attempt needed: the voice spells the SAME name the device does,
- * and no id has to travel through [poly~]'s arguments.
- *
- * OUTSIDE LIVE `---` stays literal (it is a Live-only substitution). Both writer and
- * reader keep agreeing, so a patcher opened in standalone Max degrades to the old
- * shared-name behavior instead of breaking - acceptable, since the devices only
- * meaningfully run in Live.
- */
-export const deviceBufName = (device, slot) => `---buf-${device?.name}-${slot}`;
-
-/** The same buffer, as a [poly~] voice spells it: identical - `---` scopes per DEVICE,
- * not per patcher, so the voice shares the expansion with the patcher that loaded it. */
-export const voiceBufName = (device, slot) => deviceBufName(device, slot);
-
 /**
  * How long a `remote` slot takes to slide to each new value, in ms.
  *

package/src/index.mjs

@@ -184,6 +184,19 @@ export function composePatcher(base, d, surface) {
   const mode = d.mode ?? d.type;
   boxes.find((b) => b.box.id === "obj-js").box.text = `js wrapper.js ${mode}`;
 
+  /**
+   * The ring buffer between Chromium's audio thread and MSP, for the DEVICE PAGE's
+   * own `[jweb~]`.
+   *
+   * `window({ audio: true, latency })` has taken this since 1.1.0, and the device
+   * page could not - so a device that put its buffer at the documented maximum for
+   * its sounding WINDOW left its own page at the object default (~21 ms at 48 kHz)
+   * and went on dropping out. Two pages, one setting, and only one of them had it.
+   *
+   * Unset keeps the object's default. jweb~ clamps to 3x the minimum.
+   */
+  if (d.latency != null) boxes.find((b) => b.box.id === "obj-jweb").box.latency = d.latency;
+
   const unmatchedId = d.unmatchedTo === "js" ? "obj-js" : (d.unmatchedTo ?? "obj-js");
 
   /**

package/templates/starter/package.json

@@ -17,13 +17,13 @@
     "format": "prettier --write \"src/**/*.{ts,tsx,css}\" \"scripts/*.mjs\" \"patcher/*.mjs\""
   },
   "dependencies": {
-    "@m4l-jweb/bridge": "^1.2.0",
-    "@m4l-jweb/surface": "^1.2.0",
+    "@m4l-jweb/bridge": "^1.2.1",
+    "@m4l-jweb/surface": "^1.2.1",
     "react": "^19.0.0",
     "react-dom": "^19.0.0"
   },
   "devDependencies": {
-    "@m4l-jweb/build": "^1.2.0",
+    "@m4l-jweb/build": "^1.2.1",
     "@types/node": "^22.0.0",
     "@types/react": "^19.0.0",
     "@types/react-dom": "^19.0.0",

package/templates/starter/tsconfig.json

@@ -1,4 +1,4 @@
 {
 	"files": [],
-	"references": [{ "path": "./tsconfig.app.json" }, { "path": "./tsconfig.node.json" }]
+	"references": [{ "path": "./tsconfig.app.json" }, { "path": "./tsconfig.node.json" }, { "path": "./tsconfig.test.json" }]
 }

package/templates/starter/tsconfig.test.json

@@ -0,0 +1,29 @@
+{
+	// The TESTS, which nothing typechecked before.
+	//
+	// `tsconfig.app.json` covers `src`, `tsconfig.node.json` covers the scripts and the
+	// patcher - and `tests/` fell between them. That is fine for the `.mjs` suites, but
+	// a `.ts` one carrying `expectTypeOf` assertions was checking nothing at all: the
+	// assertion is a TYPE error or it is nothing, so an unchecked type test passes for
+	// the same reason a deleted one does. Referenced from the root solution, so a plain
+	// `tsc -b` (which the build runs first) fails on it.
+	"compilerOptions": {
+		"target": "ES2022",
+		"lib": ["ES2023", "DOM", "DOM.Iterable"],
+		"module": "ESNext",
+		"skipLibCheck": true,
+		"moduleResolution": "bundler",
+		"allowImportingTsExtensions": true,
+		"resolveJsonModule": true,
+		"allowJs": true,
+		"isolatedModules": true,
+		"moduleDetection": "force",
+		"noEmit": true,
+		"strict": true
+	},
+	// `vitest.config.ts` is listed alongside the tests, and not only to check it: a
+	// project whose include matches nothing at all is a tsc ERROR (TS18003), and a
+	// freshly scaffolded repo has no tests yet. One file that always exists keeps the
+	// project valid from the first minute.
+	"include": ["tests/**/*.ts", "vitest.config.ts"]
+}