`decode` panics on `wasm32-unknown-unknown` when `validate_exp` is `true` about jsonwebtoken

[Keats]

3. Do like Chrono does: https://docs.rs/chrono/latest/src/chrono/offset/utc.rs.html#84-108 and have a different function if it's in WASM just importing the js sys lib in wasm

2 is not great because that means you now need to set the timestamp everytime you use the library while I'm expecting a lot of Validation struct to be mostly static

[BrandonDyer64]

@Keats There is an open PR that adds specific wasm support (#318), but it needs to be merged

[Keats]

Yes. As mentioned in the PR, it's missing CI

[BrandonDyer64]

@Keats The structure of Validation does not generally imply being static as the sub field is user specific. The original PR I submitted allowed for a user to choose to add a custom exp timestamp if they want.

I made another PR that uses js_sys when on wasm32-unknown-unknown, but I heavily urge you to please find a way to let the user specify a timestamp for validation