Cannot find module 'core-js/modules/es.string.replace.js'

[hcancelik]

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

1. Specify the API at the beginning of the title (for example, "Places: ..."): Library
2. OS type and version: Node
3. Library version and other environment information 3.3.42

Code example

const { Client } = require("@googlemaps/google-maps-services-js");

Stack trace

 Require stack:
        node_modules/@googlemaps/url-signature/dist/index.umd.js
        node_modules/@googlemaps/google-maps-services-js/dist/serialize.js
        node_modules/@googlemaps/google-maps-services-js/dist/directions.js
        node_modules/@googlemaps/google-maps-services-js/dist/client.js
        node_modules/@googlemaps/google-maps-services-js/dist/geolocate.js
        node_modules/@googlemaps/google-maps-services-js/dist/index.js

Thanks!

[wangela]

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.

@hcancelik Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

• Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
• Open a support case - Get 1:1 support in Cloud Console.
• Discord - chat with other developers
• StackOverflow - use the google-maps tag

This is an automated message, feel free to ignore.

[hcancelik]

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.

googlemaps/js-url-signature#528

[Politta]

Shouldn't it have pinned dependencies to avoid issues like that going forward?

[TimJohns]

Confirming, cross-posting, and summarizing some workarounds from the googlemaps/js-url-signature#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 googlemaps/js-url-signature#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.

[3DGISKing]

same for me