TannerRogalsky
npm install fails EINTEGRITY
Tried installing love.js node package, with npm install love.js -g but it failed due to integrity checks
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'install',
1 verbose cli 'love.js',
1 verbose cli '-g' ]
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session cf2e20db927b6c72
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 304 https://registry.npmjs.org/love.js 2059ms (from cache)
8 silly pacote tag manifest for love.js@latest fetched in 2107ms
9 silly install loadIdealTree
10 silly install cloneCurrentTreeToIdealTree
11 silly install loadShrinkwrap
12 silly install loadAllDepsIntoIdealTree
13 silly resolveWithNewModule [email protected] checking installable status
14 http fetch GET 304 https://registry.npmjs.org/commander 465ms (from cache)
15 silly pacote range manifest for commander@^2.9.0 fetched in 469ms
16 silly resolveWithNewModule [email protected] checking installable status
17 http fetch GET 304 https://registry.npmjs.org/fs-extra 756ms (from cache)
18 silly pacote range manifest for fs-extra@^3.0.1 fetched in 761ms
19 silly resolveWithNewModule [email protected] checking installable status
20 http fetch GET 304 https://registry.npmjs.org/mustache 780ms (from cache)
21 silly pacote range manifest for mustache@^2.3.0 fetched in 782ms
22 silly resolveWithNewModule [email protected] checking installable status
23 http fetch GET 304 https://registry.npmjs.org/klaw-sync 875ms (from cache)
24 silly pacote range manifest for klaw-sync@^2.1.0 fetched in 877ms
25 silly resolveWithNewModule [email protected] checking installable status
26 http fetch GET 304 https://registry.npmjs.org/uuid 1484ms (from cache)
27 silly pacote range manifest for uuid@^3.0.1 fetched in 1485ms
28 silly resolveWithNewModule [email protected] checking installable status
29 http fetch GET 304 https://registry.npmjs.org/graceful-fs 327ms (from cache)
30 silly pacote range manifest for graceful-fs@^4.1.2 fetched in 334ms
31 silly resolveWithNewModule [email protected] checking installable status
32 http fetch GET 304 https://registry.npmjs.org/universalify 336ms (from cache)
33 silly pacote range manifest for universalify@^0.1.0 fetched in 338ms
34 silly resolveWithNewModule [email protected] checking installable status
35 http fetch GET 304 https://registry.npmjs.org/jsonfile 342ms (from cache)
36 silly pacote range manifest for jsonfile@^3.0.0 fetched in 344ms
37 silly resolveWithNewModule [email protected] checking installable status
38 silly currentTree nodejs
39 silly idealTree nodejs
39 silly idealTree `-- [email protected]
39 silly idealTree +-- [email protected]
39 silly idealTree +-- [email protected]
39 silly idealTree +-- [email protected]
39 silly idealTree +-- [email protected]
39 silly idealTree +-- [email protected]
39 silly idealTree +-- [email protected]
39 silly idealTree +-- [email protected]
39 silly idealTree `-- [email protected]
40 silly install generateActionsToTake
41 silly diffTrees action count 9
42 silly diffTrees add [email protected]
43 silly diffTrees add [email protected]
44 silly diffTrees add [email protected]
45 silly diffTrees add [email protected]
46 silly diffTrees add [email protected]
47 silly diffTrees add [email protected]
48 silly diffTrees add [email protected]
49 silly diffTrees add [email protected]
50 silly diffTrees add [email protected]
51 silly decomposeActions action count 72
52 silly decomposeActions fetch [email protected]
53 silly decomposeActions extract [email protected]
54 silly decomposeActions preinstall [email protected]
55 silly decomposeActions build [email protected]
56 silly decomposeActions install [email protected]
57 silly decomposeActions postinstall [email protected]
58 silly decomposeActions finalize [email protected]
59 silly decomposeActions refresh-package-json [email protected]
60 silly decomposeActions fetch [email protected]
61 silly decomposeActions extract [email protected]
62 silly decomposeActions preinstall [email protected]
63 silly decomposeActions build [email protected]
64 silly decomposeActions install [email protected]
65 silly decomposeActions postinstall [email protected]
66 silly decomposeActions finalize [email protected]
67 silly decomposeActions refresh-package-json [email protected]
68 silly decomposeActions fetch [email protected]
69 silly decomposeActions extract [email protected]
70 silly decomposeActions preinstall [email protected]
71 silly decomposeActions build [email protected]
72 silly decomposeActions install [email protected]
73 silly decomposeActions postinstall [email protected]
74 silly decomposeActions finalize [email protected]
75 silly decomposeActions refresh-package-json [email protected]
76 silly decomposeActions fetch [email protected]
77 silly decomposeActions extract [email protected]
78 silly decomposeActions preinstall [email protected]
79 silly decomposeActions build [email protected]
80 silly decomposeActions install [email protected]
81 silly decomposeActions postinstall [email protected]
82 silly decomposeActions finalize [email protected]
83 silly decomposeActions refresh-package-json [email protected]
84 silly decomposeActions fetch [email protected]
85 silly decomposeActions extract [email protected]
86 silly decomposeActions preinstall [email protected]
87 silly decomposeActions build [email protected]
88 silly decomposeActions install [email protected]
89 silly decomposeActions postinstall [email protected]
90 silly decomposeActions finalize [email protected]
91 silly decomposeActions refresh-package-json [email protected]
92 silly decomposeActions fetch [email protected]
93 silly decomposeActions extract [email protected]
94 silly decomposeActions preinstall [email protected]
95 silly decomposeActions build [email protected]
96 silly decomposeActions install [email protected]
97 silly decomposeActions postinstall [email protected]
98 silly decomposeActions finalize [email protected]
99 silly decomposeActions refresh-package-json [email protected]
100 silly decomposeActions fetch [email protected]
101 silly decomposeActions extract [email protected]
102 silly decomposeActions preinstall [email protected]
103 silly decomposeActions build [email protected]
104 silly decomposeActions install [email protected]
105 silly decomposeActions postinstall [email protected]
106 silly decomposeActions finalize [email protected]
107 silly decomposeActions refresh-package-json [email protected]
108 silly decomposeActions fetch [email protected]
109 silly decomposeActions extract [email protected]
110 silly decomposeActions preinstall [email protected]
111 silly decomposeActions build [email protected]
112 silly decomposeActions install [email protected]
113 silly decomposeActions postinstall [email protected]
114 silly decomposeActions finalize [email protected]
115 silly decomposeActions refresh-package-json [email protected]
116 silly decomposeActions fetch [email protected]
117 silly decomposeActions extract [email protected]
118 silly decomposeActions preinstall [email protected]
119 silly decomposeActions build [email protected]
120 silly decomposeActions install [email protected]
121 silly decomposeActions postinstall [email protected]
122 silly decomposeActions finalize [email protected]
123 silly decomposeActions refresh-package-json [email protected]
124 silly install executeActions
125 silly doSerial global-install 72
126 verbose correctMkdir C:\Users\nano0\AppData\Roaming\npm-cache\_locks correctMkdir not in flight; initializing
127 verbose lock using C:\Users\nano0\AppData\Roaming\npm-cache\_locks\staging-dfd8fbf9c1feea0f.lock for C:\Program Files\nodejs\node_modules\.staging
128 silly doParallel extract 72
129 silly extract [email protected]
130 silly pacote trying graceful-fs@https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.11.tgz by hash: sha1-Dovf5NHduIVNZOBOp8AOKgJuVlg=
131 silly extract [email protected]
132 silly pacote trying jsonfile@https://registry.npmjs.org/jsonfile/-/jsonfile-3.0.0.tgz by hash: sha1-kufHRE5f/V+jLmqa6LhQNN+DR9A=
133 silly extract [email protected]
134 silly pacote trying universalify@https://registry.npmjs.org/universalify/-/universalify-0.1.0.tgz by hash: sha1-nrHEZR3rzGcMyU8adXYjMruWd3g=
135 silly extract [email protected]
136 silly pacote trying commander@https://registry.npmjs.org/commander/-/commander-2.11.0.tgz by hash: sha512-b0553uYA5YAEGgyYIGYROzKQ7X5RAqedkfjiZxwi0kL1g3bOaBNNZfYkzt/CL0umgD5wc9Jec2FbB98CjkMRvQ==
137 silly extract [email protected]
138 silly pacote trying fs-extra@https://registry.npmjs.org/fs-extra/-/fs-extra-3.0.1.tgz by hash: sha1-N5TzeMWLNC6n27sjCVEJxLO2IpE=
139 silly extract [email protected]
140 silly pacote trying klaw-sync@https://registry.npmjs.org/klaw-sync/-/klaw-sync-2.1.0.tgz by hash: sha1-PTvNhgDnv971MjHHOf8FOu1WDkQ=
141 silly extract [email protected]
142 silly pacote trying mustache@https://registry.npmjs.org/mustache/-/mustache-2.3.0.tgz by hash: sha1-QCj3d4sXcIpImTCm5SrDvKDaQdA=
143 silly extract [email protected]
144 silly pacote trying uuid@https://registry.npmjs.org/uuid/-/uuid-3.1.0.tgz by hash: sha512-DIWtzUkw04M4k3bf1IcpS2tngXEL26YUD2M0tMDUpnUrz2hgzUBlD55a4FjdLGPvfHxS6uluGWvaVEqgBcVa+g==
145 silly extract [email protected]
146 silly pacote trying love.js@https://registry.npmjs.org/love.js/-/love.js-0.11.0-rc2.tgz by hash: sha1-ky9QOvGf+uAT5+WpT3F+03OTUvQ=
147 silly pacote data for sha1-ky9QOvGf+uAT5+WpT3F+03OTUvQ= not present. Using manifest.
148 silly pacote universalify@https://registry.npmjs.org/universalify/-/universalify-0.1.0.tgz extracted to C:\Program Files\nodejs\node_modules\.staging\universalify-269ed4e8 by content address 90ms
149 silly pacote klaw-sync@https://registry.npmjs.org/klaw-sync/-/klaw-sync-2.1.0.tgz extracted to C:\Program Files\nodejs\node_modules\.staging\klaw-sync-bab331b3 by content address 101ms
150 silly pacote commander@https://registry.npmjs.org/commander/-/commander-2.11.0.tgz extracted to C:\Program Files\nodejs\node_modules\.staging\commander-a40d8efc by content address 107ms
151 silly pacote jsonfile@https://registry.npmjs.org/jsonfile/-/jsonfile-3.0.0.tgz extracted to C:\Program Files\nodejs\node_modules\.staging\jsonfile-ffa9e856 by content address 118ms
152 silly pacote graceful-fs@https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.11.tgz extracted to C:\Program Files\nodejs\node_modules\.staging\graceful-fs-95606d5d by content address 132ms
153 silly pacote uuid@https://registry.npmjs.org/uuid/-/uuid-3.1.0.tgz extracted to C:\Program Files\nodejs\node_modules\.staging\uuid-6936b99e by content address 161ms
154 silly pacote mustache@https://registry.npmjs.org/mustache/-/mustache-2.3.0.tgz extracted to C:\Program Files\nodejs\node_modules\.staging\mustache-62300005 by content address 165ms
155 silly pacote fs-extra@https://registry.npmjs.org/fs-extra/-/fs-extra-3.0.1.tgz extracted to C:\Program Files\nodejs\node_modules\.staging\fs-extra-e44b534e by content address 268ms
156 verbose unlock done using C:\Users\nano0\AppData\Roaming\npm-cache\_locks\staging-dfd8fbf9c1feea0f.lock for C:\Program Files\nodejs\node_modules\.staging
157 verbose stack Error: sha1-ky9QOvGf+uAT5+WpT3F+03OTUvQ= integrity checksum failed when using sha1: wanted sha1-ky9QOvGf+uAT5+WpT3F+03OTUvQ= but got sha1-bsquo3vpaEGPIIAkBotcbOdA0PA=. (3964553 bytes)
157 verbose stack at Transform.on (C:\Program Files\nodejs\node_modules\npm\node_modules\ssri\index.js:275:19)
157 verbose stack at emitNone (events.js:110:20)
157 verbose stack at Transform.emit (events.js:207:7)
157 verbose stack at endReadableNT (_stream_readable.js:1045:12)
157 verbose stack at _combinedTickCallback (internal/process/next_tick.js:102:11)
157 verbose stack at process._tickCallback (internal/process/next_tick.js:161:9)
158 verbose cwd C:\WINDOWS\system32
159 verbose Windows_NT 10.0.15063
160 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "love.js" "-g"
161 verbose node v8.0.0
162 verbose npm v5.0.4
163 error code EINTEGRITY
164 error sha1-ky9QOvGf+uAT5+WpT3F+03OTUvQ= integrity checksum failed when using sha1: wanted sha1-ky9QOvGf+uAT5+WpT3F+03OTUvQ= but got sha1-bsquo3vpaEGPIIAkBotcbOdA0PA=. (3964553 bytes)
165 verbose exit [ 1, true ]
I suppose this has to do with my internet connection, the file being too big and npm having a bad https request system which drops packages and stuff...
Electron is a package that I have installed successfully many times and is way bigger that love.js so checking how they do it may be a good alternative?
On another note, the name love.js is not Windows friendly, I can't run this package at all since it's looking for a JS file instead... I recommend you rename it to lovejs or something else...
I should remove the debug build from the npm package to make it necessary. I don't think it really adds anything.
As for the windows issue... you sure? On *nix platforms it symlinks the defined entry point to a file named love.js in a standard binary folder (/usr/local/bin for me). What does it even do on windows?
Sorry but since I installed in a weird way (grabbed this source code, and run npm install -g in it) I cannot say that it's this package fault.
First was using PowerShell, second the install command created two files, a no extension bash file and a .cmd file for bat, for normal stuff the .cmd would be used in PowerShell, but since the package is called love.js the files are called love.js and love.js.cmd so PowerShell prefers to run the former with Windows JScript which we all know sucks and fails because it's actually an sh script.
I renamed the files to lovejs and lovejs.cmd and it works with those aliases now.
On another note I'm having problems with packaging folders (No main.lua found)
I've uploaded a new version: 0.11.0-rc3
It's no different except that it doesn't include the debug build so it should be significantly smaller. Perhaps that will help?
I'm testing 0.11.0-rc2 and I can't get anything on screen, I downloaded the latest build of 0.11.0 and it works fine. I'll give you the .love file (which is a modified version of something I found in the forums)
MINESWEEP.zip rename it to .love because GitHub.
I'll test with 0.11.0-rc3 once it installs
Update: You'll need to rename the package if you want it to work on Windows because unfortunately it can't be executed:
The game you posted works great for me in Chrome Canary and Firefox Nightly under OSX.
I'm running Chrome Beta in Windows 10 with no luck, could you upload the game.data file or the entire release build so I can see if I screwed something up or it's just my browser?
Oh will do that... any reason why it doesn't work with beta anymore? I mean, the 0.10.2 version does I believe
Yeah, thread support. Support is poor right now but it will get better.
Right, I see. Well I'll download either later and test, if I also want to test the older version, can I just change the release folder of the npm love.js package with the older one? or do I need to use that python script and clone the entire emscripten thing?
Also I would love you if you can rename love.js npm package to lovejs or I don't know love.js-build something that Stupid Windows doesn't think it's a file extension