yeaaaah, we've been through this in other threads. pin the dep in package.json to a version or sha and your problem is solved. the only time a node_modules should be checked in, maybe, is in a deployment scenario for hosted service type things.
(bad corp networks aside!) On Fri, Dec 19, 2014 at 12:18 PM, Josh Soref <jso...@blackberry.com> wrote: > Not true! > > It was for stability so that we wouldn't be reliant on various things that > could fail/change/flake. > > Personally, in our network environment, any project which decides to > reference a git: url becomes unimportable. > > If they happen to be transcluded via packaged node_modules, then this is a > non-issue. > > On 12/19/14, 3:16 PM, "Brian LeRoux" <b...@brian.io> wrote: > > >none. go fix it! > > > >On Fri, Dec 19, 2014 at 12:07 PM, Dmitry Blotsky <dblot...@microsoft.com> > >wrote: > > > >> Hi all, > >> > >> What was the design decision and reasoning behind full node_module > >> directories being committed to platform repositories along with the > >>source, > >> instead of being installed from the respective package.json at the time > >> that the platform is obtained? >
