{"action":"created","issue":{"url":"https://api.github.com/repos/feross/standard/issues/87","labels_url":"https://api.github.com/repos/feross/standard/issues/87/labels{/name}","comments_url":"https://api.github.com/repos/feross/standard/issues/87/comments","events_url":"https://api.github.com/repos/feross/standard/issues/87/events","html_url":"https://github.com/feross/standard/issues/87","id":64573630,"number":87,"title":"Suggestion: splitting core out","user":{"login":"mattdesl","id":1383811,"avatar_url":"https://avatars.githubusercontent.com/u/1383811?v=3","gravatar_id":"","url":"https://api.github.com/users/mattdesl","html_url":"https://github.com/mattdesl","followers_url":"https://api.github.com/users/mattdesl/followers","following_url":"https://api.github.com/users/mattdesl/following{/other_user}","gists_url":"https://api.github.com/users/mattdesl/gists{/gist_id}","starred_url":"https://api.github.com/users/mattdesl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mattdesl/subscriptions","organizations_url":"https://api.github.com/users/mattdesl/orgs","repos_url":"https://api.github.com/users/mattdesl/repos","events_url":"https://api.github.com/users/mattdesl/events{/privacy}","received_events_url":"https://api.github.com/users/mattdesl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-03-26T16:29:52Z","updated_at":"2015-03-26T23:32:55Z","closed_at":null,"body":"Just flowing some thoughts here, let me know if you guys are interested or not.\r\n\r\nWhat if the core was split into its own module to better facilitate forks like `semistandard` and create an ecosystem like `google-standard`, `airbnb-standard`, etc. The module would just handle ESLint reporting with a given config. Then `standard` would be a thin wrapper around that module, using the current `.eslintrc`. \r\n\r\nHaving everybody on the same page is great for npm as a whole, but also a difficult goal to attain given the diversity of JS devs and their work. For example; a lot of client work I do gets touched by many devs (freelancers, juniors, co-op students, etc) and runs on very tight deadlines. Rules like `newline at end of file`, `space after comments`, `single quotes only` slow down our development and lead to distracting lint noise.\r\n\r\nHowever, it would still be beneficial for us to have a tool like `jam3-standard` so that our modules can catch true syntax errors. It also means that we can releases changes to our code style using SemVer, which is (in my view) a huge innovation brought forward by `standard`.  "},"comment":{"url":"https://api.github.com/repos/feross/standard/issues/comments/86753798","html_url":"https://github.com/feross/standard/issues/87#issuecomment-86753798","issue_url":"https://api.github.com/repos/feross/standard/issues/87","id":86753798,"user":{"login":"yoshuawuyts","id":2467194,"avatar_url":"https://avatars.githubusercontent.com/u/2467194?v=3","gravatar_id":"","url":"https://api.github.com/users/yoshuawuyts","html_url":"https://github.com/yoshuawuyts","followers_url":"https://api.github.com/users/yoshuawuyts/followers","following_url":"https://api.github.com/users/yoshuawuyts/following{/other_user}","gists_url":"https://api.github.com/users/yoshuawuyts/gists{/gist_id}","starred_url":"https://api.github.com/users/yoshuawuyts/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yoshuawuyts/subscriptions","organizations_url":"https://api.github.com/users/yoshuawuyts/orgs","repos_url":"https://api.github.com/users/yoshuawuyts/repos","events_url":"https://api.github.com/users/yoshuawuyts/events{/privacy}","received_events_url":"https://api.github.com/users/yoshuawuyts/received_events","type":"User","site_admin":false},"created_at":"2015-03-26T23:32:55Z","updated_at":"2015-03-26T23:32:55Z","body":"> Rules (...) only slow down our development and lead to distracting lint noise.\r\n\r\nThe way golang developers solve this is by having `go fmt` run on every file save through editor plugins. Doing the same with [`standard-format`](https://github.com/maxogden/standard-format) might be the right way to tackle this."}}