Open LorenzoBloedow opened 11 months ago
There is no specific policy. PostCSS is old project with big ecosystem and contains many parts—this is the result:
postcss
has big if
s block in plugins loading because we need to support PostCSS 8 plugins, PostCSS 7 plugins, old PostCSS plugins, plugins presets. Also plugins with options (plugin(opts)
) and without (plugin
)postcss-load-config
was written by other developer and some use case could be missedSo, suggest the solution.
I'm trying to figure out two things:
postcss-load-config
treats empty configuration objectsAll the context you need is in this pull request I just opened.
Minimal repro:
npm run build
doiuse
is skipped without warning even thoughpostcss.config.js
is perfectly valid.