@brdaugherty I would very much appreciate your feedback

My apologies, third-party cookie deprecation is a wicked hard problem and this is but one manifestation. So I understand it's not easy, nor kind.

Using this library and api.js will continue to work indefinitely (but not forever, nothing last that long).
Here is the list of objects and methods being deprecated. The deprecation & sunset affects only the auth2 module. I wish it was a bit easier to describe, the short of it: there are several modules loaded when src=api.js is used, each of which provides different functionality. The module responsible for downloading the discovery doc, auto-generating the JS API surface, and providing getToken is unchanged and unaffected. The module which handles Auth (both authentication and authorization) is the part which is being deprecated and is affected. If you don't see an object or method listed in the earlier link it won't change in any way.

It's expected that you'll continue to use this library (google-api-javascript-client) if you need to make multiple, chained calls to complex APIs -- this is where a discovery document and auto-generation of the API surface is super helpful, example.

In contrast, if you have only a few API methods to call, using the new gsi/client library and XHR is likely the best route -- keep it simple, right, example.

To clarify on deprecation and sunset; deprecation halts new apps from adoption and terminates support. Sunset will be the big event: breakage. We're still working on what the sunset will look like and when. Until sunset occurs existing apps will continue to function as expected. The caveat being that Chrome's plans to deprecate third-party cookies are when session functionality breaks. The best I can say is stay tuned for more on the sunset dates and impact.

If you want to minimize future risk, migrate sooner, rather than later. If you can't migrate, no worries. For now.

@brdaugherty Thank you very much for your timely and thoughtful response.

Unfortunately, I am using the auth2 module and many of the objects and methods being deprecated but I am relieved to hear that they will continue working after March 31st. I will continue with migration sooner, rather than later.

Thank you again.