Hey Claus, those peer dependency warnings are just npm letting you know that some packages expect specific versions of other libraries to work properly—let’s tackle them step by step:

1. Resolve google-maps-react’s React/React-Dom Requirements #

The warning tells you google-maps-react@2.0.0 only works with React ~0.14.8 || ^15.0.0 || ^16.0.0, but your project doesn’t have those versions installed. You’ve got two solid options here:

Option A: Downgrade React and React-Dom to Compatible Versions #

If you don’t mind rolling back your React version to 16.x (the latest stable in the supported range), run this command:

npm install react@^16.14.0 react-dom@^16.14.0 --save

This will install the newest 16.x release, which should play nicely with google-maps-react@2.0.0.

Option B: Upgrade google-maps-react to Support Your Current React Version #

If you want to keep your current React version (like 17+), check if a newer version of google-maps-react supports it. Install the latest version with:

npm install google-maps-react@latest --save

Just note: Newer versions might have API changes, so you’ll want to test your map-related components afterward to make sure nothing breaks.

2. Fix firebase-functions’ Peer Dependencies #

You mentioned the warning cuts off, but firebase-functions typically requires firebase-admin and firebase-functions-test as peer dependencies. Install their latest versions (we’ll use --save-dev for the test package since it’s only needed for development):

npm install firebase-admin@latest firebase-functions-test@latest --save-dev

3. Re-Run the firebase-functions Update #

Once you’ve handled the above dependencies, run your original update command again:

npm install --save firebase-functions@latest

This time, those peer dependency warnings should be gone (or at least reduced to only unavoidable ones).

If you still see warnings, you can run npm ls to inspect your full dependency tree and spot any remaining version conflicts.

内容的提问来源于stack exchange，提问作者Claus