Ensure options are passed to plugins when using postcss.config.js

[JohnAlbin]

If a postcss.config.js is used (instead of passing a plugins array), the PostCSS options passed to gulp-postcss are ignored by all PostCSS plugins.

If you look at the default export for postcs-load-config, you'll see:

declare function postcssrc(ctx?: ConfigContext, path?: string, options?: CosmiconfigOptions): Promise<Result>;
export = postcssrc;

where ConfigContext is defined as:

import { ProcessOptions } from "postcss";

// The full shape of the ConfigContext.
type ConfigContext = Context & ProcessOptionsPreload & RemainingProcessOptions;

// Additional context options that postcss-load-config understands.
interface Context {
    cwd?: string;
    env?: string;
}

interface ProcessOptionsPreload {
    parser?: string | ProcessOptions['parser'];
    stringifier?: string | ProcessOptions['stringifier'];
    syntax?: string | ProcessOptions['syntax'];
}

// The remaining ProcessOptions, sans the three above.
type RemainingProcessOptions =
    Pick<ProcessOptions, Exclude<keyof ProcessOptions, keyof ProcessOptionsPreload>>;

and ProcessOptions, defined in PostCSS, contains these keys: from, to, parser, stringifier, syntax, map.

TLDR; the first argument to postcssrc() is a single object with Context and PostCSS' ProcessOptions merged together.

But gulp-postcss is calling postcssrc() with { file: file, options: contextOptions } as its first argument. I noticed 2 things with this:

file is not a part of Context or ProcessOptions. But I see that postcss-load-config's README says:

Most third-party integrations add additional properties (emphasis mine) to the ctx (e.g postcss-loader).

It looks like that is what gulp-postcss is doing with the additional file property. HOWEVER, the ProcessOptions are not passed as a part of the ctx properties; instead they are put into a sub-property, ctx.options. That means the options passed to gulp-postcss are ignored by all PostCSS plugins since they are not where they are supposed to be.

[coveralls]

Coverage remained the same at 100.0% when pulling 5b98eae718919c29956d1400459229920c9f2d6c on JohnAlbin:pass-options-to-plugins into a1b82428212343b18d79a288b11c0df8d1cd0bbc on postcss:master.

[JohnAlbin]

I discovered this while using postcss-url and passing { to: 'outputfile.css' } to gulpPostCSS() was ignored by the plugin.

[JohnAlbin]

I consider passing the options in as ctx.options a bug, but I can see that this behaviour is explicitly documented in the code snippet at the bottom of gulp-postcss's README:

module.exports = function (ctx) {
    var file = ctx.file;
    var options = ctx.options;

I've fixed the bug and the above code snippet, but I've also added 1cd7e21 to ensure backwards compatibility with 9.0.0 if you want to release a 9.0.1 after this bugifx. That commit should be reverted before a 10.0.0 release is made, IMO.

[w0rm]

Thanks, I guess this is backwards compatible, so I am going to just merge this.