You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Various tools give and receive VAPID keys in the typical base64 URL format, and converting between that format and the format used by this library is sufficiently error-prone and non-trivial to justify direct support IMO.
The text was updated successfully, but these errors were encountered:
Ok perhaps error-prone and non-trivial is a slight exaggeration, but to give additional context I was running into a JWT error and it wasn't clear if the issue was in the hand-written key format conversion code or in this library, slowing down debugging substantially. It now appears that the conversion code was fine and that the issue was with this library (or a dep) and has seen been fixed in 0.4.
Being able to just plug in the same base64 URL format I was using with node's web-push library would make debugging easier and just avoid some noisy base64 handling code from existing within the application, particularly given that this library already depends on base64-bytestring.
Various tools give and receive VAPID keys in the typical base64 URL format, and converting between that format and the format used by this library is sufficiently error-prone and non-trivial to justify direct support IMO.
The text was updated successfully, but these errors were encountered: