jroblak/generator-phaser-browserify

A generator for Phaser using Gulp and Browserify

generator-phaser-browserify

A Yeoman generator to generate HTML5 games with phaser using Gulp and Browserify. Built off the work by Julien Castelain on generator-phaser. Allows the use of browserify (i.e. var player = require('Player.js')) with Phaser.

Check out this test game as an example of project layout / useage.

INSTRUCTIONS

• Install Node.js

• Install the required npm modules by issuing these commands:

  npm install -g yo generator-phaser-browserify

  You can optionally install Gulp globally npm install -g gulp but you don't have to.

• Create a new directory for your game:

  • Unix/OSX : mkdir ~/Projects/game && cd $_
  • Windows : mkdir %USERPROFILE%\Projects\game && cd %USERPROFILE%\Projects\game

• Invoke the generator:

  yo phaser-browserify

• Run a local development server (livereload, watchify enabled) with this command:

  npm start

  If you have Gulp installed globally you can also use: gulp

• Package your game (i.e. minify css, html and js) with:

  npm run build

  If you have Gulp installed globally you can also use: gulp build

CREDITS

• @photonstorm for creating phaser.
• The guys behind yeoman.
• Gulp.js

generator-phaser-browserify's Issues

TypeError: Cannot read property 'cache' of undefined

HI, just testing this out and got an error on fresh install:

$ npm start

> [email protected] start /home/rhalff/git/games/testgame
> node ./node_modules/gulp/bin/gulp.js

[22:21:01] Using gulpfile ~/git/games/testgame/gulpfile.js
[22:21:01] Starting 'connect'...
[22:21:01] Server started http://localhost:9000
[22:21:01] LiveReload started on port 35729
[22:21:01] Finished 'connect' after 23 ms
[22:21:01] Starting 'watch'...
[22:21:01] Finished 'watch' after 15 ms
[22:21:01] Starting 'clean'...
[22:21:01] Finished 'clean' after 19 ms
[22:21:01] Starting 'copy'...
[22:21:01] Finished 'copy' after 2.35 ms
[22:21:01] Starting 'copylibs'...
[22:21:01] Finished 'copylibs' after 4.32 ms
[22:21:01] Starting 'compile'...
[22:21:01] 'compile' errored after 356 μs
[22:21:01] TypeError: Cannot read property 'cache' of undefined
    at watchify (/home/rhalff/git/games/testgame/node_modules/watchify/index.js:13:27)
    at Gulp.gulp.task.gulp.src.pipe.minifycss.keepSpecialComments (/home/rhalff/git/games/testgame/gulpfile.js:53:17)
    at module.exports (/home/rhalff/git/games/testgame/node_modules/gulp/node_modules/orchestrator/lib/runTask.js:34:7)
    at Gulp.Orchestrator._runTask (/home/rhalff/git/games/testgame/node_modules/gulp/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (/home/rhalff/git/games/testgame/node_modules/gulp/node_modules/orchestrator/index.js:214:10)
    at /home/rhalff/git/games/testgame/node_modules/gulp/node_modules/orchestrator/index.js:279:18
    at finish (/home/rhalff/git/games/testgame/node_modules/gulp/node_modules/orchestrator/lib/runTask.js:21:8)
    at module.exports (/home/rhalff/git/games/testgame/node_modules/gulp/node_modules/orchestrator/lib/runTask.js:60:3)
    at Gulp.Orchestrator._runTask (/home/rhalff/git/games/testgame/node_modules/gulp/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (/home/rhalff/git/games/testgame/node_modules/gulp/node_modules/orchestrator/index.js:214:10)

This is the line in wachify: https://github.com/substack/watchify/blob/master/index.js#L13

I guess it installs a more recent version of watchify?

Also the readme is mentioning:

Invoke the generator:

yo phaser

Which should be yo phaser-browserify

Problems with watchify due to EPERM bug

I really like this generator, but after my project reached a certain size = compile / clean time, i got the watchify EPERM bug which nobody seems to be able to figure out browserify/watchify#83.

The trigger was that once the clean task needed more than ~100ms the bug occurred, EVERY time!

After i just commented out the clean task everything went as smoothly as before, so my question is, if the new files apparently overwrite the existing ones without any problem, do we really need the clean task, or is it really superfluous?

If so, it should be removed to prevent others to spend hours trying to figure it out ;)

package downloaded with npm fails with processhtml

Generator downloaded and installed from npm does not have the latest fix for processhtml so cannot build the sample project using the instructions provided in README.

Mobile/Responsive option

It would be awesome to have a mobile/responsive subgenerator (with device-orientation, etc.)