Dashboard › spotlight › Distillation
fb2888cd-7d67-47b3-a87a-aea6afb93780["e9e0b57687bf7bedd10aa01b3bc95bf9","8371492ad8736b32b3025080ee57788c"]
Date: July 28, 2026
require('brace-expansion') (no ESM default import): app-builder-lib@24.13.3 (minimatch.js:19 const expand = require('brace-expansion')), dir-compare@3.3.0 & @4.2.0 (minimatch.js:10 var expand = require('brace-expansion')), @electron/asar@3.2.13 & @3.4.1 (minimatch.js:10), @electron/universal@1.5.1 (minimatch.js:10), eslint@8.57.1 (minimatch.js:10), @eslint/eslintrc@2.1.4 (minimatch.js:10), filelist@1.0.4 (minimatch.js:19 const expand = require('brace-expansion')), glob@7.2.3 (minimatch.js:10).expand.expand(...) and never access .default, so CJS require returning module.exports works. Root-cause refinement: Vite module-runner evaluates Astro config in ESM context; an ESM module doing import brace from 'brace-expansion' (default import of CJS) fails when CJS has __esModule: true and no default (5.0.8). 5.0.7 (no __esModule) gets synthesized default = module.exports → works.<=5.0.7 covers both 2.1.0 and 5.0.7); (3) Override glob@13.0.6→glob@10.4.5 (minimatch 9 → brace 2.x CJS) — initially REJECTED as risky (glob@13 vs 10 API), now chosen to TEST via pnpm override "glob@>=13.0.0": "10.4.5" + rebuild website, as only way to clear #323 fully while keeping build green.require('brace-expansion') CJS (5.0.7 works, 5.0.8 fails via __esModule); stated @vercel/nft hard-pins glob@^13→minimatch 10→brace 5.x; stated plan to test overriding glob@13 to glob@10.4.5 (uses minimatch 9 → brace 2.x CJS) to avoid the 5.x line and clear #323 without breaking build.