Looking for a simple first contribution to Phaser

malmfors.samuel · September 11, 2026, 5:54pm

Hi! A friend and I are taking a university course about contributing to open source projects, and we’re looking into contributing to Phaser.

We both have some previous experience using Phaser, but this would be our first time contributing to the project itself. We’re hoping to start with something relatively small that we could work on independently and hopefully get reviewed within the timeframe of our course.

Are there any issues or areas of the project that you would recommend for first-time contributors? Any advice on how to get started with contributing to Phaser would also be really appreciated.

Thanks!

johnSSG · September 12, 2026, 10:10pm

Have you read this?

github.com/phaserjs/phaser

.github/CONTRIBUTING.md

master

# How to contribute

It's important to us that you feel you can contribute towards the evolution of Phaser. This can take many forms: from helping to fix bugs or improve the docs, to adding in new features to the source. This guide should help you in making that process as smooth as possible.

Before contributing, please read the [code of conduct](https://github.com/photonstorm/phaser/blob/master/.github/CODE_OF_CONDUCT.md).

## Reporting issues

[GitHub Issues][0] is the place to report bugs you may have found. When submitting a bug please do the following:

**1. Search for existing issues.** Your bug may have already been fixed, or cannot, or will not, be fixed. So be sure to search the issues first before putting in a duplicate issue.

**2. Not sure if it's a bug?.** Please ask on the [forum][4]. If something is blatantly wrong then post it to GitHub. But if you feel it might just be because you're not sure of expected behavior, then it might save us time, and get you a response faster, if you post it to the Phaser forum instead.

**3. Create an isolated and reproducible test case.** If you are reporting a bug, make sure you also have a minimal, runnable, code example that reproduces the problem you have.

**4. Include a live example.** After narrowing your code down to only the problem areas, make use of [jsFiddle][1], [jsBin][2], [CodePen][5], or a link to your live site so that we can view a live example of the problem.

**5. Share as much information as possible.** Include browser version affected, your OS, version of the library, steps to reproduce, etc. "X isn't working!!!1!" will probably just be closed.

This file has been truncated. show original

Have you checked out the repos and tried fixing any bugs and submitting them? You asked if there are any issues. Yes, there are currently 110 open issues:

You can’t contribute through the forums here, you have to work through git. As far as if they’ll review your code before your course is finished, I think that’s a tough ask and I doubt anyone would commit to doing that. So that would be a big maybe in my mind.

Topic		Replies	Views
Phaser 3 making a game in Phaser tutorial Phaser 3	1	279	June 25, 2022
Awesome Phaser Showcase	2	1062	April 18, 2019
Looking for Collaborators! Phaser 3	7	782	February 12, 2023
Cool/New/Interesting Things In Phaser Phaser 3	1	360	April 10, 2020
Phaser 3 FAQ (from Discord) Phaser 3	0	1298	December 7, 2018

Looking for a simple first contribution to Phaser

Related topics