I'm working on Pygodide, a Pyodide-based alternative to pygbag for putting Pygame apps on the web.

What pain points have you hit with pybag? What features would you want to see from a project like this? I want to build something that people will want to use.

Itch.io Live Demo pygodide-test-project

• It's running both numpy and fastquadtree, which aren't pure-python packages
• Source: Numpy Particles

Main differences from pygbag:

• Supports all pyodide-compatible packages (e.g. scipy works here but not on pygbag)
• Typer-based modern CLI
• Automatic asyncification of your game loop (so you don't have to add async def and asyncio.sleep(0)
• More extensive error and warning messages to figure out why your app isn't running properly + generated logs for filing issues.
• Reads the pyproject.toml and requirements.txt for dependencies instead of a comment at the top of main.py
• Configurable entry point (Not always main.py's main)
• Relies on Pyodide for web support of pygame and other packages, so when Pyodide gets better, so does Pygodide.
• Everything can be configured via the CLI, but also via an entry in your pyproject.toml

Similarities with pygbag:

• Similar super simple user interface pygodide build . --serve

I want to add many more features and QoL improvements (such as a configurable background color) as well as improve the loading times and performance of games running through Pygodide.

Links

Repo
Documentation