No check needed. Parsing will throw an error if base64 is not valid

[levinunnink]

We don't actually need to run the regex check on the base64 string.

1. It was failing on a valid base64 string for me.
2. The window.atob or the Buffer.from will both throw errors if the string is invalid and the parseJwtToken will return false.

By removing this, we don't get any invalid results on valid jwt tokens.

[michaelzoidl]

Hey @levinunnink thanks for the PR, your right, thanks for removing the function (i was anyway not happy with this big and complex regex)

Could you also remove the isValidBase64 tests from the test.js file? :) After that i will update some dependencies and deploy a new version 🎉

[levinunnink]

@michaelzoidl Whoops! I totally missed the test coverage. It should be fixed now.

[coveralls]

Coverage decreased (-0.2%) to 89.286% when pulling 2b67833 on levinunnink:master into d951c19 on entwicklerstube:master.

[michaelzoidl]

Wow, totally forgot this PR.

I've seen you published your own version with the name is-jwt-valid right? Do you want still to merge your version into this one?

Alternative i could mention your repository in the README of this one.

[levinunnink]

@michaelzoidl No worries! I just need to ship this fix into production so I forked it. I'm fine with whatever you want to do. :-)