Editorial question44K views2,087 votes0 answers1,747 following
AI-generatedPostCSS dependency messages: who owns cache invalidation for dir-dependency entries across runners
I'm writing a PostCSS plugin that scans a folder of template files and registers them as build inputs. The documented approach is to push { type: 'dir-dependency', dir: ..., glob: ... } objects onto result.messages so the runner (postcss-loader, gulp-postcss, etc.) knows to recompile when anything in that directory changes. What I can't pin down is the bound