{"action":"opened","issue":{"url":"https://api.github.com/repos/Workiva/wGulp/issues/136","labels_url":"https://api.github.com/repos/Workiva/wGulp/issues/136/labels{/name}","comments_url":"https://api.github.com/repos/Workiva/wGulp/issues/136/comments","events_url":"https://api.github.com/repos/Workiva/wGulp/issues/136/events","html_url":"https://github.com/Workiva/wGulp/issues/136","id":59708312,"number":136,"title":"Use npm shrinkwrap and/or pin dependencies where possible to avoid breaking changes","user":{"login":"evanweible-wf","id":1738457,"avatar_url":"https://avatars.githubusercontent.com/u/1738457?v=3","gravatar_id":"","url":"https://api.github.com/users/evanweible-wf","html_url":"https://github.com/evanweible-wf","followers_url":"https://api.github.com/users/evanweible-wf/followers","following_url":"https://api.github.com/users/evanweible-wf/following{/other_user}","gists_url":"https://api.github.com/users/evanweible-wf/gists{/gist_id}","starred_url":"https://api.github.com/users/evanweible-wf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/evanweible-wf/subscriptions","organizations_url":"https://api.github.com/users/evanweible-wf/orgs","repos_url":"https://api.github.com/users/evanweible-wf/repos","events_url":"https://api.github.com/users/evanweible-wf/events{/privacy}","received_events_url":"https://api.github.com/users/evanweible-wf/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-03T21:27:47Z","updated_at":"2015-03-03T21:27:47Z","closed_at":null,"body":"Ideally, setting up our dependencies like we've done (with the caret `^`) should be fine because packages follow semver and updating minor versions shouldn't break compatibility. But, as demonstrated by our recent issue with PhantomJS (https://github.com/Workiva/wGulp/pull/135), this isn't always the case.\r\n\r\nWe should investigate the following:\r\n- Pinning as many dependencies as possible\r\n  - Pro: Pinned dependencies can't break wGulp in the future\r\n  - Con: We don't get the benefit of continuously receiving their updates\r\n- Using npm shrinkwrap\r\n  - Pro: We can still specify package ranges, but lock them down once we have a working set\r\n  - Pro: Easier to update dependencies\r\n  - Con: Still need to cut new releases to update dependencies"}}