Generic config file

[MoOx]

Following #72

What about supporting these file:

• (.)?cssnext.json
• (.)?cssnext.yml
• .cssnextrc (json or yaml)
• (.)?cssnext.config.js (that exports config)

[hgl]

Do you mean a config file that the CLI will automatically look for (in cwd?) when it executes?

[MoOx]

Yep

[magsout]

cssnext.json Sounds good.

Any plan about that ?

[MoOx]

I don't plan to implement that in a near future. That being said, PRs are always welcome (note: maybe we should discuss a little bit on the implementation before pushing this)

[magsout]

This option interests me. I rather like to use a json configs. Especially I want to delete gulp on my workflow. We discuss on irc next week if you're available

[Nyalab]

.cssnextrc with a json syntax

[magsout]

@Nyalab
why *rc ?

edit:

[MoOx]

if we support json, I guess we can easily support js too (trick: export a js object).

Do you think yml support is useless ?
I found yml easier to maintain than json (and it accept comments) but I think I will use JS anyway (especially to require shared variables).

[pascalduez]

.cssnextrc (json or yaml)

Just my too cents.

.<projectname>rc is a widely used convention: .eslintrc, .jshintrc, .babelrc ...

Supporting both JSON and YAML is neat, and a breeze using js-yaml.

One minor hitch though, syntax highlighting in editors with the .rc sheme.

[MoOx]

This will support js/json/yaml

[MoOx]

Do you think js support for the config (like webpack) is mandatory?
I plan to rely on rc but for now this module only handle json/ini. Note that it's easy to add a parser (eg: yaml), so I guess trying to eval() the config might be doable. Not sure if that's a smart/secure idea.

[MoOx]

https://github.com/MoOx/rc-loader is ready.

[MoOx]

Not relevant anymore. cssnext is now postcss-cssnext. cssnext is deprecated. See postcss-cssnext migration guide http://cssnext.io/postcss/