In the current implementation of the Netcentric FE Build, PostCSS plugins that require configuration objects (e.g. [pluginName, options]) were not being handled correctly. Only string-based plugin entries were supported, which limited compatibility with many popular PostCSS plugins that rely on custom options.
This issue made it impossible to use plugins like postcss-extract-media-query, which require detailed configuration to function properly.
The handling of the plugins array has now been improved to support both:
Plugin names as strings (e.g. "postcss-combine-media-query")
Arrays with [pluginName, options] format (e.g. ["postcss-extract-media-query", { extractAll: false }])
This change increases the flexibility of the build system and brings it in line with how PostCSS plugins are typically consumed in modern tooling.
In the current implementation of the Netcentric FE Build, PostCSS plugins that require configuration objects (e.g. [pluginName, options]) were not being handled correctly. Only string-based plugin entries were supported, which limited compatibility with many popular PostCSS plugins that rely on custom options.
This issue made it impossible to use plugins like postcss-extract-media-query, which require detailed configuration to function properly.
The handling of the plugins array has now been improved to support both:
Plugin names as strings (e.g. "postcss-combine-media-query")
Arrays with [pluginName, options] format (e.g. ["postcss-extract-media-query", { extractAll: false }])
This change increases the flexibility of the build system and brings it in line with how PostCSS plugins are typically consumed in modern tooling.