Since

  try {
    ...
  } catch(err) {}

does that, is clear and explicit, and doesn’t make no-catch mean something different than it does in

  try {
    ...
  } finally {
    ...
  }

I think “no 'catch' as empty 'catch' when there is no 'finally'” is just unnecessary inconsistency for no meaningful gain.