{"action":"closed","issue":{"url":"https://api.github.com/repos/Semantic-Org/Semantic-UI/issues/2224","labels_url":"https://api.github.com/repos/Semantic-Org/Semantic-UI/issues/2224/labels{/name}","comments_url":"https://api.github.com/repos/Semantic-Org/Semantic-UI/issues/2224/comments","events_url":"https://api.github.com/repos/Semantic-Org/Semantic-UI/issues/2224/events","html_url":"https://github.com/Semantic-Org/Semantic-UI/issues/2224","id":73993792,"number":2224,"title":"Consider rethinking dependencies and post install script","user":{"login":"timkelty","id":18329,"avatar_url":"https://avatars.githubusercontent.com/u/18329?v=3","gravatar_id":"","url":"https://api.github.com/users/timkelty","html_url":"https://github.com/timkelty","followers_url":"https://api.github.com/users/timkelty/followers","following_url":"https://api.github.com/users/timkelty/following{/other_user}","gists_url":"https://api.github.com/users/timkelty/gists{/gist_id}","starred_url":"https://api.github.com/users/timkelty/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/timkelty/subscriptions","organizations_url":"https://api.github.com/users/timkelty/orgs","repos_url":"https://api.github.com/users/timkelty/repos","events_url":"https://api.github.com/users/timkelty/events{/privacy}","received_events_url":"https://api.github.com/users/timkelty/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-05-07T13:47:47Z","updated_at":"2015-05-07T22:09:38Z","closed_at":"2015-05-07T22:09:38Z","body":"Semantic UI currently makes the assumption that the dev will `npm install semantic-ui`, go through the build process, and use the resulting files.\r\n\r\nHowever, if the dev already has their own build solutions in place and wants to use semantic-ui's source files directly, this doesn't necessarily work very well.\r\n\r\nFor example, we use [Webpack](http://webpack.github.io/), alongside Gulp. Therefore, what I _want_ to do is `npm install semantic-ui --save-dev` and then require the source files directly. However, the post-install script forces me to go through a build step I don't want. (yes, I could `npm install --ignore-scripts`, but then I'd have to every time).\r\n\r\nAlong the same lines, if I'm using my own frontend tooling, then much of what is listed as a `peerDependencies` and `dependencies` may conflict.\r\n\r\nE.g., when I run `npm install semantic-ui --ignore-scripts`:\r\n```\r\nnpm ERR! peerinvalid The package gulp-plumber does not satisfy its siblings' peerDependencies requirements!\r\nnpm ERR! peerinvalid Peer semantic-ui@1.12.2 wants gulp-plumber@0.*\r\n```\r\n\r\nI think those would be better served as `devDependencies` (or maybe `optionalDependencies`).\r\n\r\nThoughts?"}}