Cannot "npm install" - commits do not exist #52

dlsso · 2014-08-11T20:51:15Z

Hi, love what you're doing with voxel and would like to play around with your project.

However, cloning this repo and running npm install results in a page full of errors. This seems to be because packages.json is requesting specific commits that do not exist.

Changing them to latest version breaks the program, so that is not a solution. Any advice on how to get this running locally would be appreciated. Thanks!

kumavis · 2014-08-14T04:16:28Z

@dlsso please include the npm error log

dlsso · 2014-08-14T16:27:05Z

npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-start.git) fatal: bad object a2ec261e772340f8a874869c360d1fd43bd71f04
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-start.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-decorative.git) fatal: bad object c9476268358819442ac4a7ad547e9f608bb5c1ff
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-decorative.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-chest.git) fatal: bad object 02f5d321377ca9a3218f02a10f4eaa2c6c509314
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-chest.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-health-bar.git) fatal: bad object c42fa42b685e67d6f08eb4e0e88a668b681dd531
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-health-bar.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-workbench.git) fatal: bad object aaa3927aaf079d3e26fe045b0fd60fd95e926a35
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-workbench.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-furnace.git) fatal: bad object cfb0b3c400c31ff00bf0b4833cb79a833734a964
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-furnace.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-webview.git) fatal: bad object 1f49c285c32ff2f03cd00316a51fb25a5d97f052
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-webview.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-recipes.git) fatal: bad object ce2fe11c0830f9a1c69db6772b7fc029916effc0
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-recipes.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-bucket.git) fatal: bad object b5f9e750c80732b93d86327559433f6e68d36564
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-bucket.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-carry.git) fatal: bad object a464d4dd24641e938665ecedf5d283e6740f7567
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-carry.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-inventory-hotbar.git) fatal: bad object 5c291a7410962776ae9ba085a22db6f1d305af9a
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-inventory-hotbar.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-blockdata.git) fatal: bad object 1cefa9bb44b64974aec8c9be7b50f2a0d7dc1d56
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-blockdata.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-zen.git) fatal: bad object 17fc631ad5260bcc688fcd787d09dd8a5da2c1b5
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-zen.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-wool.git) fatal: bad object 21638a55ab3821b804dc175127582415e922e85a
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-wool.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-pickaxe.git) fatal: bad object 7f8f5b12ee01f35c42b099ed5455ef63e490d4b6
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-pickaxe.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-gamemode.git) fatal: bad object 47569efaf4ebf76b7ec512c92f5f8af7232b83a2
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-gamemode.git)
npm ERR! Error: Command failed: fatal: bad object a2ec261e772340f8a874869c360d1fd43bd71f04
npm ERR!
npm ERR! at ChildProcess.exithandler (child_process.js:647:15)
npm ERR! at ChildProcess.emit (events.js:98:17)
npm ERR! at maybeClose (child_process.js:755:16)
npm ERR! at Socket. (child_process.js:968:11)
npm ERR! at Socket.emit (events.js:95:17)
npm ERR! at Pipe.close (net.js:465:12)
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/npm/npm/issues

npm ERR! System Darwin 13.3.0
npm ERR! command "node" "/usr/local/bin/npm" "install"
npm ERR! cwd /Users/student/projects/voxpopuli
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! code 128
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/student/projects/voxpopuli/npm-debug.log
npm ERR! not ok code 0

greenlion · 2014-08-19T17:54:05Z

