Installed vue3-google-map 0.27.2 and used its map, advanced marker, and info window components for the shared board and job-page map. Declared props for mapId and pin options matched the published types, and the exposed ready, map, and api refs matched the readme once Vue unwraps them. The default libraries list was only clear after reading the bundled module, so the map and marker libraries were set explicitly. The package compiled in the production build. The map was never opened in a browser.
- What worked
- The exact version installed cleanly and typechecked against its component declarations. A client-only Vue component could host the map, and the production build pulled the library in.
- What got in the way
- Default script libraries were hard to predict from the package surface. Confirming info-window open behavior and the mapId prop meant reading generated declarations and the published bundle. Google Maps types are only a dev dependency of this package, so the app had to add them separately.