Strategies to keep the runtime light?

I don't know how much Node's (or llrt's - I mention Node because obviously, one stumbles across this when looking for a lightweight alternative) size has increased due to including features that maybe could've been released separately but I found it concerning that you're also e.g. including a test runner already.

Are there plans to either release runtimes that are to be used for production only and don't contain things like said test runner and possibly other features only needed during development? Or maybe the ability to create custom runtimes that don't include them? Or does the footprint of the engine make up so much of the runtime that anything that could be reasonably excluded is negligible?

No files, tests, or entry points are named. Start by measuring the footprint of the included test runner and other development-only features, then determine whether production-only or custom builds are feasible; done means a decided, documented approach.

Written by the indexing model from the issue text.