Change Details

The module doesn't throw an exception but just goes "that's undefined" which ends up being propagated as an uninformative Z5. We should throw an exception, which would become fixed then. **DoD** Because JavaScript is dang permissive, non-existent exports of the error module are realized as undefined. We do not have tests that exercise this possibility. We should: [ ] make tests for what happens when functions are called with undefined, and [ ] throw a legible error when that happens.

The module doesn't throw an exception but just goes "that's undefined" which ends up being propagated as an uninformative Z5. We should throw an exception, which would become fixed then. **DoD** Because JavaScript is dang permissive, non-existent exports of the error module are realized as undefined. We do not have tests that exercise this possibility. We should: [x] make tests for what happens when functions are called with undefined, and [x] throw a legible error when that happens.

The module doesn't throw an exception but just goes "that's undefined" which ends up being propagated as an uninformative Z5. We should throw an exception, which would become fixed then. **DoD** Because JavaScript is dang permissive, non-existent exports of the error module are realized as undefined. We do not have tests that exercise this possibility. We should: [ x] make tests for what happens when functions are called with undefined, and [ x] throw a legible error when that happens.