Cannot find namespace 'google' after upgrading to version 6

[brune83]

Bug Report

Plugin(s)

"@capacitor/google-maps": "6.0.0"

Capacitor Version

6.1.2

Platform(s)

Web

Current Behavior

I upgraded capacitor/google-maps plugin in my project (I was using version 6.0.0-rc.0 before and it was working) and now building the project or executing ionic serve I have this errors:
[ng] Error: node_modules/@capacitor/google-maps/dist/typings/definitions.d.ts:43:34 - error TS2503: Cannot find namespace 'google'. [ng] 43 export interface Polygon extends google.maps.PolygonOptions { [ng] ~~~~~~ [ng] Error: node_modules/@capacitor/google-maps/dist/typings/definitions.d.ts:64:33 - error TS2503: Cannot find namespace 'google'. [ng] 64 export interface Circle extends google.maps.CircleOptions { [ng] ~~~~~~ [ng] Error: node_modules/@capacitor/google-maps/dist/typings/definitions.d.ts:84:35 - error TS2503: Cannot find namespace 'google'. [ng] 84 export interface Polyline extends google.maps.PolylineOptions { [ng] ~~~~~~ [ng] Error: node_modules/@capacitor/google-maps/dist/typings/definitions.d.ts:117:42 - error TS2503: Cannot find namespace 'google'. [ng] 117 export interface GoogleMapConfig extends google.maps.MapOptions { [ng] ~~~~~~ [ng] Error: node_modules/@capacitor/google-maps/dist/typings/definitions.d.ts:159:14 - error TS2503: Cannot find namespace 'google'. [ng] 159 styles?: google.maps.MapTypeStyle[] | null;

Expected Behavior

I expect my project compiles normally

Code Reproduction

Just build a project using version 6 of @capacitor/google-maps plugin

Other Technical Details

Additional Context

[brune83]

I solved it including this declaration in the file tsconfig.app.json:
"compilerOptions": { "types": [ "google.maps" ] }

Maybe you should specify it in the documentation of the plugin.
Thank you.

[singatias]

I solved it including this declaration in the file tsconfig.app.json: "compilerOptions": { "types": [ "google.maps" ] }

Maybe you should specify it in the documentation of the plugin. Thank you.

Thank you!

This issue shouldn't get close until the documentation is fix imo.