attempting to do:
1: on top of issue #274, which is that locally i've been working with: "React" && Upon deployment, not so.
2: create compatibility in the production environment for packages that have been working locally.
3: migrate from to newer? and getting some incompatibility errors and leg-peer-deps tips
4: instead of installing and migrating to ReactGoogleLogin decided to uninstall and reinstall GoogleLogin --legacy-peer-deps
(this would be the package that was first in use)
error:
Upon completing steps 3 & 4 which is to uninstall and then: npm i google-login --legacy-peer-deps not perf not bad but:
npm i audit fix --force
the fix command made everything worse: 2x more errors, only 20% more LOW but the 2x comes from HIGH & CRITICAL
proposed approach:
regarding a reddit comment/opinion about webpack:
"quicker to migrate to parcel or vite than to fix big app with webpack"
// obviously as long as webpack is not specific enough so that parcel or vite cant achieve same end goal.
(for me end goal of webpack, now removed, was just to get .ENV variables so not too specific)
0: been considering more past few days: update GraphQL, update redux to toolkit, and go with Next.js
attempting to do: 1: on top of issue #274, which is that locally i've been working with: "React" && Upon deployment, not so.
2: create compatibility in the production environment for packages that have been working locally.
3: migrate from to newer? and getting some incompatibility errors and leg-peer-deps tips
4: instead of installing and migrating to ReactGoogleLogin decided to uninstall and reinstall GoogleLogin --legacy-peer-deps
(this would be the package that was first in use)
error: Upon completing steps 3 & 4 which is to uninstall and then: npm i google-login --legacy-peer-deps not perf not bad but:
npm i audit fix --force
the fix command made everything worse: 2x more errors, only 20% more LOW but the 2x comes from HIGH & CRITICAL
proposed approach: regarding a reddit comment/opinion about webpack: "quicker to migrate to parcel or vite than to fix big app with webpack" // obviously as long as webpack is not specific enough so that parcel or vite cant achieve same end goal. (for me end goal of webpack, now removed, was just to get .ENV variables so not too specific)
0: been considering more past few days: update GraphQL, update redux to toolkit, and go with Next.js
1: try setting up as intended for now