Martin Schuhfuss

The newer versions of the APIs will not be supported in this library. See here: https://github.com/googlemaps/google-maps-services-js/issues/1105 There is a standaolne library for places available as `@googlemaps/places` https://github.com/googleapis/google-cloud-node/tree/main/packages/google-maps-places

Can someone provide a minimal reproducible example? Does this only happen in combination with angular?

@anorakdepluie we want to move forward with this and wanted to ask if you could maybe add some more details on what issues you are currently having that could be...

The minmal functionality for that is still there: https://github.com/googlemaps/js-three/blob/main/src/util.ts#L89-L96 That function will convert an `[x, y]` coordinate (in mercator-projection) to a `LatLngLiteral`. To get from your three.js coordinates to mercator-meters...

I think this is out of scope for this library, but I would be really interested to see how this could be implemented.

Hi @Krassnig! Do you have an example-repo where this can be reproduced? I think I saw that error before and it had something to do with the new `moduleResolution: 'bundler'`...

As you already mentioned, the only supported options right now are `radius` and `location`. But there are the `locationbias` and `locationrestriction` parameters available that this library doesn't support at the...

As for this issue, I'm not convinced that this has something to do with the wrapper component provided by this library. Can someone create an example (codesandbox or similar) that...

@BenJackGill this package doesn't really interact with the Places API at all, it only loads the Google Maps JavaScript API in the browser. I don't think there is a way...

Ah, I see. Indeed, the 'places' library dependency of the maps API is still mostly using the older version of the places API. As far as I know, only the...