package-lock.json

问题 If two different developers are using different versions of node (12/15) & npm (6/7) in a project that was originally created using a package-lock.json "lockfileVersion": 1 , when the developer using npm 7x installs new packages it seems that the package-lock.json is re-created using "lockfileVersion": 2 . This seems to cause issues for the developer using npm v6, as it tries to work with the lockfileVersion 2 , but it ends up producing new diffs. npm WARN read-shrinkwrap This version of npm

问题 If two different developers are using different versions of node (12/15) & npm (6/7) in a project that was originally created using a package-lock.json "lockfileVersion": 1 , when the developer using npm 7x installs new packages it seems that the package-lock.json is re-created using "lockfileVersion": 2 . This seems to cause issues for the developer using npm v6, as it tries to work with the lockfileVersion 2 , but it ends up producing new diffs. npm WARN read-shrinkwrap This version of npm

问题 There are a lot of people online asking this same question in different ways but there is no clear answer. Can anybody understand enough to explain why a docker build fails when package-lock.json file exists in the application, but runs successfully when it is not? Seemingly it is related to npm but it is not clear. Everybody says delete the package-lock.json , but it is there for a reason. Note: npm install works fine on my local machine, just fails in docker container. If I have this

问题 Here is the relevant part of my package.json file: "devDependencies": { "ajv": "^6.0.0", "webpack": "^4.0.0", "websocket": "^1.0.0", "bignumber.js": "^7.0.0", "decimal.js": "^10.0.0", "truffle": "4.1.11", "ganache-cli": "6.1.0", "solidity-coverage": "0.5.4", "ethereumjs-testrpc-sc": "6.1.2", "web3": "1.0.0-beta.34" } I have this file in two different repositories, on the same PC. When I run npm install in each one of these repositories at the same time, I get a different package-lock.json

问题 Here is the relevant part of my package.json file: "devDependencies": { "ajv": "^6.0.0", "webpack": "^4.0.0", "websocket": "^1.0.0", "bignumber.js": "^7.0.0", "decimal.js": "^10.0.0", "truffle": "4.1.11", "ganache-cli": "6.1.0", "solidity-coverage": "0.5.4", "ethereumjs-testrpc-sc": "6.1.2", "web3": "1.0.0-beta.34" } I have this file in two different repositories, on the same PC. When I run npm install in each one of these repositories at the same time, I get a different package-lock.json

问题 Here is the relevant part of my package.json file: "devDependencies": { "ajv": "^6.0.0", "webpack": "^4.0.0", "websocket": "^1.0.0", "bignumber.js": "^7.0.0", "decimal.js": "^10.0.0", "truffle": "4.1.11", "ganache-cli": "6.1.0", "solidity-coverage": "0.5.4", "ethereumjs-testrpc-sc": "6.1.2", "web3": "1.0.0-beta.34" } I have this file in two different repositories, on the same PC. When I run npm install in each one of these repositories at the same time, I get a different package-lock.json

问题 In package-lock.json in dependency object, I have both requires and dependencies fields, e.g "requires": { "@angular-devkit/core": "0.8.5", "rxjs": "6.2.2", "tree-kill": "1.2.0", "webpack-sources": "1.3.0" }, "dependencies": { "rxjs": { "version": "6.2.2", "resolved": "https://registry.npmjs.org/rxjs/-/rxjs-6.2.2.tgz", "integrity": "sha512-0MI8+mkKAXZUF9vMrEoPnaoHkfzBPP4IGwUYRJhIRJF6/w3uByO1e91bEHn8zd43RdkTMKiooYKmwz7RH6zfOQ==", "dev": true, "requires": { "tslib": "1.9.3" } } } What is the

问题 In package-lock.json in dependency object, I have both requires and dependencies fields, e.g "requires": { "@angular-devkit/core": "0.8.5", "rxjs": "6.2.2", "tree-kill": "1.2.0", "webpack-sources": "1.3.0" }, "dependencies": { "rxjs": { "version": "6.2.2", "resolved": "https://registry.npmjs.org/rxjs/-/rxjs-6.2.2.tgz", "integrity": "sha512-0MI8+mkKAXZUF9vMrEoPnaoHkfzBPP4IGwUYRJhIRJF6/w3uByO1e91bEHn8zd43RdkTMKiooYKmwz7RH6zfOQ==", "dev": true, "requires": { "tslib": "1.9.3" } } } What is the

问题 I deleted it by accident and have made many changes to package.json since. An npm install or npm update do not generate package-lock.json anymore. I tried clearing my npm cache and my nvm cache, but nothing seems to be working. I tried it on several versions of Node.js (6.10.3 Node.js - 3.10.10 npm is what I would like it to work on), and it doesn't work on any. Is there a way to force npm to generate the package-lock.json file? 回答1: By default, package-lock.json is updated whenever you run

问题 I deleted it by accident and have made many changes to package.json since. An npm install or npm update do not generate package-lock.json anymore. I tried clearing my npm cache and my nvm cache, but nothing seems to be working. I tried it on several versions of Node.js (6.10.3 Node.js - 3.10.10 npm is what I would like it to work on), and it doesn't work on any. Is there a way to force npm to generate the package-lock.json file? 回答1: By default, package-lock.json is updated whenever you run