Skip to content
This repository has been archived by the owner on Sep 5, 2019. It is now read-only.

Why using shrinkwrap? #34

Closed
analog-nico opened this issue Aug 12, 2016 · 1 comment
Closed

Why using shrinkwrap? #34

analog-nico opened this issue Aug 12, 2016 · 1 comment

Comments

@analog-nico
Copy link

analog-nico commented Aug 12, 2016

It somehow makes sense to me that gulp-nsp uses npm shrinkwrap and shrinkydink – awesome lib btw. But nsp is at 2.6.1 and gulp-nsp still depends on 2.3.0.

I didn't open this issue for asking to change anything other than maybe updating nsp at your convenience. Instead I am interested to know what let you to decide to choose a fixed version of nsp over a looser version as a dependency or even a peer dependency. As a library developer myself I get mixed opinions from the community and thus am looking for arguments to make my decisions.

tl;dr: What are your 2 cents about why you chose to use shrinkwrap for gulp-nsp? Thanks a lot!

@nlf
Copy link
Member

nlf commented Feb 15, 2018

we were using it to pin dependencies in a very specific way, as of this moment in time we have stopped. it may come back, it may not. we'll have to evaluate that.

@nlf nlf closed this as completed Feb 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants