Npm 当相关包保持不变时,package.lock文件要求部分为什么会更改?
这项Npm 当相关包保持不变时,package.lock文件要求部分为什么会更改?,npm,dependencies,semantic-versioning,package-lock.json,Npm,Dependencies,Semantic Versioning,Package Lock.json,这项包锁.json更改如何可能: 之前: ... "chokidar": { "version": "1.7.0", "resolved": "https://registry.npmjs.org/chokidar/-/chokidar-1.7.0.tgz", "integrity": "sha1-eY5ol3gVHIB2tLNg5e3SjNortGg=", "requires": { "anymatch": "1.3.2"
包锁.json
更改如何可能:
之前:
...
"chokidar": {
"version": "1.7.0",
"resolved": "https://registry.npmjs.org/chokidar/-/chokidar-1.7.0.tgz",
"integrity": "sha1-eY5ol3gVHIB2tLNg5e3SjNortGg=",
"requires": {
"anymatch": "1.3.2",
"async-each": "1.0.3",
"glob-parent": "2.0.0",
"inherits": "2.0.4",
"is-binary-path": "1.0.1",
"is-glob": "2.0.1",
"path-is-absolute": "1.0.1",
"readdirp": "2.2.1"
}
},
...
之后:
...
"chokidar": {
"version": "1.7.0",
"resolved": "https://registry.npmjs.org/chokidar/-/chokidar-1.7.0.tgz",
"integrity": "sha1-eY5ol3gVHIB2tLNg5e3SjNortGg=",
"requires": {
"anymatch": "^1.3.0",
"async-each": "^1.0.0",
"fsevents": "^1.0.0",
"glob-parent": "^2.0.0",
"inherits": "^2.0.1",
"is-binary-path": "^1.0.0",
"is-glob": "^2.0.0",
"path-is-absolute": "^1.0.0",
"readdirp": "^2.0.0"
}
},
...
这发生在docker容器中,所以平台不是问题。完整性字段匹配——所以是WTF。所需版本更改(可能是npm审计
),但fsevents作为一项要求是新的,而包没有更改。
有人能给我一个线索吗?你确定你有正确的前后顺序吗?是的。。我检查过很多次了。。另外--请注意,即使我用了错误的方法--解析的url是相同的,完整性指纹是相同的,但是,要求是非常不同的。NPM的版本改变了吗?没有。。此后,npm版本发生了变化,但这两个
包锁文件的npm版本相同。即使是不同的——对于同一版本的依赖项,突然出现的需求仍然没有意义。您应该提交一个bug: