3.2.1: Different behavior when referencing a git repo as dependency without sha/branch/tag.

[pleunv]

Somewhat related to my previous issue #9143.

Given the following dep config in package.json:

"dependencies": {
  "internal-dependency": "git+https://<bitbucket-api-key>:x-oauth-basic@bitbucket.org/<username>/internal-dependency.git"
}

npm@2 would do a reinstall of the module with every npm install, automatically fetching any new commits.
npm@3.2.1 installs the module initially, ignores it during all subsequent npm installs.

Is there a way in v3 to get v2's behavior back? Even better, would there be a way to make it poll the repo and see if the package version or at least the most recent commit has changed before it pulls any changes?

[iarna]

Reminder to ourselves, I started to work on infrastructure to support checking for changed git sources here: https://github.com/npm/git-repo-manager

[pleunv]

Hurray!
On Sat, 24 Oct 2015 at 00:49, Rebecca Turner notifications@github.com
wrote:

Reminder to ourselves, I started to work on infrastructure to support
checking for changed git sources here:
https://github.com/npm/git-repo-manager

—
Reply to this email directly or view it on GitHub
#9145 (comment).

[othiym23]

The CLI team really needs to decide what the actual desired behavior around cloning and caching git respositories is, and making that behavior consistent and predictable, testing it thoroughly, and updating the installer documentation to clearly describe how git dependencies are cached. This will probably happen in the first half of 2016 as part of making the npm@3 installer robust.