I have the same issue. There are 14 packages with specific commit numbers that don't exist:
[justin@localhost voxpopuli]$ npm install
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-start.git) fatal: bad object a2ec261e772340f8a874869c360d1fd43bd71f04
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-start.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-zen.git) fatal: bad object 17fc631ad5260bcc688fcd787d09dd8a5da2c1b5
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-zen.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-health-bar.git) fatal: bad object c42fa42b685e67d6f08eb4e0e88a668b681dd531
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-health-bar.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-blockdata.git) fatal: bad object 1cefa9bb44b64974aec8c9be7b50f2a0d7dc1d56
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-blockdata.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-bucket.git) fatal: bad object b5f9e750c80732b93d86327559433f6e68d36564
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-bucket.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-inventory-hotbar.git) fatal: bad object 5c291a7410962776ae9ba085a22db6f1d305af9a
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-inventory-hotbar.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-chest.git) fatal: bad object 02f5d321377ca9a3218f02a10f4eaa2c6c509314
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-chest.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-carry.git) fatal: bad object a464d4dd24641e938665ecedf5d283e6740f7567
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-carry.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-webview.git) fatal: bad object 1f49c285c32ff2f03cd00316a51fb25a5d97f052
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-webview.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-recipes.git) fatal: bad object ce2fe11c0830f9a1c69db6772b7fc029916effc0
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-recipes.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-decorative.git) fatal: bad object c9476268358819442ac4a7ad547e9f608bb5c1ff
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-decorative.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-furnace.git) fatal: bad object cfb0b3c400c31ff00bf0b4833cb79a833734a964
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-furnace.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-pickaxe.git) fatal: bad object 7f8f5b12ee01f35c42b099ed5455ef63e490d4b6
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-pickaxe.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-wool.git) fatal: bad object 21638a55ab3821b804dc175127582415e922e85a
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-wool.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-workbench.git) fatal: bad object aaa3927aaf079d3e26fe045b0fd60fd95e926a35
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-workbench.git)
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-gamemode.git) fatal: bad object 47569efaf4ebf76b7ec512c92f5f8af7232b83a2
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-gamemode.git)
npm ERR! Error: Command failed: fatal: bad object a2ec261e772340f8a874869c360d1fd43bd71f04
npm ERR!
npm ERR! at ChildProcess.exithandler (child_process.js:647:15)
npm ERR! at ChildProcess.EventEmitter.emit (events.js:98:17)
npm ERR! at maybeClose (child_process.js:753:16)
npm ERR! at Socket. (child_process.js:966:11)
npm ERR! at Socket.EventEmitter.emit (events.js:95:17)
npm ERR! at Pipe.close (net.js:465:12)
npm ERR! If you need help, you may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! [email protected]

npm ERR! System Linux 3.13.10-200.fc20.x86_64
npm ERR! command "node" "/usr/bin/npm" "install"
npm ERR! cwd /home/justin/voxpopuli
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.3.6
npm ERR! code 128
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/justin/voxpopuli/npm-debug.log
npm ERR! not ok code 0

If I remove the specific commit identifiers , the project no longer works. In the console I get:
"voxpopuli starting" bundle.js:117
TypeError: aabb.base[0] is undefined bundle.js:55738
TypeError: aabb.base is undefined bundle.js:55738

silentrob · 2014-08-27T00:34:05Z

So I ran into the same issue.
Remove all the commits tags from the projects.
Change voxel-engine to use

"voxel-engine": "git://github.com/maxogden/voxel-engine.git#9998d9ea7920c73144913d4e520b99413f2e668d",

Max Ogden ndarray branch (latest)

And remove the voxel-walk plugin. It seems to have issues with AABB, then it works.

jlarsson · 2014-08-28T21:00:08Z

silentrob, I can confirm your effort - check out jlarsson@b859fc9

In addition to your steps, I also had to remove voxel-clientmc due to some soft fs linking to voxel-wireframe that dont work on my windows installation.

Im really happy to get this amazing piece of pure codejoy up and running again :)

silentrob · 2014-08-28T21:26:55Z

👍 I'm also happy to see the code working. I hope development hasn't stalled.

…y, voxel-chest, voxel-clientmc, voxel-decorative, voxel-engine, voxel-furnace, voxel-gamemode, voxel-health-bar, voxel-inventory-hotbar, voxel-land, voxel-pickaxe, voxel-recipes, voxel-start, voxel-webview, voxel-wireframe, voxel-wool, voxel-workbench, voxel-zen voxel/voxel-blockdata@775f10c 0.2.1 voxel/voxel-bucket@c9a3af0 0.0.2 voxel/voxel-carry@a881aa0 0.1.2 voxel/voxel-chest@02587da 0.2.1 voxel/voxel-clientmc@67d38a1 Tweak spawn offset voxel/voxel-clientmc@5ad1c08 Add missing chunk padding. Ref voxel/voxel-clientmc#6 voxel/voxel-clientmc@a25b85b Only load origin chunk, for testing purposes voxel/voxel-clientmc@f5f9f6f Fix chunk load log message arguments voxel/voxel-clientmc@d1b17b1 Add missing voxel-fly plugin voxel/voxel-clientmc@e82fe08 Latest voxel-engine ndarray branch is on github.com/maxogden voxel/voxel-clientmc@30e8b25 Fix voxel-artpacks version voxel/voxel-clientmc@50a707b Set field of view to 90 degrees (vs default 45), match https://github.com/deathcap/voxpopuli voxel/voxel-decorative@9f9b6ae 0.1.1 deathcap/voxel-engine@8202310 Update dependencies deathcap/voxel-engine@9998d9e Update to voxel-registry ^0.8.1 voxel/voxel-furnace@e6407dd 0.1.1 voxel/voxel-gamemode@273fec1 0.2.1 voxel/voxel-health-bar@8e4c4dc 0.1.1 voxel/voxel-inventory-hotbar@a5e6e19 0.4.1 voxel/voxel-land@cb63bf5 0.2.1 voxel/voxel-land@009bbb8 Update dependencies voxel/voxel-land@855127e Remove asm.js-based simplex-noise for faster performance on Firefox voxel/voxel-pickaxe@29f0451 0.2.1 voxel/voxel-recipes@9a58dcb 0.3.1 deathcap/voxel-start@4159811 0.1.1 voxel/voxel-webview@168d73d 0.1.1 voxel/voxel-wireframe@018a589 0.5.1 voxel/voxel-wireframe@f044b4e Fix possible TypeError if no event passed to toggle() (voxel-keys <0.5.0) voxel/voxel-wool@a1824a3 0.1.1 voxel/voxel-workbench@0edf74d 0.2.1 voxel/voxel-zen@313682b 0.1.1 Commit message generated by https://github.com/deathcap/lmno-cl

deathcap · 2014-09-17T04:45:34Z

Sorry for the neglect, just pushed all the missing commits (I think). Still to do:

verify full clean installation from scratch works as expected
possibly remove voxel-clientmc, or node-gyp dependency from minecraft-protocol (dependency minecraft-protocol requires node-gyp, introduces difficulty building on Windows voxel-clientmc#7)
find out what is going on with voxel-walk AABB (not seeing problems myself, but I have it disabled)
long-term, decide how to avoid unpushed commits. tool to check, git url w/o commit-id, or only semver?

kumavis · 2014-09-17T18:15:52Z

@deathcap maybe setup tests with testling, and they will fail if the build fails

max-mapper · 2014-09-20T00:06:27Z

I get a similar error w/ npm install in voxpopuli@master:

$ npm i
npm http GET https://registry.npmjs.org/ever
npm http GET https://registry.npmjs.org/coffeeify
npm http GET https://registry.npmjs.org/beefy
npm http GET https://registry.npmjs.org/browserify
npm http 200 https://registry.npmjs.org/coffeeify
npm http GET https://registry.npmjs.org/coffeeify/-/coffeeify-0.6.0.tgz
npm http 304 https://registry.npmjs.org/ever
npm http 200 https://registry.npmjs.org/beefy
npm http GET https://registry.npmjs.org/beefy/-/beefy-2.0.2.tgz
npm http 200 https://registry.npmjs.org/coffeeify/-/coffeeify-0.6.0.tgz
npm http 200 https://registry.npmjs.org/browserify
npm http GET https://registry.npmjs.org/browserify/-/browserify-5.6.1.tgz
npm http 200 https://registry.npmjs.org/beefy/-/beefy-2.0.2.tgz
npm http 200 https://registry.npmjs.org/browserify/-/browserify-5.6.1.tgz
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-engine.git) fatal: bad object 82023105dab9eccb3aab1c6e81431cf239be4473
npm ERR! Failed resolving git HEAD (git://github.com/deathcap/voxel-engine.git) 
npm ERR! Error: Command failed: fatal: bad object 82023105dab9eccb3aab1c6e81431cf239be4473
npm ERR! 
npm ERR!     at ChildProcess.exithandler (child_process.js:647:15)
npm ERR!     at ChildProcess.EventEmitter.emit (events.js:98:17)
npm ERR!     at maybeClose (child_process.js:753:16)
npm ERR!     at Process.ChildProcess._handle.onexit (child_process.js:820:5)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Darwin 13.3.0
npm ERR! command "node" "/usr/local/bin/npm" "i"
npm ERR! cwd /Users/maxogden/src/js/voxpopuli
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.9
npm ERR! code 128
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/maxogden/src/js/voxpopuli/npm-debug.log
npm ERR! not ok code 0

EndangeredMassa · 2014-09-23T19:02:24Z

I managed to use @jlarsson's fork to get this running, but I also had to set voxel-wool to 0.1.0 to get that working.

Going forward, if you don't want to go with full published versions (especially if you don't have publish access to these modules), it would be awesome if voxpopuli could reference branches on each module. Or, reference master and make changes to each module via Pull Requests that can be more easily reverted if something breaks.

…. Ref GH-52

EndangeredMassa · 2014-09-27T00:41:34Z

An npm install works now, but something else appears to be missing.

