Closed hcancelik closed 6 months ago
@hcancelik Thank you for opening this issue. 🙏 Please check out these other resources that might help you get to a resolution in the meantime:
google-maps
tagThis is an automated message, feel free to ignore.
Looking closely at the issue, this is related to the URL signature package.
There is an open ticket here, so I'm closing this one.
Shouldn't it have pinned dependencies to avoid issues like that going forward?
Confirming, cross-posting, and summarizing some workarounds from the https://github.com/googlemaps/js-url-signature/issues/528 issue thread, npm users can override the upstream js-url-signature version to the 1.0.32 version:
"overrides": {
"@googlemaps/url-signature": "1.0.32"
}
Similarly it appears that users of other package managers (presumably pnpm or yarn) can use the following, but I have not personally confirmed:
"resolutions": {
"@googlemaps/url-signature": "1.0.32"
}
Alternately, you could add "core-js" explicitly as a dev dependency (also confirmed works in our use case):
npm install core-js --save-dev
That said, these are essentially just temporary workarounds already suggested by others in the https://github.com/googlemaps/js-url-signature/issues/528 issue thread that I am cross-posting here for convenience and confirming worked for my team -- but my own team's actual plan is to just wait a bit for a fix, so that we don't have to remember to pull these out when js-url-signature is presumably updated.
same for me
Currently getting the following error from this library
Cannot find module 'core-js/modules/es.string.replace.js' from 'node_modules/@googlemaps/url-signature/dist/index.umd.js'
Environment details
Code example
Stack trace
Thanks!