But that library hasn't been updated to not use the deprecated api yet: https://github.com/jaredhanson/passport-google-oauth2/issues...
And even when the fix lands, you still need to make specific code changes for it.
They can't possibly expect everyone to fix their social login code in time right? 50k weekly downloads: https://www.npmjs.com/package/passport-google-oauth20
At the bottom of the PR discussion, there is a link to a fork that somebody created here: https://github.com/passport-next/passport-google-oauth2 As far as I can tell, the only way to continue using node + google oauth right now is to switch to using that hard-to-find fork. That's what I've done with https://cocalc.com.
Dropping functionality the day before the notice is sent is ... troubling.
As I've noted about several similar such instances previously: this is the company that wants us to trust it to build driverless cars and other such systems? Vastly better process and respect is required.
It will be free and will charge a fee for the following:
1. auto upgrading from discarded services
2. retrieving passwords that are forgotten
3. Changing around your login id (automatically) for various services so you won't have to remember what you used
>Please update your projects listed below by March 7, 2019 and ensure they are no longer using Google+ APIs, or requesting Google+ OAuth scopes.
Sure, it won't be that difficult to change, but this isn't something you do every day. You do it once and then forget about it. The initial investigation of how to add a Google login and then implementing it was done 2 years ago -- now I have to go off and research and learn how to do it all again in a different way.