Closed dzuluaga closed 2 weeks ago
Thank you for highlighting the issue. It seems to be fixed with the 1.0.2 release.
If you still struggle with some issues, make sure to follow the core instruction first and then plugins: google and openstreetmap.
I've also prepared the minimal sample that you can found here.
Hi @dzuluaga - closing the issue since it seems to have been resolved with lates release. In case of any issues still reappearing please reopen! 👍
Yes, the issue was resolved after the modules were published. Moving forward, it would be great if we could avoid similar issues by having the team cross-test each other's work. This will help us catch any potential problems earlier.
I encountered an issue while installing the
@openmobilehub/maps-plugin-googlemaps
and@openmobilehub/maps-plugin-openstreetmap
packages. These modules have a peer dependency on@openmobilehub/maps-core@1.0.0-beta
, but it seems that this version doesn't exist in the npm registry.Steps to Reproduce:
The following warnings and errors are displayed:
Expected Behavior:
The installation should succeed without errors or warnings. The correct version of
@openmobilehub/maps-core
should be referenced by the plugins.Actual Behavior:
The installation fails because
@openmobilehub/maps-core@1.0.0-beta
does not exist in the npm registry.Additional Information:
@openmobilehub/maps-plugin-googlemaps
and@openmobilehub/maps-plugin-openstreetmap
are incorrectly referencing@openmobilehub/maps-core@1.0.0-beta
.Incorrect references:
Google Maps
Mapbox
Azure Maps
OpenStreetMap
The latest available version in the npm registry for
@openmobilehub/maps-core
is1.0.0
.Suggested Solution:
@openmobilehub/maps-core
, such as1.0.0
.More context
npm add @openmobilehub/auth-google
Thank you for looking into this issue!