mikser-io 9.78.0 → 9.79.0

package/docs/diagnostics.md

@@ -882,6 +882,14 @@ surfaces that turn silence into a statement:
 - **A plugin that appears to do nothing** — `No plugins loaded` with a
   config present is a warning naming the file. A config that fails to
   load now exits non-zero rather than loading as empty.
+- **A derivative for a source that is gone.** The assets folder sits at
+  the working-folder root, outside both `outputFolder` and the runtime
+  folder, and it is symlinked INTO the output — so an orphaned derivative
+  is still served, and `find out -type f` cannot see it (that tree is
+  reached through a link; use `find -L`). `--clear` removes the folder and
+  re-derives what still has a source. An ordinary build does not: the
+  files plugin performs no delete sweep, so a source deleted from disk
+  stays in the catalog and its derivative stays with it.
 - **A postprocess that could not run** — a stage whose external
   dependency is absent (no chrome for a PDF, no binary for a conversion)
   reports a fault naming the subsystem, and each page that wanted that

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mikser-io",
-  "version": "9.78.0",
+  "version": "9.79.0",
   "files": [
     "app.js",
     "index.js",

package/src/plugins/assets.js

@@ -291,6 +291,28 @@ export function assets(options = {}) {
         runtime.options.assets = options.assetsFolder || 'assets'
         runtime.options.assetsFolder = path.join(runtime.options.workingFolder, runtime.options.assets)
         logger.debug('Assets folder: %s', runtime.options.assetsFolder)
+
+        // --clear means "throw away what was derived and build it again", and
+        // derivatives are derived — but this folder sits at the working-folder
+        // root, outside both outputFolder and runtimeFolder, so the engine's
+        // clear never reached it. Anything here whose source had gone stayed
+        // forever: still on disk, still SERVED through the symlink below, and
+        // invisible to `find out -type f` because that tree is reached through
+        // a link. The only way out was deleting the folder by hand.
+        //
+        // Cleared here rather than in the engine because the path is not known
+        // until this plugin resolves it — the engine's clear runs before any
+        // plugin's onLoaded.
+        //
+        // Whole folder, not a sweep of orphans: identifying an orphan means
+        // mapping a derivative back to a source, which is the id/name mapping
+        // that has bitten this plugin twice. --clear already accepts a full
+        // rebuild, so re-deriving is the honest cost of asking for one.
+        if (runtime.options.clear) {
+            await rm(runtime.options.assetsFolder, { recursive: true, force: true })
+            logger.info('Assets cleared: %s', runtime.options.assetsFolder)
+        }
+
         await mkdir(runtime.options.assetsFolder, { recursive: true })
 
         let link = path.join(runtime.options.outputFolder, runtime.options.assets)