You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Use @googlemaps/js-api-loader as a peer dependency #782
If you would like to upvote the priority of this issue, please comment below or react on the original post above with 👍 so we can see what is popular when we triage.
@cgarrovillo Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:
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.
What happened last week was a published version of @googlemaps/js-api-loader that was broken. That would have had mostly the same effect if it was installed as a peer-dependency instead of a transitive dependency.
The only thing you can do in such a situation is to pin the dependency to an older version, and that can be done for both peerDependencies as well as for transitive dependencies (by specifying a resolution for the package in the package.json).
Activity
wangela commentedon Feb 16, 2024
If you would like to upvote the priority of this issue, please comment below or react on the original post above with 👍 so we can see what is popular when we triage.
@cgarrovillo Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:
google-mapstagThis is an automated message, feel free to ignore.
IsraelVazquezEsparza commentedon Feb 16, 2024
@cgarrovillo Thanks. It works!
usefulthink commentedon Feb 23, 2024
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.
What happened last week was a published version of
@googlemaps/js-api-loaderthat was broken. That would have had mostly the same effect if it was installed as a peer-dependency instead of a transitive dependency.The only thing you can do in such a situation is to pin the dependency to an older version, and that can be done for both peerDependencies as well as for transitive dependencies (by specifying a resolution for the package in the package.json).