{"action":"created","issue":{"url":"https://api.github.com/repos/kitze/create-react-app/issues/19","repository_url":"https://api.github.com/repos/kitze/create-react-app","labels_url":"https://api.github.com/repos/kitze/create-react-app/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/kitze/create-react-app/issues/19/comments","events_url":"https://api.github.com/repos/kitze/create-react-app/issues/19/events","html_url":"https://github.com/kitze/create-react-app/issues/19","id":181096793,"number":19,"title":"Better way to manage webpack config","user":{"login":"stereobooster","id":179534,"avatar_url":"https://avatars.githubusercontent.com/u/179534?v=3","gravatar_id":"","url":"https://api.github.com/users/stereobooster","html_url":"https://github.com/stereobooster","followers_url":"https://api.github.com/users/stereobooster/followers","following_url":"https://api.github.com/users/stereobooster/following{/other_user}","gists_url":"https://api.github.com/users/stereobooster/gists{/gist_id}","starred_url":"https://api.github.com/users/stereobooster/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stereobooster/subscriptions","organizations_url":"https://api.github.com/users/stereobooster/orgs","repos_url":"https://api.github.com/users/stereobooster/repos","events_url":"https://api.github.com/users/stereobooster/events{/privacy}","received_events_url":"https://api.github.com/users/stereobooster/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-10-05T08:48:26Z","updated_at":"2016-11-21T08:58:35Z","closed_at":"2016-11-21T08:47:55Z","body":"I suppose I'm not the only one who finds Webpack configuration hard to maintain.\n\nConfigurations are not portable/sharable: there is no (good) way to pack configs in modules and reuse across a project. I want to be able to do something like install module `webpack-sass-config` and it will work out of the box with reasonable defaults (Convention over configuration). \n\nAs of now default way to share code across projects is _copy/paste_. Including this project which patches initial webpack (and this is error prone and hard to maintain).\n\nI know this is problem of webpack not this repo, but this problem is big part of this project which is why I'm creating issue here. Maybe we can come up with reasonable solution.\n\nThere are some projects which tried to solve this:\n- https://github.com/mdreizin/webpack-config by @mdreizin\n- https://github.com/jakubbabiak/webpack-configurator by @jakubbabiak\n- https://github.com/lewie9021/webpack-configurator by @lewie9021\n\n---\n\nrelated: https://github.com/facebookincubator/create-react-app/issues/670\n"},"comment":{"url":"https://api.github.com/repos/kitze/create-react-app/issues/comments/261880291","html_url":"https://github.com/kitze/create-react-app/issues/19#issuecomment-261880291","issue_url":"https://api.github.com/repos/kitze/create-react-app/issues/19","id":261880291,"user":{"login":"bebraw","id":166921,"avatar_url":"https://avatars.githubusercontent.com/u/166921?v=3","gravatar_id":"","url":"https://api.github.com/users/bebraw","html_url":"https://github.com/bebraw","followers_url":"https://api.github.com/users/bebraw/followers","following_url":"https://api.github.com/users/bebraw/following{/other_user}","gists_url":"https://api.github.com/users/bebraw/gists{/gist_id}","starred_url":"https://api.github.com/users/bebraw/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bebraw/subscriptions","organizations_url":"https://api.github.com/users/bebraw/orgs","repos_url":"https://api.github.com/users/bebraw/repos","events_url":"https://api.github.com/users/bebraw/events{/privacy}","received_events_url":"https://api.github.com/users/bebraw/received_events","type":"User","site_admin":false},"created_at":"2016-11-21T08:58:35Z","updated_at":"2016-11-21T08:58:35Z","body":"@kitze Yeah. If you have time, consider giving [webpack-merge](https://www.npmjs.com/package/webpack-merge) a quick go. I expect it would go a long way if you could provide a place where to literally extend the core configs. You would have to intercept before passing the configuration to webpack but after that you could do quite a few things.\r\n\r\nI guess the main problem is that you would be operating against a black box still. I expect simple configuration, like adding a new loader or plugin, would be easy, but for anything more complicated than that you would have to eject. Still, that would be far better than the current situation I think as staying without ejecting as long as possible would be extreme useful when it comes to maintenance."}}
{"actor":{"display_login":"bebraw"}}