Martin Schuhfuss

Closing this as unrelated to the `@googlemaps/js-api-loader` package.

This doesn't quite sit right with me. It seems to work, but I feel like checking the number of clusters as a proxy for "has anything changed" isn't accurate enough....

@Remarketeer with the new version 1.4.0, this should be fixed. Can you re-check if you're still seeing the problem?

I'd like to add that after `loader.importLibrary()` you will also have access to the global `google.maps` namespace as it was before after calling `.load()`. So for example: ```js const loader...

modifying as little of the code as possible, that'd be something like this: ```tsx useEffect(() => { const init = async () => { if (!apiKey) return; try { if...

Just noticed an error in this line: `const loader = new Loader({ apiKey, apiOptions });`, it should have been `const loader = new Loader({ apiKey, ...apiOptions });` > Also, does...

Which electron version are you using? Can you provide some more details about the error-message?

I don't think that would have helped much, and most of the time - when dependencies aren't broken - it would only make it more complicated to install this package....

See here: https://developers.google.com/maps/documentation/javascript/versions?hl=en#choosing-a-version-number There is no infinite availability of older versions, and the last 3.50 version [was released 7 November, 2022](https://developers.google.com/maps/documentation/javascript/releases#3.50.12a). I think the versions are only available for a...

Closing this as it isn't related to the js-api-loader package. Bugreports and Feature suggestions for the Maps API should go into the issue tracker at https://issuetracker.google.com/issues?q=status:open%20componentid:188853&s=created_time:desc