frankcollins3
commented
1 year ago solving by saving face with google. As far as I just experienced, --legacy-peer-deps could easily turn into a production bug
next app will still have the react-express directory with the working
attempting to do: link react-google-login but tbh it was implemented in the waterapp react version & i also use passport now for local-auth
error: npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: mine-nugget-ts@0.1.0 npm ERR! Found: react@18.2.0 npm ERR! node_modules/react npm ERR! react@"18.2.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"^16 || ^17" from react-google-login@5.2.2 npm ERR! node_modules/react-google-login npm ERR! react-google-login@"*" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /Users/me/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
proposed approach: 0: firstly admitting the react-express version was breaking (👍 heroku psql but 👎 azure | EC2 ) problem in that version was that webpack started breaking in build, removed webpack and app still recognized webpack. // saw it probably quicker to fix w/ nextJS & did so with this next-water-app. (then added @redux/tool & redis & apollo, JWT)
also: computer messed up after upgrading macOS so using an older machine. I plan on migrating again to 13.4.9 I was using NextJS13.4.9 before pulling the repo: github.com/frankcollins3/mine-nugget-ts, stripping clean, starting fresh.