You must log in or register to comment.
That’s not an error, it’s a warning. It shouldn’t break anything…
Exactly
My #1 pet peeve is when someone comes to me with a problem, and the solution is in the fucking console output or error message.
On a bad day, if I had unilateral power, I would fire those people on the spot.
Sometimes I’ll copy paste the error message back to them. Apparently it works better when it’s in a text message.
On the context of a node package, I’m pretty sure that “solution” is utterly worthless and doesn’t come even close to targeting the same functionality the old code had.
But odds are the one place the library author used that function can be replaced by a completely different functionality that happens to use the suggestion.
Ahh… the ostrich approach
Wait I thought the deprecation of the deprecation warning was deprecated.