Install fails

[rudyrockstar]

rudy@uranus:~/nodejs/tm$ npm install

TournamentMango@0.7.0 postinstall /home/nodejs/tm
node ./node_modules/bower/bin/bower install

module.js:538
throw err;
^

Error: Cannot find module 'internal/util/types'
at Function.Module._resolveFilename (module.js:536:15)
at Function.Module._load (module.js:466:25)
at Module.require (module.js:579:17)
at require (internal/module.js:11:18)
at evalmachine.:31:26
at Object. (/home/nodejs/tm/node_modules/bower/node_modules/graceful-fs/fs.js:11:1)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! TournamentMango@0.7.0 postinstall: node ./node_modules/bower/bin/bower install
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the TournamentMango@0.7.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/rudy/.npm/_logs/2017-12-23T17_01_37_478Z-debug.log
rudy@uranus:/nodejs/tm$ ping 49.106.252.222
rudy@uranus:/nodejs/tm$ uname -a
Linux uranus 4.9.0-4-686-pae #1 SMP Debian 4.9.51-1 (2017-09-28) i686 GNU/Linux
rudy@uranus:/nodejs/tm$ npm -version
5.6.0
rudy@uranus:/nodejs/tm$ node -v
v8.9.1

[seiyria]

I'm not sure why Bower is failing. Bower was recently deprecated I think. You could probably rework it so it uses npm instead of Bower and it'd work.

…

On Sat, Dec 23, 2017, 17:08 rudyrockstar ***@***.***> wrote: ***@***.***:~/nodejs/tm$ npm install ***@***.*** postinstall /home/nodejs/tm node ./node_modules/bower/bin/bower install module.js:538 throw err; ^ Error: Cannot find module 'internal/util/types' at Function.Module._resolveFilename (module.js:536:15) at Function.Module._load (module.js:466:25) at Module.require (module.js:579:17) at require (internal/module.js:11:18) at evalmachine.:31:26 at Object. (/home/nodejs/tm/node_modules/bower/node_modules/graceful-fs/fs.js:11:1) at Module._compile (module.js:635:30) at Object.Module._extensions..js (module.js:646:10) at Module.load (module.js:554:32) at tryModuleLoad (module.js:497:12) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! ***@***.*** postinstall: node ./node_modules/bower/bin/bower install npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the ***@***.*** postinstall script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/rudy/.npm/_logs/2017-12-23T17_01_37_478Z-debug.log ***@***.***:/nodejs/tm$ ping 49.106.252.222 ***@***.***:/nodejs/tm$ uname -a Linux uranus 4.9.0-4-686-pae #1 <#1> SMP Debian 4.9.51-1 (2017-09-28) i686 GNU/Linux ***@***.***:/nodejs/tm$ npm -version 5.6.0 ***@***.***:/nodejs/tm$ node -v v8.9.1 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#146>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAum2VglQ_eN6F_KpilV8Y_YpROMzcwxks5tDYf8gaJpZM4RLyL5> .

[rudyrockstar]

Was Bower initially used to accomplish something npm had difficuly with? I will dingle with it tonight.

[seiyria]

It was used way back when, when bower was for frontend and npm was for backend. Way before the times of things like webpack, etc. So, it's mostly irrelevant now, but I haven't worked on this since I failed to monetize it a few years back so here it sits. Good luck.

[makayabou]

Is no one able to commit a fix?
Thanks

[Muirrum]

@makayabou it works with npm 6.9.5, try using NVM? I'm going to make a PR to use yarn as soon as I can verify it all works

[seiyria]

I will not accept a PR to use Yarn.

[Muirrum]

Why not? Bower's been deprecated, and they recommend using yarn.

[seiyria]

I don't care what bower recommends. If anything comes through, I would accept a PR to move all the dependencies to npm.

The problem is that this project is:

• not something I work on
• outdated
• needs a new build pipeline

So if this were to change, it should move to webpack + npm, fixing the build process and having a better dependency lock.