You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have the same issue, I tried upgrading to v5.0.0 but I then got a JS out of memory exception. So I removed my package-lock.json and deleted the folder node_modules manually and I ran npm i from scratch. I am also now getting this same error, on npm run start on npm run build and on all CI/CD pipelines. Any ideas?
yarn why v1.22.17
[1/4] 🤔 Why do we have the module "webpack"...?
[2/4] 🚚 Initialising dependency graph...
[3/4] 🔍 Finding dependency...
[4/4] 🚡 Calculating file sizes...
=> Found "webpack@4.44.2"
info Reasons this module exists
- "react-scripts" depends on it
- Hoisted from "react-scripts#webpack"
info Disk size without dependencies: "3.57MB"
info Disk size with unique dependencies: "13.64MB"
info Disk size with transitive dependencies: "33.61MB"
info Number of shared dependencies: 140
=> Found "frappe-gantt-react#webpack@4.29.6"
info Reasons this module exists
- "frappe-gantt-react#react-scripts" depends on it
- Hoisted from "frappe-gantt-react#react-scripts#webpack"
info Disk size without dependencies: "10.34MB"
info Disk size with unique dependencies: "20.45MB"
info Disk size with transitive dependencies: "40.43MB"
info Number of shared dependencies: 141
✨ Done in 0.60s.
Activity
raix commentedon Dec 15, 2021
Did you remove node_modules folder and re installing?
fkocovski commentedon Dec 16, 2021
I have the same issue, I tried upgrading to
v5.0.0but I then got a JS out of memory exception. So I removed mypackage-lock.jsonand deleted the foldernode_modulesmanually and I rannpm ifrom scratch. I am also now getting this same error, onnpm run startonnpm run buildand on all CI/CD pipelines. Any ideas?Mouaadouk302 commentedon Dec 17, 2021
i have the same error
raix commentedon Dec 17, 2021
do you have node_modules out side the project folder?
fkocovski commentedon Dec 17, 2021
Nope same level as
src,publicand wherepackage.jsonisraix commentedon Dec 17, 2021
What output do you get when running
npm why webpack?(same question if you use yarn,
yarn why webpack)fkocovski commentedon Dec 29, 2021
anshu1121 commentedon Jan 6, 2022
upgrade react-scripts to fix the issue