better error logging
Author: MikeKovarikCreated Mar 9, 2019Updated Jun 17, 2023
I'm submitting a feature request
- Library Version: aurelia-script 1.3.1
Current behavior:
If you make a typo, or on this case I forgot to add async to a function, you get a long but useless stacktrace pointing to inside of aurelia but nowhere in the stack trace does it give me any clue of what view, class, file is at fault. I've had this issue for years, ever since Aurelia was still in beta and it's been my biggest problem with aurelia ever since. Because despite having .developmentLogging() enabled I'm subjected to tearing my app down and uncommenting it line by line until I find the needle in the haystack

Expected Behavior: Some general information about origin of the error - the file, line, or a class/method
Source: aurelia/framework