Skip to content
This repository was archived by the owner on Dec 19, 2024. It is now read-only.

Generic config file #73

Closed
MoOx opened this issue Feb 26, 2015 · 13 comments · Fixed by #238
Closed

Generic config file #73

MoOx opened this issue Feb 26, 2015 · 13 comments · Fixed by #238
Assignees

Comments

@MoOx
Copy link
Owner

MoOx commented Feb 26, 2015

Following #72

What about supporting these file:

  • (.)?cssnext.json
  • (.)?cssnext.yml
  • .cssnextrc (json or yaml)
  • (.)?cssnext.config.js (that exports config)
@hgl
Copy link

hgl commented Feb 27, 2015

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

@MoOx
Copy link
Owner Author

MoOx commented Feb 27, 2015

Yep

@magsout
Copy link
Contributor

magsout commented Mar 27, 2015

cssnext.json Sounds good.

Any plan about that ?

@MoOx
Copy link
Owner Author

MoOx commented Mar 27, 2015

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
Copy link
Contributor

magsout commented Mar 27, 2015

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

@MoOx MoOx mentioned this issue Apr 3, 2015
@Nyalab
Copy link
Contributor

Nyalab commented Apr 3, 2015

.cssnextrc with a json syntax

@magsout
Copy link
Contributor

magsout commented Apr 3, 2015

@Nyalab
why *rc ?

edit:
facepalm-gif-31

@MoOx
Copy link
Owner Author

MoOx commented Apr 3, 2015

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
Copy link
Contributor

.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 MoOx removed this from the v2.0.0 milestone Jun 8, 2015
@MoOx
Copy link
Owner Author

MoOx commented Jun 17, 2015

This will support js/json/yaml

@MoOx
Copy link
Owner Author

MoOx commented Aug 3, 2015

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
Copy link
Owner Author

MoOx commented Sep 16, 2015

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

@MoOx MoOx mentioned this issue Dec 29, 2015
5 tasks
@MoOx MoOx closed this as completed in #238 Jan 4, 2016
@MoOx
Copy link
Owner Author

MoOx commented Jan 4, 2016

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants