greenkeeperio
Allow configuring npm version used to update package-lock.json file
First of all a big thanks! This is really a great project, a must have IMHO.
Now with https://blog.greenkeeper.io/announcing-native-lockfile-support-85381a37a0d0 I don't need to use greenkeeper-lockfile package to update the lock file, but the problem is that the PRs I'm getting is seems to be using latest (or at least fairly recent) npm version, which means that the lock file might have a different format than the npm version used in my project. I'm currently using npm 5.x, mostly because I'm using macOS for development while CI runs linux and part of my CI workflow is to verify that npm install doesn't result in any git diff (which usually means that I bumped package.json without running npm install and commiting lock file changes). There has been a number of issues with npm generating a different lock file content on different platforms (with the same package.json), current issue that forced me to stick with 5.x is https://npm.community/t/package-lock-json-keeps-changing-between-platforms-and-runs/1129/4, wich is a continuation of https://github.com/npm/npm/issues/17722 Would be great if I was able to tell Greenkeeper which nodejs/npm version to use if possible, without that I need to manually clone the PR branch, run npm install myself, commit and rebase and then force push to re-run CI jobs.
Hi @prymitive, thank you for the kind words! — You’ll be happy to find out that we are planning exactly this: being able to pick the npm version (at least major version). This will be part of our second or third iteration of this feature.
is an .nvmrc file honored currently? we already use this to keep versions in sync between developers and travis-ci. if not already supported, my request would be to at least support that file.
