{"action":"created","issue":{"url":"https://api.github.com/repos/postcss/postcss/issues/477","labels_url":"https://api.github.com/repos/postcss/postcss/issues/477/labels{/name}","comments_url":"https://api.github.com/repos/postcss/postcss/issues/477/comments","events_url":"https://api.github.com/repos/postcss/postcss/issues/477/events","html_url":"https://github.com/postcss/postcss/issues/477","id":99291932,"number":477,"title":"Make PostCSS a complete tool (cli/.postcssrc builtin)","user":{"login":"MoOx","id":157534,"avatar_url":"https://avatars.githubusercontent.com/u/157534?v=3","gravatar_id":"","url":"https://api.github.com/users/MoOx","html_url":"https://github.com/MoOx","followers_url":"https://api.github.com/users/MoOx/followers","following_url":"https://api.github.com/users/MoOx/following{/other_user}","gists_url":"https://api.github.com/users/MoOx/gists{/gist_id}","starred_url":"https://api.github.com/users/MoOx/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MoOx/subscriptions","organizations_url":"https://api.github.com/users/MoOx/orgs","repos_url":"https://api.github.com/users/MoOx/repos","events_url":"https://api.github.com/users/MoOx/events{/privacy}","received_events_url":"https://api.github.com/users/MoOx/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/postcss/postcss/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":22,"created_at":"2015-08-05T20:29:44Z","updated_at":"2015-08-18T11:34:21Z","closed_at":null,"body":"I just read the thread about the upcoming Babel 6.0 https://github.com/babel/babel/issues/2168\r\n\r\ntl;dr: Instead of being something similar to cssnext, Babel will become an engine, like PostCSS.\r\n\r\nI think this is a really nice road. PostCSS is already on it, so it's awesome. I was trying hard to make cssnext THE solution, but I guess I failed, people like modularity (and don't care that much about standard).\r\ncssnext has too many problem to handle with potential specs changes (that's why Babel is moving from a solution with many transformers to none).\r\n\r\nThe idea of preset for Babel seems really the way to go (\"preset-es2015\" :heart:). The thing is, cssnext can't do that, because csswg is working on different modules. So I guess it's time to think about deprecating cssnext.\r\nThe thing I love in both cssnext and babel is that they have a cli builtin and an easy management for conf (.babelrc, I am currently working on .cssnextrc - but I am not sure I should finish my work).\r\nWhat I am offering here (and really think it will be just awesome for PostCSS) is to bring you back my work to easily add a CLI builtin + a .postcssrc.\r\nDirect benefits are:\r\n- cli builtin is a really nice thing, especially to share postcssified code (this will easily solve #434)  because this way, you can add a prepublish hook to publish transformed code to npm for example.\r\n- all postcss runners will have less work to do (every plugins might be defined in .postcssrc) and PostCSS will handle a same config the same way from all runners. This is a great added value we can bring.\r\n\r\n**This will not require a lot of code in postcss** because work is already done as separate module (or will be in a couple of days):\r\n- a recently made a .*rc loader that support YAML, JSON and JavaScript ! (`module.exports = {/*config*/}` like webpack, very nice to configure plugins) https://github.com/MoOx/rc-loader\r\n- I am exporting the cli+watcher of cssnext for stylelint (see https://github.com/stylelint/stylelint/issues/288) as a standalone module, so using this into PostCSS will probably be just a small file of javascript.\r\n\r\nDiscussion is open !"},"comment":{"url":"https://api.github.com/repos/postcss/postcss/issues/comments/132182029","html_url":"https://github.com/postcss/postcss/issues/477#issuecomment-132182029","issue_url":"https://api.github.com/repos/postcss/postcss/issues/477","id":132182029,"user":{"login":"codemakerlive","id":9938875,"avatar_url":"https://avatars.githubusercontent.com/u/9938875?v=3","gravatar_id":"","url":"https://api.github.com/users/codemakerlive","html_url":"https://github.com/codemakerlive","followers_url":"https://api.github.com/users/codemakerlive/followers","following_url":"https://api.github.com/users/codemakerlive/following{/other_user}","gists_url":"https://api.github.com/users/codemakerlive/gists{/gist_id}","starred_url":"https://api.github.com/users/codemakerlive/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/codemakerlive/subscriptions","organizations_url":"https://api.github.com/users/codemakerlive/orgs","repos_url":"https://api.github.com/users/codemakerlive/repos","events_url":"https://api.github.com/users/codemakerlive/events{/privacy}","received_events_url":"https://api.github.com/users/codemakerlive/received_events","type":"User","site_admin":false},"created_at":"2015-08-18T11:34:21Z","updated_at":"2015-08-18T11:34:21Z","body":"Thanks, I was just about to edit to add...\r\n\r\nI'm curious if/how you see the CLI differing from https://github.com/code42day/postcss-cli"}}