One weird way to address #1508, rather than the eminently reasonable "two try-catches with console.log(error) in the catch block", is to run the relevant code in an async forEach. This means exceptions become rejected promises in the console and don't affect other loop iterations.
This also means that there is an async keyword which serves a purpose despite having no corresponding await, which is pretty terrible practice (I try to remove those!), especially uncommented.
Description
One weird way to address #1508, rather than the eminently reasonable "two try-catches with
console.log(error)in the catch block", is to run the relevant code in an async forEach. This means exceptions become rejected promises in the console and don't affect other loop iterations.This also means that there is an
asynckeyword which serves a purpose despite having no correspondingawait, which is pretty terrible practice (I try to remove those!), especially uncommented.Testing steps