jaredhanson who maintains passport-google-oauth2 seems unfortunately MIA since October, and it seems he's the only one that can update that package. Google says they are degrading services already (starting Jan 28), so some sites could start seeing problems already. The fixes to the passport-google-oauth2 are nontrivial and require a fork (not just a configuration change). Fortunately, there's a lot of discussion on this PR: https://github.com/jaredhanson/passport-google-oauth2/pull/5...
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.
They probably don't expect everyone to fix their stuff in time, but I'm sure the people who actually care about their product working are already taking care of it. Social logins aren't exactly rocket science. Especially when you use a library that does all the work for you.
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.