Nothing showing up in browser when i start the application

[vaMuchenje]

I installed gulp using:

npm install gulp -g

I already had npm installed.

I cloned your repo, switched into the folder and ran

sudo npm install

followed by

gulp

and got the following output

> TournamentMango@0.6.11 start /home/tendi/apps/mango
> node ./node_modules/gulp/bin/gulp.js

[03:08:27] Using gulpfile ~/apps/mango/gulpfile.js
[03:08:27] Starting 'clean:libcss'...
[03:08:27] Starting 'clean:libjs'...
[03:08:27] Starting 'clean:css'...
[03:08:27] Starting 'clean:js'...
[03:08:27] Starting 'copy:assets'...
[03:08:27] Starting 'copy:root'...
[03:08:27] Starting 'eslint'...
[03:08:27] Starting 'compile:jade'...
[03:08:27] Starting 'watch:package'...
[03:08:27] Finished 'watch:package' after 15 ms
[03:08:27] Starting 'watch:sass'...
[03:08:27] Finished 'watch:sass' after 4.7 ms
[03:08:27] Starting 'watch:jade'...
[03:08:27] Finished 'watch:jade' after 15 ms
[03:08:27] Starting 'watch:js'...
[03:08:28] Finished 'watch:js' after 32 ms
[03:08:28] Starting 'watch:all'...
[03:08:28] Finished 'watch:all' after 3.91 μs
[03:08:28] Finished 'clean:css' after 735 ms
[03:08:28] Starting 'compile:sass'...
[03:08:28] Finished 'clean:js' after 763 ms
[03:08:28] Finished 'clean:libcss' after 850 ms
[03:08:28] Starting 'compile:libcss'...
[03:08:28] Finished 'clean:libjs' after 855 ms
[03:08:28] Starting 'clean:all'...
[03:08:28] Finished 'clean:all' after 8.17 μs
[03:08:28] Starting 'compile:libjs'...
[03:08:28] Finished 'copy:assets' after 972 ms
[03:08:29] Finished 'copy:root' after 1.35 s
[03:08:29] Starting 'copy:dist'...
[03:08:29] Finished 'copy:dist' after 6.57 μs
[03:08:37] Finished 'compile:sass' after 8.4 s
[03:08:37] Finished 'compile:libcss' after 8.31 s
[03:08:37] Finished 'compile:libjs' after 8.74 s
[03:08:37] Starting 'build:lib'...
[03:08:37] Finished 'build:lib' after 6.29 μs
[03:08:39] Finished 'compile:jade' after 12 s
[03:08:41] Finished 'eslint' after 14 s
[03:08:41] Starting 'compile:js'...
[03:08:46] Finished 'compile:js' after 4.5 s
[03:08:46] Starting 'compile:all'...
[03:08:46] Finished 'compile:all' after 7.96 μs
[03:08:46] Starting 'build:all'...
[03:08:46] Finished 'build:all' after 9.15 μs
[03:08:46] Starting 'connect'...
[03:08:46] Finished 'connect' after 23 ms
[03:08:46] Starting 'default'...
[03:08:46] Finished 'default' after 8.73 μs
[BS] Access URLs:
 -------------------------------------
       Local: http://localhost:8000
    External: http://10.5.151.216:8000
 -------------------------------------
          UI: http://localhost:3001
 UI External: http://10.5.151.216:3001
 -------------------------------------
[BS] Serving files from: ./dist

Checked the UI console on localhost:3001 and it's up and running.

Then went to localhost:8000

The page is blank. Like nothing.

I did a view source and this is what it is bringing up:

https://paste.ee/p/np8m2 (source code)

I am probably missing something, no idea what. I got a few warnging when i ran npm install and they are:

npm WARN lifecycle TournamentMango@0.6.11~postinstall: cannot run in wd %s %s (wd=%s) TournamentMango@0.6.11 node ./node_modules/bower/bin/bower install /home/tendi/apps/mango
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.14: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/browser-sync/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.14: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

Any ideas???

[seiyria]

Weird, I totally thought I replied to this via email. Anyway, it's entirely possible that a dependency isn't at the correct version, or bower install did not happen. Try grabbing master (I just fixed this sorta stuff the other day because I needed it running again) and reinstalling. If it doesn't work, make sure bower install happens and completes, then run gulp.

