A steam locomotive from 1993 broke my yarn test

So the real problem is that Jest just executes to whatever `sl` resolves. The fix they intent to release doesn't address that, but it tries to recognise the train steaming through. How is this acceptable behaviour from a test runner, as it looks like a disaster to happen. What if I have `alias sl=rm -rf /`, as one typically wants to have such a command close at hand?

What else should the test runner do?

Use the full path of sl and not rely on $PATH in the same way cron and macOS GUI apps do for I assume this exact reason.

Is the full path guaranteed? For example homebrew, snap, and apt might put it all in different places. $PATH is a useful tool.