cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian LeRoux...@brian.io>
Subject Re: Reason for node_modules in Platform Repos
Date Fri, 19 Dec 2014 20:31:58 GMT
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 <jsoref@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 <dblotsky@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?
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message