funoteka 0.1.3 → 0.1.4

package/CHANGELOG.md

@@ -9,6 +9,21 @@ The version lives in exactly one place — `package.json`.
 
 _(nothing yet)_
 
+## [0.1.4] — 2026-09-17
+
+### Fixed
+
+- **The scan started from the server starts again.** `src/cli.ts` called
+  `entryPoint('./cli')` and the helper's default base was `import.meta.url`
+  evaluated *inside the helper* — so `./cli` resolved against `src/cli/`, not the
+  caller, and the scan child died with `Cannot find module '.../src/cli/cli.ts'`.
+  That killed every server-side entry to a scan: `POST /scan`, the MCP
+  `funoteka_scan_start` tool, the interval timer and the reader-change trigger.
+  The CLI scan kept working, which is why a broken published build read as a
+  deployment problem. The base is now a **required** argument to `entryPoint`
+  (forgetting it is a `TS2554`, and a path that does not exist throws), both call
+  sites name it, and the seam has tests over the exact pair the call sites use.
+
 ## [0.1.3] — 2026-09-17
 
 ### Changed

package/DEPLOY.md

@@ -61,7 +61,7 @@ node -e "console.log(require('crypto').randomBytes(32).toString('base64url'))"
 ## 3. Path A — Docker (main path)
 
 Works the same on a laptop, a NAS and a VDS. There is a **published image** —
-`ghcr.io/kzntsv-dev/funoteka:0.1.3`, `linux/amd64` and `linux/arm64` in one
+`ghcr.io/kzntsv-dev/funoteka:0.1.4`, `linux/amd64` and `linux/arm64` in one
 manifest — and `build: .` still builds on the machine that runs it (that is the
 path where a published image is not wanted or not reachable).
 
@@ -75,7 +75,7 @@ docker run -d --name funoteka -p 4533:4533 -p 4534:4534 \
   -e FUNOTEKA_ADMIN_TOKEN=PASTE_THE_TOKEN_YOU_GENERATED \
   -e FUNOTEKA_SUPERVISED=1 -e FUNOTEKA_LOG_FILE=/data/funoteka.log \
   -v "$MUSIC":/music:ro -v funoteka-data:/data \
-  --restart unless-stopped ghcr.io/kzntsv-dev/funoteka:0.1.3
+  --restart unless-stopped ghcr.io/kzntsv-dev/funoteka:0.1.4
 ```
 
 (The token above is a placeholder with no angle brackets in it, on purpose: a

package/dist/api/envelope.js

@@ -30,7 +30,7 @@ export const API_VERSION = '1.16.1';
  * module every route depends on.
  */
 export const SERVER_TYPE = 'funoteka';
-export const SERVER_VERSION = '0.1.3';
+export const SERVER_VERSION = '0.1.4';
 /**
  * The fields every answer carries, whatever the answer is.
  *

package/dist/cli/daemon.js

@@ -101,8 +101,10 @@ export async function start(dbPath, argv, timeoutMs = 15_000) {
     const log = openSync(logPath(dbPath), 'a');
     const child = spawn(process.execPath, 
     // The entry point as *this* build spells it — `.ts` beside the sources, `.js`
-    // in the compiled build the npm package ships (see `cli/entry.ts`).
-    [entryPoint('../cli'), 'serve', ...argv], {
+    // in the compiled build the npm package ships (see `cli/entry.ts`). The base
+    // is this module's own URL, because the relative name is counted from the
+    // file that spawns (`issue:91`).
+    [entryPoint('../cli', import.meta.url), 'serve', ...argv], {
         detached: true,
         // Nothing on stdin: a daemon that could read a terminal would be waiting
         // on a prompt nobody is there to answer.

package/dist/cli/entry.js

@@ -13,13 +13,34 @@ import { fileURLToPath } from 'node:url';
  *
  * Asking the filesystem instead of inferring the answer from the caller's own
  * extension makes it checkable rather than assumed: the emitted file is preferred
- * because a tree that has one is a built tree, the source is the fallback, and
- * neither existing names the source — so the failure reads as "the build did not
- * run" rather than as a `.js` that was never going to be there.
+ * because a tree that has one is a built tree, the source is the fallback.
+ *
+ * ## The base is the caller's, and it is a parameter rather than a default
+ *
+ * `from` has **no default on purpose.** It had one — `import.meta.url`, which
+ * reads as "here" and is evaluated *in this file*: so a caller writing
+ * `entryPoint('./cli')` from `src/cli.ts` was asking for a sibling of
+ * `src/cli/entry.ts`, and got `src/cli/cli.ts`, which does not exist. The server
+ * answered `202` to `POST /scan`, the child died on `MODULE_NOT_FOUND`, and the
+ * only trace was in the child's stderr — `issue:91`, and it reached a released
+ * image because nothing in the suite ran the command the scanner builds. A
+ * required parameter turns that from a silent wrong path into a compile error at
+ * the next call site, which is the version of this that cannot happen again.
+ *
+ * ## And a path that is not there is a throw, not a guess
+ *
+ * The first version returned the `.ts` spelling whether or not it existed, so a
+ * wrong base travelled out of here as a plausible-looking string and failed
+ * somewhere else entirely. Now the search either finds a file or says so.
  */
-export function entryPoint(relative, from = import.meta.url) {
+export function entryPoint(relative, from) {
     const emitted = fileURLToPath(new URL(`${relative}.js`, from));
     if (existsSync(emitted))
         return emitted;
-    return fileURLToPath(new URL(`${relative}.ts`, from));
+    const source = fileURLToPath(new URL(`${relative}.ts`, from));
+    if (existsSync(source))
+        return source;
+    throw new Error(`no entry point beside ${fileURLToPath(from)}: neither ${emitted} nor ${source} exists. ` +
+        `A relative name is resolved against the base the caller passes, so a base that is not ` +
+        `the calling module's own URL looks in the wrong directory.`);
 }

package/dist/cli.js

@@ -494,7 +494,10 @@ function listen(db, config, admin, scan, stopLog) {
             args: [
                 // The entry point as *this* build spells it — `.ts` beside the sources,
                 // `.js` in the compiled build the npm package ships (see `cli/entry.ts`).
-                entryPoint('./cli'),
+                // `import.meta.url` is this module's, and it has to be passed: the name is
+                // relative to the file that *spawns*, not to the helper that resolves it
+                // (`issue:91`).
+                entryPoint('./cli', import.meta.url),
                 'scan',
                 ...listRoots(db).map((one) => one.path),
                 '--db',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "funoteka",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "Subsonic-compatible server: smart music library — scanner-classifier, cue splitting, meta layer, virtual tree",
   "license": "MIT",
   "type": "module",