-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Underlying dependency urlsafe-base64 uses Buffer unsafely #785
Comments
See PR: #786 |
Merged
marco-c
pushed a commit
that referenced
this issue
Jun 11, 2023
…r.from (#813) Fixes #785 Co-authored-by: Dan Lee <[email protected]>
Because i needed this quick, and the dev didn't update the npm, ping me when you update the npm repo, so i can use it instead of my temporary one |
@haouarihk I've just published 3.6.2. |
8 tasks
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
NOTE: Please test in a least two browsers (i.e. Chrome and Firefox). This
helps with diagnosing problems quicker.
Setup
Operating System: Amazon Linux 2
Node Version: 18.15.0
web-push Version: 3.5.0
Problem
When calling
setVapidDetails
in Node18 I see the following console error:Doing some debugging the cause of this is because the underlying library:
urlsafe-base64
has not updated to using Buffer.from(). While there are already PRs to fix this, the maintainers seem to have abandoned the project. Would it be possible to fork the implementation ofurlsafe-base64
and consume a patched version withinweb-push
?Expected
No console errors
Features Used
Example / Reproduce Case
The text was updated successfully, but these errors were encountered: