-
Notifications
You must be signed in to change notification settings - Fork 11
Conversation
So far this seems to be working okay for me. Looks like we got another vulnerability in the last few days, though. |
Updated ToastUI to get rid of that error, ran another round of updates. And I was wrong about that other vulnerability - turns out that audit was from a different branch, so it's one of the ones this fixes. However, I now get the following errors logged to the console:
Also, I get this whether I run it in a private tab or not:
|
That error is from ssb-ebt, it should be harmless. I don't understand the other bug. I tried doing a npm upgrade toast + dedupe. Seems to be running fine here. |
I general not super excited about these huge npm upgrades, as so many things can go wrong and the gains seems to be rather small. |
In general, I would agree. My rationale for this is as follows:
|
Looking at that error again, it should not be related to these bumps. Instead its the new sync module I built: https://github.com/arj03/ssb-browser-core/blob/master/feed-replication.js. I'll move the error over to core. |
Attempt at updating deeper dependencies. Haven't tested it thoroughly yet.
Partial fix for #301 - gets rid of one vulnerability.