Just wanted to add my experience incase it helps anyone.
I am using a Sanity CMS + Gatsby set up which comprises of a root folder containing a web and a studio directory. I was forgetting to delete the package.lock and node modules folders from all three and was therefore getting conflicting react version errors. So remember to check in all of your project’s directories.
Hi @tomwrankmore 
, thanks that is really helpful advice. I appreciate you sharing that with use. This will help others who are having similar issues. 
Nathan you are a life saver! This is precisely what was happening with my deploys, and I was wondering why I had to force the npm_flags every time. Turns out its the tailwindcss generated package-lock.json pegged to certain versions as you mentioned. Thanks a ton!
I’m using yarn and seeing this exact issue. --legacy-peer-deps is for npm so I’m not sure why that would have any impact?
@winkerVSbecks I don’t believe that I ever said it would.
I’m also not sure what you’re referring to in general, since you’ve provided no detail and have made no other posts on the forum.
Sorry my bad, I conflated this with another issue.