Closed Hannnes1 closed 3 years ago
Hello,
For my purposes, this try catch block was useful to have a clean lib and normalizing errors. (I must need to add more JWTError) But I understand why you need to remove it. I will not do that, but I will add an option in the verify function to passthrough every errors inside this catch block.
This new version will be online in 1h.
Okay, that's fine. In my opinion I prefer the flexibility of being able to handle the errors differently on the front-end, but i see your point
BREAKING CHANGE for v2.1.0
The try catch block that wrapped all other code in the verify method previously catches all useful errors that are thrown, and instead throws the same error all the time, which is not very useful.