v1.9.1 — load paths stop eating your pages

A sass load path with a slash in it silently produced a zero-page markup build. Fixed. The example docs also moved onto the poops-docs-theme package, the first real consumer of v1.9.0's package templates.

Fixed

• includePaths no longer breaks the markup glob. Top-level includePaths is a sass/esbuild load path, but it was also folded into the exclude list the markup compiler globs with — and that list fills a single extglob segment:

  !(node_modules|.git|.svn|.hg|_*)/**/*.+(md|html)

  Any entry with a separator in it made the whole pattern match nothing. A site that legitimately needs "includePaths": ["../node_modules"] — node_modules at the repo root, docs built from a subdirectory — compiled zero pages, exited 0, and said so only as Compiled: 0 file. Entries with a separator are now filtered out of the excludes; bare directory names still exclude as before.

Changed

• The example docs consume poops-docs-theme instead of local copies. The docs layout, nav partial, stylesheet, and script are now an npm dependency — the first real user of the package templates added in v1.9.0. Front matter points at the package, and the theme's sources compile straight out of node_modules:

  {
    "scripts": [
      {
        "in": "node_modules/poops-docs-theme/src/docs.ts",
        "out": "example/dist/js/docs.js"
      }
    ],
    "styles": [
      {
        "in": "node_modules/poops-docs-theme/scss/docs.scss",
        "out": "example/dist/css/docs.css"
      }
    ]
  }

  ---
  layout: poops-docs-theme/docs
  ---

  Four files left the repo and nothing about the docs changed on screen — which was the point.

---