starred/peerflix-server
1
0
Fork 0
mirror of https://github.com/asapach/peerflix-server.git synced 2026-04-25 14:45:50 +03:00
Code Issues 88 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #94] npm coughs and rolls over. #80

New issue
Closed
opened 2026-02-25 20:32:21 +03:00 by kerem · 2 comments
kerem commented 2026-02-25 20:32:21 +03:00
Owner
Copy link

Originally created by @varunchopra on GitHub (Dec 29, 2016).
Original GitHub issue: https://github.com/asapach/peerflix-server/issues/94

Ran this on a clean Debian install.

root@v0rt3x:~# npm install -g peerflix-server
npm WARN engine peerflix-server@0.1.1: wanted: {"node":">=0.12"} (current: {"node":"0.10.29","npm":"1.4.21"})
npm WARN deprecated bittorrent-dht@3.2.6: Critical security issue fixed in 5.1.3. All users should upgrade. (More info: https://github.com/feross/bittorrent-dht/issues/87)
npm WARN deprecated static-favicon@1.0.2: use serve-favicon module
npm WARN deprecated node-uuid@1.4.7: use uuid module instead
npm WARN engine hawk@0.10.2: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"})
npm WARN engine boom@0.3.8: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"})
npm WARN engine cryptiles@0.1.3: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"})
npm WARN engine hoek@0.7.6: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"})
npm WARN engine sntp@0.1.4: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"})
/usr/local/bin/peerflix-server -> /usr/local/lib/node_modules/peerflix-server/server/bin.js
peerflix-server@0.1.1 /usr/local/lib/node_modules/peerflix-server
├── range-parser@1.2.0
├── pump@1.0.2 (once@1.4.0, end-of-stream@1.1.0)
├── mkdirp@0.5.1 (minimist@0.0.8)
├── connect-multiparty@1.2.5 (on-finished@2.1.1, qs@2.2.5, type-is@1.5.7, multiparty@3.3.2)
├── lodash@2.4.2
├── read-torrent@1.3.0 (xtend@4.0.1, magnet-uri@2.0.1, request@2.16.6, parse-torrent@4.1.0)
├── socket.io@1.7.2 (object-assign@4.1.0, socket.io-adapter@0.5.0, has-binary@0.1.7, debug@2.3.3, socket.io-parser@2.3.1, engine.io@1.8.2, socket.io-client@1.7.2)
├── torrent-stream@0.18.1 (bitfield@0.1.0, thunky@0.1.0, hat@0.0.3, random-access-file@0.3.2, ip@0.3.3, mkdirp@0.3.5, magnet-uri@2.0.1, end-of-stream@0.1.5, ip-set@1.0.1, bncode@0.5.3, compact2string@1.4.0, bittorrent-dht@3.2.6, rimraf@2.5.4, peer-wire-swarm@0.9.2, bittorrent-tracker@2.12.1, parse-torrent@4.1.0)
├── express@3.5.3 (methods@0.1.0, merge-descriptors@0.0.2, cookie@0.1.2, debug@0.8.1, cookie-signature@1.0.3, fresh@0.2.2, range-parser@1.0.0, buffer-crc32@0.2.1, mkdirp@0.4.0, commander@1.3.2, send@0.3.0, connect@2.14.5)
└── fluent-ffmpeg@2.1.0 (which@1.2.12, async@2.1.4)
root@v0rt3x:~# peerflix-server
/usr/bin/env: node: No such file or directory
Originally created by @varunchopra on GitHub (Dec 29, 2016). Original GitHub issue: https://github.com/asapach/peerflix-server/issues/94 Ran this on a clean Debian install. ``` root@v0rt3x:~# npm install -g peerflix-server npm WARN engine peerflix-server@0.1.1: wanted: {"node":">=0.12"} (current: {"node":"0.10.29","npm":"1.4.21"}) npm WARN deprecated bittorrent-dht@3.2.6: Critical security issue fixed in 5.1.3. All users should upgrade. (More info: https://github.com/feross/bittorrent-dht/issues/87) npm WARN deprecated static-favicon@1.0.2: use serve-favicon module npm WARN deprecated node-uuid@1.4.7: use uuid module instead npm WARN engine hawk@0.10.2: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"}) npm WARN engine boom@0.3.8: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"}) npm WARN engine cryptiles@0.1.3: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"}) npm WARN engine hoek@0.7.6: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"}) npm WARN engine sntp@0.1.4: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"}) /usr/local/bin/peerflix-server -> /usr/local/lib/node_modules/peerflix-server/server/bin.js peerflix-server@0.1.1 /usr/local/lib/node_modules/peerflix-server ├── range-parser@1.2.0 ├── pump@1.0.2 (once@1.4.0, end-of-stream@1.1.0) ├── mkdirp@0.5.1 (minimist@0.0.8) ├── connect-multiparty@1.2.5 (on-finished@2.1.1, qs@2.2.5, type-is@1.5.7, multiparty@3.3.2) ├── lodash@2.4.2 ├── read-torrent@1.3.0 (xtend@4.0.1, magnet-uri@2.0.1, request@2.16.6, parse-torrent@4.1.0) ├── socket.io@1.7.2 (object-assign@4.1.0, socket.io-adapter@0.5.0, has-binary@0.1.7, debug@2.3.3, socket.io-parser@2.3.1, engine.io@1.8.2, socket.io-client@1.7.2) ├── torrent-stream@0.18.1 (bitfield@0.1.0, thunky@0.1.0, hat@0.0.3, random-access-file@0.3.2, ip@0.3.3, mkdirp@0.3.5, magnet-uri@2.0.1, end-of-stream@0.1.5, ip-set@1.0.1, bncode@0.5.3, compact2string@1.4.0, bittorrent-dht@3.2.6, rimraf@2.5.4, peer-wire-swarm@0.9.2, bittorrent-tracker@2.12.1, parse-torrent@4.1.0) ├── express@3.5.3 (methods@0.1.0, merge-descriptors@0.0.2, cookie@0.1.2, debug@0.8.1, cookie-signature@1.0.3, fresh@0.2.2, range-parser@1.0.0, buffer-crc32@0.2.1, mkdirp@0.4.0, commander@1.3.2, send@0.3.0, connect@2.14.5) └── fluent-ffmpeg@2.1.0 (which@1.2.12, async@2.1.4) root@v0rt3x:~# peerflix-server /usr/bin/env: node: No such file or directory ```
kerem closed this issue 2026-02-25 20:32:21 +03:00
kerem commented 2026-02-25 20:32:22 +03:00
Author
Owner
Copy link

@asapach commented on GitHub (Dec 29, 2016):

I think Debian and Ubuntu don't like node binary, because there's a conflicting package and instead use nodejs. You should either install nodejs-legacy or PPA: https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions or

<!-- gh-comment-id:269701271 --> @asapach commented on GitHub (Dec 29, 2016): I think Debian and Ubuntu don't like `node` binary, because there's a [conflicting package](https://packages.debian.org/jessie/node) and instead use [`nodejs`](https://packages.debian.org/jessie/nodejs). You should either install [`nodejs-legacy`](https://packages.debian.org/jessie/nodejs-legacy) or PPA: https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions or
kerem commented 2026-02-25 20:32:22 +03:00
Author
Owner
Copy link

@varunchopra commented on GitHub (Dec 29, 2016):

Coughed but didn't roll over this time.

root@v0rt3x:~# npm install -g peerflix-server
npm WARN engine peerflix-server@0.1.1: wanted: {"node":">=0.12"} (current: {"node":"0.10.29","npm":"1.4.21"})
npm WARN deprecated bittorrent-dht@3.2.6: Critical security issue fixed in 5.1.3. All users should upgrade. (More info: https://github.com/feross/bittorrent-dht/issues/87)
npm WARN deprecated static-favicon@1.0.2: use serve-favicon module
npm WARN deprecated node-uuid@1.4.7: use uuid module instead
npm WARN engine hawk@0.10.2: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"})
npm WARN engine hoek@0.7.6: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"})
npm WARN engine boom@0.3.8: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"})
npm WARN engine sntp@0.1.4: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"})
npm WARN engine cryptiles@0.1.3: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"})
/usr/local/bin/peerflix-server -> /usr/local/lib/node_modules/peerflix-server/server/bin.js
peerflix-server@0.1.1 /usr/local/lib/node_modules/peerflix-server
├── range-parser@1.2.0
├── mkdirp@0.5.1 (minimist@0.0.8)
├── pump@1.0.2 (once@1.4.0, end-of-stream@1.1.0)
├── connect-multiparty@1.2.5 (on-finished@2.1.1, qs@2.2.5, type-is@1.5.7, multiparty@3.3.2)
├── lodash@2.4.2
├── read-torrent@1.3.0 (xtend@4.0.1, magnet-uri@2.0.1, request@2.16.6, parse-torrent@4.1.0)
├── socket.io@1.7.2 (object-assign@4.1.0, socket.io-adapter@0.5.0, has-binary@0.1.7, debug@2.3.3, socket.io-parser@2.3.1, engine.io@1.8.2, socket.io-client@1.7.2)
├── torrent-stream@0.18.1 (bitfield@0.1.0, thunky@0.1.0, hat@0.0.3, random-access-file@0.3.2, ip@0.3.3, mkdirp@0.3.5, magnet-uri@2.0.1, end-of-stream@0.1.5, ip-set@1.0.1, bncode@0.5.3, compact2string@1.4.0, bittorrent-dht@3.2.6, rimraf@2.5.4, peer-wire-swarm@0.9.2, bittorrent-tracker@2.12.1, parse-torrent@4.1.0)
├── express@3.5.3 (methods@0.1.0, merge-descriptors@0.0.2, cookie@0.1.2, debug@0.8.1, cookie-signature@1.0.3, fresh@0.2.2, range-parser@1.0.0, buffer-crc32@0.2.1, mkdirp@0.4.0, commander@1.3.2, send@0.3.0, connect@2.14.5)
└── fluent-ffmpeg@2.1.0 (which@1.2.12, async@2.1.4)
root@v0rt3x:~# peerflix-server
Listening on http://localhost:9000

Even though it's working, I'd rather have a clean setup.

<!-- gh-comment-id:269702663 --> @varunchopra commented on GitHub (Dec 29, 2016): Coughed but didn't roll over this time. ``` root@v0rt3x:~# npm install -g peerflix-server npm WARN engine peerflix-server@0.1.1: wanted: {"node":">=0.12"} (current: {"node":"0.10.29","npm":"1.4.21"}) npm WARN deprecated bittorrent-dht@3.2.6: Critical security issue fixed in 5.1.3. All users should upgrade. (More info: https://github.com/feross/bittorrent-dht/issues/87) npm WARN deprecated static-favicon@1.0.2: use serve-favicon module npm WARN deprecated node-uuid@1.4.7: use uuid module instead npm WARN engine hawk@0.10.2: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"}) npm WARN engine hoek@0.7.6: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"}) npm WARN engine boom@0.3.8: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"}) npm WARN engine sntp@0.1.4: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"}) npm WARN engine cryptiles@0.1.3: wanted: {"node":"0.8.x"} (current: {"node":"0.10.29","npm":"1.4.21"}) /usr/local/bin/peerflix-server -> /usr/local/lib/node_modules/peerflix-server/server/bin.js peerflix-server@0.1.1 /usr/local/lib/node_modules/peerflix-server ├── range-parser@1.2.0 ├── mkdirp@0.5.1 (minimist@0.0.8) ├── pump@1.0.2 (once@1.4.0, end-of-stream@1.1.0) ├── connect-multiparty@1.2.5 (on-finished@2.1.1, qs@2.2.5, type-is@1.5.7, multiparty@3.3.2) ├── lodash@2.4.2 ├── read-torrent@1.3.0 (xtend@4.0.1, magnet-uri@2.0.1, request@2.16.6, parse-torrent@4.1.0) ├── socket.io@1.7.2 (object-assign@4.1.0, socket.io-adapter@0.5.0, has-binary@0.1.7, debug@2.3.3, socket.io-parser@2.3.1, engine.io@1.8.2, socket.io-client@1.7.2) ├── torrent-stream@0.18.1 (bitfield@0.1.0, thunky@0.1.0, hat@0.0.3, random-access-file@0.3.2, ip@0.3.3, mkdirp@0.3.5, magnet-uri@2.0.1, end-of-stream@0.1.5, ip-set@1.0.1, bncode@0.5.3, compact2string@1.4.0, bittorrent-dht@3.2.6, rimraf@2.5.4, peer-wire-swarm@0.9.2, bittorrent-tracker@2.12.1, parse-torrent@4.1.0) ├── express@3.5.3 (methods@0.1.0, merge-descriptors@0.0.2, cookie@0.1.2, debug@0.8.1, cookie-signature@1.0.3, fresh@0.2.2, range-parser@1.0.0, buffer-crc32@0.2.1, mkdirp@0.4.0, commander@1.3.2, send@0.3.0, connect@2.14.5) └── fluent-ffmpeg@2.1.0 (which@1.2.12, async@2.1.4) root@v0rt3x:~# peerflix-server Listening on http://localhost:9000 ``` Even though it's working, I'd rather have a clean setup.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
dependabot/npm_and_yarn/decode-uri-component-0.2.2
dependabot/npm_and_yarn/minimatch-and-grunt-and-grunt-contrib-jshint-and-grunt-contrib-watch-and-grunt-wiredep-and-load-grunt-tasks-3.0.4
dependabot/npm_and_yarn/socket.io-parser-and-karma-3.4.1
dependabot/npm_and_yarn/grunt-1.5.3
dependabot/npm_and_yarn/ajv-6.12.6
v0.6.0
v0.5.1
v0.5.0
v0.4.2
v0.4.1
v0.4.0
v0.3.1
v0.3.0
v0.2.0
v0.1.3
v0.1.2
v0.1.1
v0.1.0
v0.0.30
v0.0.29
v0.0.28
v0.0.27
v0.0.26
v0.0.25
v0.0.24
v0.0.23
v0.0.22
v0.0.21
v0.0.20
v0.0.19
v0.0.18
v0.0.17
v0.0.16
v0.0.15
v0.0.14
v0.0.13
v0.0.12
v0.0.11
v0.0.10
v0.0.9
v0.0.8
0.0.7
0.0.6
0.0.5
0.0.4
0.0.3
0.0.2
Labels
Clear labels   
bug

   
duplicate

   
enhancement

   
invalid

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
tip

   
wontfix
No labels
bug
duplicate
enhancement
invalid
pull-request
question
tip
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/peerflix-server#80
No description provided.