PostCSS 8 plugin migration: legacy plugins load but ordering and visitor behavior are unclear
Context We are moving a build pipeline from PostCSS 7 to PostCSS 8 (assume 8.4.x). PostCSS 8 replaced the postcss.plugin() wrapper with factory objects exposing a postcssPlugin name, and made postcss a peer dependency so plugins share one instance. The uncertainty Our plugins array mixes older PostCSS 7-era packages with native PostCSS 8 plugins. The legacy