This may be related to my own misunderstanding of how npm packages work but I'm a bit confused. I am including mdbreact using the git URL for the pro version (git.mdbootstrap.com/mdb/react/re-pro.git) in my package.json.

Previously I had the react package I wanted installed specified in my package.json too, upon a recently npm update react started complaining about multiple versions of react. I am not sure why because mdbreact and my package.json specific 17.0.1.

I temporarily have it working again by not specifying react in my own package.json although of course there is a complaint by npm that I have the missing peer dependancy react that is required mdbreact.

I think my questions are: Is it intended that mdbreact manages the react version or that I specify it in my own package.json? Does it make sense to have a package specified in mdbreacts dependancy's and peerDependencies in the mdbreact package.json? (especially given that react hates having multiple versions installed)

Matt.