Open tagyoureit opened 6 years ago
I fixed these two errors but I wasn't able to push because this repo is giving me a 403. I also can't officially use this module because of guaranteed error messages every time a service has a length longer than 20.
If I understand correctly, you have made some changes to this modules code but havent been able to create a pull request because of 403?
Correct, I've tried with SSH & HTTPS. Maybe I don't have permission to push? I didn't add error emitting or anything, I just removed MAX_STRING
from service_type.js
along with its references, because I don't see how checking it adds any value, especially when the Error can't be caught.
Hi, I've run into a couple of situations where your module Throws an error, but there is no way to catch it in my application. For example,
and
It would be great if these errors (and all errors) were emitted to a
browser.on('error', function...)
event. It would be hard to officially include this module in my code when it causes an error to exit the nodejs process.thanks!