[seiyria]

What version of npm are you using? I saw npm@4 might break postinstall, I
think. I just got this up and running the other day so I know it does work.

Try running postinstall manually, or better try running bower install
manually.

On Sat, Oct 22, 2016, 02:19 vaMuchenje notifications@github.com wrote:

I installed gulp using:

npm install gulp -g

I already had npm installed.

I cloned your repo, switched into the folder and ran

sudo npm install

followed by

gulp

and got the following output

TournamentMango@0.6.11 start /home/tendi/apps/mango
node ./node_modules/gulp/bin/gulp.js

[03:08:27] Using gulpfile ~/apps/mango/gulpfile.js
[03:08:27] Starting 'clean:libcss'...
[03:08:27] Starting 'clean:libjs'...
[03:08:27] Starting 'clean:css'...
[03:08:27] Starting 'clean:js'...
[03:08:27] Starting 'copy:assets'...
[03:08:27] Starting 'copy:root'...
[03:08:27] Starting 'eslint'...
[03:08:27] Starting 'compile:jade'...
[03:08:27] Starting 'watch:package'...
[03:08:27] Finished 'watch:package' after 15 ms
[03:08:27] Starting 'watch:sass'...
[03:08:27] Finished 'watch:sass' after 4.7 ms
[03:08:27] Starting 'watch:jade'...
[03:08:27] Finished 'watch:jade' after 15 ms
[03:08:27] Starting 'watch:js'...
[03:08:28] Finished 'watch:js' after 32 ms
[03:08:28] Starting 'watch:all'...
[03:08:28] Finished 'watch:all' after 3.91 μs
[03:08:28] Finished 'clean:css' after 735 ms
[03:08:28] Starting 'compile:sass'...
[03:08:28] Finished 'clean:js' after 763 ms
[03:08:28] Finished 'clean:libcss' after 850 ms
[03:08:28] Starting 'compile:libcss'...
[03:08:28] Finished 'clean:libjs' after 855 ms
[03:08:28] Starting 'clean:all'...
[03:08:28] Finished 'clean:all' after 8.17 μs
[03:08:28] Starting 'compile:libjs'...
[03:08:28] Finished 'copy:assets' after 972 ms
[03:08:29] Finished 'copy:root' after 1.35 s
[03:08:29] Starting 'copy:dist'...
[03:08:29] Finished 'copy:dist' after 6.57 μs
[03:08:37] Finished 'compile:sass' after 8.4 s
[03:08:37] Finished 'compile:libcss' after 8.31 s
[03:08:37] Finished 'compile:libjs' after 8.74 s
[03:08:37] Starting 'build:lib'...
[03:08:37] Finished 'build:lib' after 6.29 μs
[03:08:39] Finished 'compile:jade' after 12 s
[03:08:41] Finished 'eslint' after 14 s
[03:08:41] Starting 'compile:js'...
[03:08:46] Finished 'compile:js' after 4.5 s
[03:08:46] Starting 'compile:all'...
[03:08:46] Finished 'compile:all' after 7.96 μs
[03:08:46] Starting 'build:all'...
[03:08:46] Finished 'build:all' after 9.15 μs
[03:08:46] Starting 'connect'...
[03:08:46] Finished 'connect' after 23 ms
[03:08:46] Starting 'default'...
[03:08:46] Finished 'default' after 8.73 μs
[BS] Access URLs:

---

   Local: http://localhost:8000
External: http://10.5.151.216:8000

---

      UI: http://localhost:3001

UI External: http://10.5.151.216:3001

---

[BS] Serving files from: ./dist

Checked the UI console on localhost:3001 and it's up and running.

Then went to localhost:8000

The page is blank. Like nothing.

I did a view source and this is what it is bringing up:

https://paste.ee/p/np8m2 (source code)

I am probably missing something, no idea what. I got a few warnging when i
ran npm install and they are:

npm WARN lifecycle TournamentMango@0.6.11~postinstall: cannot run in wd %s %s (wd=%s) TournamentMango@0.6.11 node ./node_modules/bower/bin/bower install /home/tendi/apps/mango
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.14: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/browser-sync/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.14: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

Any ideas???

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#135, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAum2bbLM2QSbHneksLJ8F5O7u2DSUnVks5q2bjrgaJpZM4Kdyfo
.