This repository was archived by the owner on Aug 11, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3k
Got different package-lock.json on different machine #19966
Copy link
Copy link
Open
Description
I'm opening this issue because:
- npm is crashing.
- npm is producing an incorrect install.
- npm is doing something I don't understand.
- Other (see below for feature requests):
What's going wrong?
On different machine, npm install produce different package-lock.json.
Here is the diff:
diff --git a/package-lock.json b/package-lock.json
index a66a293..4dba3fe 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -15,12 +15,14 @@
"acorn": {
"version": "5.5.0",
"resolved": "http://registry.npm.taobao.org/acorn/download/acorn-5.5.0.tgz",
- "integrity": "sha1-GrtYf78FH5Tj3iDmsm75ELGCgpg="
+ "integrity": "sha1-GrtYf78FH5Tj3iDmsm75ELGCgpg=",
+ "dev": true
},
"acorn-jsx": {
"version": "3.0.1",
"resolved": "http://registry.npm.taobao.org/acorn-jsx/download/acorn-jsx-3.0.1.tgz",
"integrity": "sha1-r9+UiPsezvyDSPb7IvRk4ypYs2s=",
+ "dev": true,
"requires": {
"acorn": "3.3.0"
},
@@ -28,7 +30,8 @@
"acorn": {
"version": "3.3.0",
"resolved": "http://registry.npm.taobao.org/acorn/download/acorn-3.3.0.tgz",
- "integrity": "sha1-ReN/s56No/JbruP/U2niu18iAXo="
+ "integrity": "sha1-ReN/s56No/JbruP/U2niu18iAXo=",
+ "dev": true
}
}
},
@@ -54,7 +57,8 @@
"ajv-keywords": {
"version": "2.1.1",
"resolved": "http://registry.npm.taobao.org/ajv-keywords/download/ajv-keywords-2.1.1.tgz",
- "integrity": "sha1-YXmX/F9gV2iUxDX5QNgZ4TW4B2I="
+ "integrity": "sha1-YXmX/F9gV2iUxDX5QNgZ4TW4B2I=",
+ "dev": true
},
"align-text": {
"version": "0.1.4",
@@ -179,6 +183,7 @@
"version": "1.0.10",
"resolved": "http://registry.npm.taobao.org/argparse/download/argparse-1.0.10.tgz",
"integrity": "sha1-vNZ5HqWuCXJeF+WtmIE0zUCz2RE=",
+ "dev": true,
"requires": {
"sprintf-js": "1.0.3"
}
@@ -187,6 +192,7 @@
"version": "0.7.1",
"resolved": "http://registry.npm.taobao.org/aria-query/download/aria-query-0.7.1.tgz",
"integrity": "sha1-Jsu1r/ZBRLCoJb4YRuCxbPoAsR4=",
+ "dev": true,
"requires": {
"ast-types-flow": "0.0.7",
"commander": "2.14.1"
@@ -238,6 +244,7 @@
"version": "3.0.3",
"resolved": "http://registry.npm.taobao.org/array-includes/download/array-includes-3.0.3.tgz",
"integrity": "sha1-GEtI9i2S10UrsxsyMWXH+L0CJm0=",
+ "dev": true,
"requires": {
"define-properties": "1.1.2",
"es-abstract": "1.10.0"
@@ -258,6 +265,7 @@
"version": "1.0.2",
"resolved": "http://registry.npm.taobao.org/array-union/download/array-union-1.0.2.tgz",
"integrity": "sha1-mjRBDk9OPaI96jdb5b5w8kd47Dk=",
+ "dev": true,
"requires": {
"array-uniq": "1.0.3"
}
@@ -265,7 +273,8 @@
"array-uniq": {
"version": "1.0.3",
"resolved": "http://registry.npm.taobao.org/array-uniq/download/array-uniq-1.0.3.tgz",
- "integrity": "sha1-r2rId6Jcx/dOBYiUdThY39sk/bY="
+ "integrity": "sha1-r2rId6Jcx/dOBYiUdThY39sk/bY=",
+ "dev": true
},How can the CLI team reproduce the problem?
- Machine A: macOS 10.13.3, Node v8.9.4, npm v5.6.0
- Machine B: Ubuntu 16.04.3, Node v8.9.4, npm v5.6.0
dependencies:
"devDependencies": {
"autoprefixer": "^6.6.1",
"babel-core": "^6.1.2",
"babel-loader": "^6.0.1",
"babel-plugin-antd": "^0.5.1",
"babel-plugin-transform-runtime": "^6.4.3",
"babel-preset-es2015": "^6.1.2",
"babel-preset-react": "^6.1.2",
"babel-runtime": "^6.3.19",
"css-loader": "^0.22.0",
"del": "^2.2.2",
"extract-text-webpack-plugin": "^1.0.1",
"file-loader": "^0.8.4",
"eslint": "^4.16.0",
"eslint-config-airbnb": "^16.1.0",
"eslint-plugin-import": "^2.8.0",
"eslint-plugin-jsx-a11y": "^6.0.3",
"eslint-plugin-react": "^7.6.1",
"gulp": "^3.9.0",
"gulp-changed": "^1.3.0",
"gulp-clean": "^0.3.2",
"gulp-file": "^0.2.0",
"gulp-htmlmin": "^1.2.0",
"gulp-rename": "^1.2.2",
"gulp-replace": "^0.5.4",
"gulp-svg-symbols": "^1.0.0",
"json-loader": "^0.5.3",
"less": "^2.7.3",
"less-loader": "^4.0.5",
"merge-stream": "^1.0.0",
"postcss-loader": "^1.2.2",
"raw-loader": "^0.5.1",
"style-loader": "^0.13.0",
"url-loader": "^0.5.6",
"webpack": "^1.12.3",
"yaml-loader": "^0.4.0"
},
"dependencies": {
"antd": "^3.1.1",
"bytes": "^2.4.0",
"chart.js": "^2.3.0",
"co": "^4.6.0",
"compression": "^1.6.0",
"debug": "^2.6.3",
"ejs": "^2.4.1",
"express": "^4.13.3",
"highlight.js": "^9.9.0",
"http-proxy-middleware": "^0.17.2",
"isomorphic-fetch": "^2.2.1",
"jquery": "^3.1.0",
"js-base64": "^2.1.9",
"lodash": "^4.17.0",
"markdown-it-emoji": "^1.3.0",
"marked": "^0.3.6",
"mime": "^1.3.4",
"moment": "^2.17.1",
"node-uuid": "^1.4.7",
"numeral": "^1.5.3",
"promise": "^7.1.1",
"prop-types": "^15.5.10",
"rainbowlog": "^2.0.1",
"react": "^15.3.0",
"react-dnd": "^2.1.4",
"react-dnd-html5-backend": "^2.1.2",
"react-dom": "^15.3.0",
"react-laser-beam": "^1.3.5",
"react-mixin": "^3.0.5",
"react-redux": "^4.4.5",
"react-router": "^2.6.1",
"redux": "^3.0.4",
"redux-thunk": "^1.0.0",
"request": "^2.73.0",
"semver": "^5.3.0",
"store": "^1.3.17",
"thunkify-wrap": "^1.0.4",
"whatwg-fetch": "^1.0.0"
}
supporting information:
npm -vprints: 5.6.0 (both)node -vprints: v8.9.4 (both)npm config get registryprints: https://registry.npm.taobao.org/ (both)- Windows, OS X/macOS, or Linux?: macOS and Linux
- Network issues:
- Geographic location where npm was run:
- I use a proxy to connect to the npm registry.
- I use a proxy to connect to the web.
- I use a proxy when downloading Git repos.
- I access the npm registry via a VPN
- I don't use a proxy, but have limited or unreliable internet access.
- Container:
- I develop using Vagrant on Windows.
- I develop using Vagrant on OS X or Linux.
- I develop / deploy using Docker.
- I deploy to a PaaS (Triton, Heroku).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels