max-mapper / max-mapper/voxel-builder

Install failed

Open
#20 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
150
Forks
50
PR merge metrics
No merged PRs in 30d

Description

Running on CentOS and I got this at the end of the npm install, which of course gave errors when I tried npm start.

ndarray@1.0.15 node_modules/ndarray
└── iota-array@1.0.0

orthogami@1.1.0 node_modules/orthogami
├── signum@1.0.0
├── contour-2d@1.0.0
├── boxpack@0.1.0
├── interval-tree-1d@1.0.0 (binary-search-bounds@1.0.0)
└── ndarray-ops@1.2.2 (cwise-compiler@1.0.0)

ndarray-stl@1.0.1 node_modules/ndarray-stl
├── normals@0.1.0
├── isosurface@0.1.0
└── ao-mesher@0.2.10 (cwise-compiler@0.1.0, typedarray-pool@0.1.2, greedy-mesher@1.0.2)

voxel-critter@1.0.0 node_modules/voxel-critter
├── voxel-mesh@0.2.1
├── inherits@2.0.1
├── voxel-creature@0.1.0 (inherits@1.0.0)
├── get-pixels@1.1.0 (node-bitmap@0.0.1, through@2.3.4, omggif@1.0.5, ppm@0.0.0, ndarray-pack@1.1.1, jpeg-js@0.0.3, pngparse@1.1.4)
├── voxel-engine@0.20.1 (voxel-view@0.0.6, inherits@1.0.0, pin-it@0.0.1, collide-3d-tilemap@0.0.1, spatial-trigger@0.0.0, aabb-3d@0.0.0, voxel-physical@0.0.10, voxel-control@0.0.7, tic@0.2.1, spatial-events@0.0.1, voxel-region-change@0.1.0, voxel-raycast@0.2.1, voxel-texture@0.5.6, kb-controls@0.0.2, gl-matrix@2.0.0, three@0.56.0, interact@0.0.2)
└── voxel@0.3.1 (inherits@1.0.0)

voxel-2d-print@1.0.0 node_modules/voxel-2d-print
├── contour-2d@1.0.0
├── atlaspack@0.2.7
├── color@0.4.4 (color-string@0.1.3, color-convert@0.2.1)
├── save-pixels@1.0.0 (through@2.3.4, pngjs@0.4.0)
├── ndarray-fill@0.1.0 (cwise@0.3.4)
└── voxel-critter@0.1.2 (voxel-mesh@0.2.1, inherits@2.0.1, voxel-creature@0.1.0, voxel-engine@0.20.1, voxel@0.3.1)

ndarray-fill@1.0.1 node_modules/ndarray-fill
└── cwise@1.0.4 (cwise-compiler@1.0.0, uglify-js@2.4.13, cwise-parser@1.0.0, static-module@1.0.0)

beefy@0.0.11 node_modules/beefy
├── response-stream@0.0.0
├── through@2.2.7
├── colors@0.6.2
├── filed@0.0.7
├── optimist@0.3.7 (wordwrap@0.0.2)
└── live-reload@0.2.0 (hound@1.0.4, watchr@2.1.6, shoe@0.0.5, reconnect@0.1.5, browserify-server@2.0.4)
[root@coursesaver cubecounting]# npm start

> voxel-painter@0.0.1 start /var/www/html/quizzes/cubecounting
> beefy demo.js:bundle.js 8080

listening on 8080
using browserify

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: listen EADDRINUSE
  at errnoException (net.js:904:11)
  at Server._listen2 (net.js:1042:14)
  at listen (net.js:1064:10)
  at Server.listen (net.js:1138:5)
  at Object.<anonymous> (/var/www/html/quizzes/cubecounting/node_modules/beefy/index.js:118:4)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (module.js:356:32)
  at Function.Module._load (module.js:312:12)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at Object.<anonymous> (/var/www/html/quizzes/cubecounting/node_modules/beefy/bin/beefy:2:1)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (module.js:356:32)
  at Function.Module._load (module.js:312:12)
  at Function.Module.runMain (module.js:497:10)
  at startup (node.js:119:16)
  at node.js:906:3

npm ERR! weird error 8
npm ERR! not ok code 0

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the npm start command shown in the report and inspect the beefy invocation, especially node_modules/beefy/index.js:118, where the EADDRINUSE trace points. Reproduce the failure after npm install; the issue does not state what repository change or expected behavior would constitute done, so that scope needs maintainer clarification.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.