Uncaught Error: voxel-gamemode requires game.buttons as kb-bindings (vs kb-controls), cannot add down event listener index.js:25Gamemode index.js:25module.exports index.js:10Plugins.instantiate plugins.js:103(anonymous function) plugins.js:83Plugins.wrapExceptions plugins.js:31Plugins.scanAndInstantiate plugins.js:82Plugins.enable plugins.js:228Plugins.loadAll plugins.js:180Game index.js:171Game index.js:43main index.coffee:63camera-debug index.coffee:3s _prelude.js:1e _prelude.js:1(anonymous function) _prelude.js:1

Uncaught TypeError: Cannot read property '0' of undefined

This should hopefully help with problems like GH-52

Get it at https://github.com/deathcap/voxel-clientmc if you want It worked with MC 1.7(?), kind of, but the player was kicked due to not sending correct position updates. With 1.8 its dependency node-minecraft-protocol is currently being updated. Not yet in a publishable state for the NPM registry, and npm complains if a module is not yet in NPM even if I give it a git URL, so removing it until then. To help ease installation, GH-52 Also a kb-bindings-ui update to fix kb-bindings deprecation warning, deps

deathcap · 2015-02-23T08:30:07Z

Alright I think I finally fixed this. As of d834c77, cloning into a clean directory, npm install: https://gist.github.com/deathcap/b8005637524513fac206

No longer have any commit ids in package.json, using released versions everywhere except for voxel-engine#ndarray, which I'm using a branch reference. Tracking version updates in the repository with npm shrinkwrap instead.

deathcap · 2015-02-23T08:36:15Z

… or not. The npm install succeeds for me but I don't understand why it misses some subdependencies:

[email protected] node_modules/voxel-recipes
└── [email protected] ([email protected], [email protected])

Both https://www.npmjs.com/package/voxel-recipes and node_modules/voxel-recipes/package.json confirm this module also depends on itempile, but it isn't installed, and therefore fails to load in the browser:

Error: Cannot find module 'itempile' from '/private/tmp/voxelmetaverse/node_modules/voxel-recipes'
  at /private/tmp/voxelmetaverse/node_modules/browserify/node_modules/resolve/lib/async.js:46:17
  at process (/private/tmp/voxelmetaverse/node_modules/browserify/node_modules/resolve/lib/async.js:173:43)
  at ondir (/private/tmp/voxelmetaverse/node_modules/browserify/node_modules/resolve/lib/async.js:188:17)
  at load (/private/tmp/voxelmetaverse/node_modules/browserify/node_modules/resolve/lib/async.js:69:43)
  at onex (/private/tmp/voxelmetaverse/node_modules/browserify/node_modules/resolve/lib/async.js:92:31)
  at /private/tmp/voxelmetaverse/node_modules/browserify/node_modules/resolve/lib/async.js:22:47
  at FSReqWrap.oncomplete (fs.js:99:15)

node_modules clocking in a 360 MB.. would hope it includes everything :/

deathcap · 2015-02-23T08:47:40Z

The problem seems to be npm-shrinkwrap.json. If I delete it, then npm install, everything is included. If I rerun npm shrinkwrap on the new install then it generates the correct module hierarchy, but it doesn't on my usual development directory, I guess shrinkwrap is ignoring npm link'd modules (intentional?). If this interaction between npm link and npm shrinkwrap cannot be worked around I'll have to rethink my workflow… (all I want to do is track all the deps & subdeps & subsubdeps … so I know what changed. possible?)

Anyways I added a complete shrinkwrap from a new install, I believe this should work now, if anyone wants to retest

greenlion · 2015-02-23T15:27:06Z

I will try to test in the next couple days. Thanks for the update!

Sent from my iPhone

On Feb 23, 2015, at 1:47 AM, deathcap [email protected] wrote:

The problem seems to be npm-shrinkwrap.json. If I delete it, then npm install, everything is included. If I rerun npm shrinkwrap on the new install then it generates the correct module hierarchy, but it doesn't on my usual development directory, I guess shrinkwrap is ignoring npm link'd modules (intentional?). If this interaction between npm link and npm shrinkwrap cannot be worked around I'll have to rethink my workflow… (all I want to do is track all the deps & subdeps & subsubdeps … so I know what changed. possible?)

Anyways I added a complete shrinkwrap from a new install, I believe this should work now, if anyone wants to retest

—
Reply to this email directly or view it on GitHub.

deathcap · 2015-12-30T04:22:13Z

Testing from node v5.3.0 (GH-61), clean checkout, fails now but with a different error:

npm ERR! fetch failed https://registry.npmjs.org/esprima-six/-/esprima-six-0.0.3.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
npm ERR! fetch failed https://registry.npmjs.org/esprima-six/-/esprima-six-0.0.3.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
npm WARN deprecated [email protected]: Use ndarray-resample instead!

