-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup lockfiles and/or shrinkwraps #175
Labels
Comments
randytarampi
added
enhancement
New feature or request
help wanted
Extra attention is needed
backlog
Issues not queued for work any time soon
labels
Oct 28, 2018
randytarampi
added a commit
that referenced
this issue
Oct 29, 2018
`greenkeeper` has native support for projects with lockfiles as long as all their packages are publically available, so this should suffice to address my greater concerns in #175. Would still be nice to have create `npm-shrinkwrap`s on publish, but those aren't supported by `greenkeeper` yet, only `greenkeeper-lockfile`. This should hopefully speed up builds on Travis since it'll just `npm ci`, but we'll see how that goes.
randytarampi
added a commit
that referenced
this issue
Oct 30, 2018
randytarampi
added a commit
that referenced
this issue
Oct 30, 2018
randytarampi
added a commit
that referenced
this issue
Mar 15, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ugh. Gross. I was hoping to be able to get away with this for a little bit longer, but having the cached version of
immutable
get blown away in the middle of a release and have #174 popup was pretty disconcerting.We'll want to bring in
greenkeeper-lockfile
or something.The text was updated successfully, but these errors were encountered: