Closed alexanderGalushka closed 4 years ago
I agree with you @alexanderGalushka and I have been watching the deno development of additional crypto modules. I also share your opinion that it would be better to focus on the official deno modules from now on. If you have already done it, I would love to accept the PR! After that, I will update the README accordingly.
Thank you!
@timonson on it, give me about 30 min
Thank you @alexanderGalushka !
If you use Deno.bundle() to bundle with djwt lib compiler throws downcast error. In one of the latest deno releases deno dev team generalized errors to use ErrOp and has removed some javascript errors.
The underlying problem is with hmac deno/x dependency is not being up to date. There are a few options we have:
The later option is limited to support only hmac256, hmac512 is not implemented. I've submitted a feature request to implement hmac512.
I propose to disable hmac512 support for now (I can submit PR to pluck it up and replace hmac256 with HmacSha256, I've tested it) and use what deno std provides. Eventually when deno implements 512 we can put it back in :)
Just in general I think it's better build on top of deno std.
@timonson would like to hear your thoughts.