Is your feature request related to a problem? Please describe.

NES.css doesn't contain layout styles. This puts a burden on developers.
So I think it will be e

https://wiki.nesdev.com/w/index.php/Emulator_tests

It could run these ROMs and actually check the output somehow - perhaps either by checking memory values, or a copy of the screen buffer.

https://github.com/libretro/blastem-libretro

Alternative Genesis Core with ARM support.

#136 added customizable keys, but there is no way for users to discover this behaviour. Perhaps the text "Click to change" should be somewhere, perhaps as a tooltip?

Be good to understand how to load ROMs and where to obtain legal ones from. I found this: https://dpadhero.com/Download.html.

I can't seem to find any sort of documentation. You mention several new features in the changelog, but some of them (such as the "arpeggio schemes") I can't find any way to access, and others (notably "grooves") I can't figure out what they do. Is there and will there be any sort of help or documentation? As it is, pressing F1 for help just gives an error message.

Currently user needs to kill the process to terminate nes-rust in standalone mode. We should add a proper way to stop.

I realize it would probably take a good deal of work, but it would be nice to have some documentation around the structure of the compiler and its execution flow. I would be interested in contributing to fix the bugs I've reported (big thanks for your prompt responses and fixes), but its difficult to understand the current setup without investing a great deal of energy.