Ah! It took me a while to get why one would need it. I am doing all setups per hand, but I think esp for intermediate devs who actually don't care about the engine in the background but want to write apps this seams like a good thing.
Thank you! I think this could even help advanced devs though––it's more readable and future-proof to define transformations on react-scripts than it is to directly edit react-scripts and then have to keep it in sync with the upstream fork. Plus, the @rescripts/utilities package helps ensure that transformations you define conflict as little as possible with other rescripts 😇