Swap the order, spread once instead of twice.

We probably should use a different cache object for each memoized function.
The cache key cannot collide here with those two memoized functions since they have a different arity, but just in case we were to re-use that memoize() helper in the future.

// Memoize the `mIsExe` and `fs.access`, for performance
const memoize = function_ => {
  const EXE_MEMO = {}
  // eslint-disable-next-line no-return-assign
  return (...arguments_) =>
	  // Use returned assignment to keep code small
	  EXE_MEMO[arguments_.join('\0')] ??= function_(...arguments_);
}

The cache key cannot be collide here with those two memoized functions since they have a different arity

That's exactly why I choose to use one object, I think it's fine to keep this way for now, it we want resue, we probably need update the logic here , since it only takes strings and use \0 as separator, other cases might not suit anyway.

Since it's "nano" 😄

Ok, but let's keep this in mind.