4 ms·
There's precedent for outright deprecating a package when others exist that do a better job of meeting current development needs. With Promises and node/browser
by rmrfrmrf 8y ago
There's precedent for outright deprecating a package when others exist that do a better job of meeting current development needs. With Promises and node/browser cross compatibility being the biggest ecosystem shifts, there are a few newer choices that already meet those needs. Also, `request` in particular would be gross to upgrade since so many people rely on additional dependencies that add compatibility for things like Promises, retry strategies, etc., all with varying degrees of active maintenance.