which is #60 nonexistent dependency

z3t0 · 2015-12-30T05:05:27Z

@deathcap glslify needs to be updated for most to fix...
Also need to add gl-shader as that is no longer a part of glslify2+, also means a small syntactical change in the shader..

deathcap · 2015-12-30T06:06:14Z

@z3t0 yah found https://github.com/stackgl/glslify#migrating-from-glslify1-to-glslify2, migrating in #60

Another issue: voxel-console 0.2.2 not found, I have no record of any 0.2.2 anywhere (latest is 0.2.1 even on my local systems); republished 0.2.1 as 0.2.2 in voxel/voxel-console@56ecaa1 - am now able to npm install after npm linking voxel-decals, voxel-engine-stackgl, voxel-webview for GH-60 fixes - to retest after GH-60 published

deathcap · 2015-12-30T10:04:54Z

Testing on 0879167, a couple warnings (+ new issues):

$ npm install
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"5.3.0","npm":"3.3.12"}) (voxel/voxel-stitch#10)
npm WARN deprecated [email protected]: Use ndarray-resample instead! (voxel/rect-mip-map#2)
npm WARN engine [email protected]: wanted: {"node":"0.12.x"} (current: {"node":"5.3.0","npm":"3.3.12"}) (kumavis/browserify-commit-sha#5)
npm WARN prefer global [email protected] should be installed with -g (?)

but it installs with no errors (full npm list output: https://gist.github.com/deathcap/218eafd20e8542b37598), and http://localhost:8080/ is functional

dlsso changed the title ~~Cannot "npm install" commits do not exist~~ Cannot "npm install" - commits do not exist Aug 11, 2014

deathcap mentioned this issue Sep 17, 2014

dependency minecraft-protocol requires node-gyp, introduces difficulty building on Windows voxel/voxel-clientmc#7

Closed

deathcap added a commit that referenced this issue Sep 17, 2014

Remove voxel-walk (disabled) due to AABB incompatibility. Ref GH-52

3602d5f

deathcap added a commit that referenced this issue Sep 24, 2014

Update dependencies to use versions instead of commits where possible…

9742e57

…. Ref GH-52

deathcap added a commit that referenced this issue Feb 23, 2015

Use branch references instead of commit ids in unreleased dependencies

e74e8e1

This should hopefully help with problems like GH-52

deathcap added a commit that referenced this issue Feb 23, 2015

Add complete npm shrinkwrap. Ref GH-52

9c734dc

deathcap mentioned this issue Dec 30, 2015

Update to node v5.3.0, browserify v12.0.1 #61

Closed

deathcap closed this as completed Dec 30, 2015

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Cannot "npm install" - commits do not exist #52

Cannot "npm install" - commits do not exist #52

dlsso commented Aug 11, 2014

kumavis commented Aug 14, 2014

dlsso commented Aug 14, 2014

greenlion commented Aug 19, 2014

silentrob commented Aug 27, 2014

jlarsson commented Aug 28, 2014

silentrob commented Aug 28, 2014

deathcap commented Sep 17, 2014

kumavis commented Sep 17, 2014

max-mapper commented Sep 20, 2014

EndangeredMassa commented Sep 23, 2014

EndangeredMassa commented Sep 27, 2014

deathcap commented Feb 23, 2015

deathcap commented Feb 23, 2015

deathcap commented Feb 23, 2015

greenlion commented Feb 23, 2015

deathcap commented Dec 30, 2015

z3t0 commented Dec 30, 2015

deathcap commented Dec 30, 2015

deathcap commented Dec 30, 2015

Cannot "npm install" - commits do not exist #52

Cannot "npm install" - commits do not exist #52

Comments

dlsso commented Aug 11, 2014

kumavis commented Aug 14, 2014

dlsso commented Aug 14, 2014

greenlion commented Aug 19, 2014

silentrob commented Aug 27, 2014

jlarsson commented Aug 28, 2014

silentrob commented Aug 28, 2014

deathcap commented Sep 17, 2014

kumavis commented Sep 17, 2014

max-mapper commented Sep 20, 2014

EndangeredMassa commented Sep 23, 2014

EndangeredMassa commented Sep 27, 2014

deathcap commented Feb 23, 2015

deathcap commented Feb 23, 2015

deathcap commented Feb 23, 2015

greenlion commented Feb 23, 2015

deathcap commented Dec 30, 2015

z3t0 commented Dec 30, 2015

deathcap commented Dec 30, 2015

deathcap commented Dec 30, 2015