cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Gill <>
Subject Re: [DISCUSS] shrinkwrap
Date Wed, 01 Oct 2014 22:12:51 GMT
In the past, semver has caused me problems due to having modules npm
linked. Ex Running npm shrinkwrap on cordova-lib while i have cordva-js
linked will break.

Shrinkwrap also requires those dependencies to already be on npm. So if I
reference cordova-js 3.7.0 and it hasn't been published yet, it will fail.

Overall, I find it to be very annoying. I can follow the instructions step
by step while releasing to get around some of these problems (publishing
dependent packages first, remembering to unlink) but it just feels like a
waste of time to me.

Another problem is if we leave it in master, it will cause headaches as we
do local dev. Will have to remember to remove it.

Pinning seems like much better option IMO

On Wed, Oct 1, 2014 at 1:46 PM, Marcel Kinard <> wrote:

> From my scars of the last release, what I'd suggest as closer to the ideal
> of "benefits of shrinkwrap with a lower cost" would be to publish to a
> private npm repo and use something like the --registry flag to test. Using
> a private registry would also give us the opportunity to wipe any published
> packages in case a republish is needed, to avoid bumping the version
> numbers.
> Until we have a private registry for release testing, I agree with Steve
> that rc's should not be published to npm, and instead use --usegit.
> On Oct 1, 2014, at 4:25 PM, Andrew Grieve <> wrote:
> > The root of what I meant I guess, was that if shrinkwrap doesn't work
> > without publishing, then let's just publish and don't sweat version
> numbers
> > jumping by more than one. If we can get shrinkwrap to work through
> another
> > means (private npm repo?), than that's even better.
> >
> > On Wed, Oct 1, 2014 at 4:00 PM, Josh Soref <>
> wrote:
> >
> >> Steven Gill wrote:
> >>> we can test platform rc's with --usegit and
> >>> eventually a private npm registry for testing.
> >>
> >> +1
> >>
> >>

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