I tried to avoid webpack since I knew compile time would be an issue for my other team members and it turned it out it was. As a web-dev I'm use to its workflow but onboarding game devs hate it. I have to hear everyday lets move to Godot, Unity, Unreal Engine because waiting 4 seconds for compiling is a headache.

Switching to Typescript is great for larger teams because it makes properties explicit. I personally like coffee-script and find it more productive if I'm the only dev but I swallowed the medicine on this one and it was worth it.

VSScode is powerful with Typescript but its not as productive as VIM. I think of code completion and seeing errors right away as crutches that atrophies a developers own skills to find code and errors but they can make it much easier for juniors and lower the bar, pair this with wallabyjs and you have a controlled environment that catches everything for you.

I found no resources on testing Phaser but figured out my own way of mocking Phaser objects, and came up with my own way to write acceptance-like tests for my game without electron.

I really wanted to contribute to Phaser3 and had put great effort to join but Richard was useless in responding. He said he was porting their tickets from Trello to Github and then I could contribute which never happened, I asked month over month. I really wanted to use Phaser 3 to future proof my game and I would have contributed significantly. I could have forked PhaserCE but its a mess which makes sense for the rewrite but working blindly on Phaser 3 would be futile. I am quite bitter about bitter about this because I 20 hours a week for 6 months I could have contribute and now I don't

I think I will likely just write my own lightweight game framework to map only what I need and gut Phaser. Even looking at Phaser 3 codebase with their big rewrite from scratch its still clunky and I think this is because they don't build games at a large scale with a team to have a good feeling to fine tune an engine.

https://github.com/omenking/swap-n-pop

(meaning: team-based, has more days available, not part of the main "competition", which is about the solo achievement of making a 48 hour game)

It was my first introduction to either, and none of us had used Phaser before. My experience matches yours: combining the two made for a great dev experience, and the docs are confusing at times.

Luckily my friends Thomas ten Cate (aka Frozen Fractal) and Marten Veldthuis (aka... Marten Veldthuis) are excellent developers, who have struggled with way worse documentation, so we managed anyway. Docs aside, Phaser-the-framework seemed very well constructed.

Tangent: a few competitions later Thomas made Leonardo's Paint Machine[2], which is so amazing, especially for a 48 hour game, that I'll link it despite being made in a different framework (he uses Ludum Dares to try new out new frameworks and such).

[0] http://ludumdare.com/compo/ludum-dare-34/?action=preview&uid...

[1] https://blindedcyclops.neocities.org/ld34/index.html

[2] https://frozenfractal.com/games/leonardos-painting-machine/

(I was using timer instead of collision for bullets since I had the hit/miss outcome coming from a percentage base rile as opposed as game phisycs and expired bullets just at the right time to make them appear misses - maybe not the greatest idea mind you but eh got it working and was cool enough)

I bet it's a great place to learn tricks for squeezing better performance out of the web too (even if limited to specific niche tasks).

[1] http://phaser.io/phaser3/devlog

[2] http://phaser.io/news/2016/12/phaser-in-2016-and-beyond

Phaser is a great framework. I managed to conceive, write the game from scratch and have it in the app store within a day.

It's no longer on the iOS store as I didn't continue to pay my dev licence, but happy to share the play store link if anyone is interested.

In the end was running well enough from the browser too making wrapping moot.

It’s published at http://increstellar.com and the code is not obfuscated but beware: it’s very amateurish

One of the recent posts mentioned that TS defs would be part of launch, but it's been quiet on that front now.

There's a closed issue in GitHub where someone is creating defs themself.

If I remember correctly TS community support was why he didn't stick with it. Community voted and straight JS but with TS defs were going to be the target.

Phaser uses an old customized version of pixi for the visuals.

If on the other hand you want the option to build for desktop or mobile and other platforms try Unity. Why not pick Unity from the start? It supports building in WebGL but you can't really delve in that automatically generated javascript code to fix something in there and even if you tried to do it you would have to do it every time you build your game. You just have to trust that Unity will keep up to date its framework and its build system will optimise it as best as it can.

Also with Unity you trust your art and music to its packaging system. You can change some of the import options, but in the end you depend on its optimisations.