@pandax381, I made a fork of mruby here, where I applied your work from mruby-io to the current release (3.2.0) of mruby. I'll probably do the same for mruby-socket soon.

Those gems were standalone when you modified them, but they're integrated into mruby now. Once everything is up to date, can we switch the mruby submodule in this project to target that fork? Instead of requiring separate io and socket gems, the config file could require from the standard library.

Or would you rather update the gems separately? Changes are made on the esp32 branch btw.