Nick Amoscato

@DanieleMar, an initialized `gapi` client can be retrieved by the [`getGapiClient` promise-based method](https://vue-gapi.github.io/vue-gapi/reference/GoogleAuthService/__index__.html#getgapiclient-%E2%87%92-promise-gapi). It's also included in the resolved response of `login` as described in [Usage](https://vue-gapi.github.io/vue-gapi/#usage).

@DanieleMar, are you still having issues? > at least when using the Composition API @grandpaslab, `v2.1.0-beta.0` [adds support](https://github.com/vue-gapi/vue-gapi/pull/306) for Composition API dependency injection via a `useGapi` wrapper. Could you try...

@CynthiaBlue, sorry for the delayed response, but I hope you've learned a little bit about Vue.js since! I just added a more comprehensive [authentication example](https://vue-gapi.github.io/vue-gapi/examples/authentication.html) which should hopefully give you...

@dcaldessa, this plugin persists the user's session to local storage which you can retrieve via [`getUserData()`](https://vue-gapi.github.io/vue-gapi/reference/GoogleAuthService/__index__.html#GoogleAuthService+getUserData) as illustrated in [the Authentication example](https://vue-gapi.github.io/vue-gapi/examples/authentication.html). Hopefully that helps.

@anaygupta, I'm personally not familiar with Nuxt, but this would be good to document and/or support.

@hanzoz, you might be hitting a known issue with a pending fix (https://github.com/vue-gapi/vue-gapi/pull/109), but to be sure: 1. Does this happen for you in other browsers as well? 2. If...

@DanieleMar, you could try invoking [`getAuthInstance`](https://vue-gapi.github.io/vue-gapi/reference/GoogleAuthService/__index__.html#GoogleAuthService+getAuthInstance) to implement an alternative login flow, just know that it will not inherently store the session in local storage. Feel free to reference the...

Hey, thanks for surfacing. I'm personally not familiar with these mobile contexts, but it seems this library would benefit from improvements on this front. I don't have time to dig...

@ctalkington, any plans to address this discrepancy? These conflicting versions seems to be causing issues during a Webpack compilation process (i.e. via [ncc](https://github.com/vercel/ncc)).

Thoughts on just copying `xml2js`'s [`Options` interface](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/07b2759140ad390e14801cfcc5ed9ff94182e7bb/types/xml2js/index.d.ts#L38-L62) into this project's type definition?