Build failed because of webpack errors

Question

I am getting below error from next js app suddenly. Any solution to fix that problem?

./pages/_app.tsx Error: [BABEL] C:\Projects\skribeNew\app-web\pages\_app.tsx: You gave us a visitor for the node type TSSatisfiesExpression but it's not a valid type at verify (C:\Projects\skribeNew\app-web\node_modules\next\dist\compiled\babel\bundle.js:1910:397612) at Function.explode (C:\Projects\skribeNew\app-web\node_modules\next\dist\compiled\babel\bundle.js:1910:396515) at C:\Projects\skribeNew\app-web\node_modules\next\dist\compiled\babel\bundle.js:1:49254 at Generator.next (<anonymous>) at Function.<anonymous> (C:\Projects\skribeNew\app-web\node_modules\next\dist\compiled\babel\bundle.js:1:79767) at Generator.next (<anonymous>) at evaluateSync (C:\Projects\skribeNew\app-web\node_modules\next\dist\compiled\babel\bundle.js:1910:717268) at Function.sync (C:\Projects\skribeNew\app-web\node_modules\next\dist\compiled\babel\bundle.js:1910:715284) at sync (C:\Projects\skribeNew\app-web\node_modules\next\dist\compiled\babel\bundle.js:1:80263) at sync (C:\Projects\skribeNew\app-web\node_modules\next\dist\compiled\babel\bundle.js:1910:716601)

I changed the babel types version to previous one, But it did not work.

Try removing node_modules and yarn.lock (or package-lock.json) and yarn install (or npm install) again. — Cully
– Cully, Commented Oct 28, 2022 at 4:42
Does this answer your question? You gave us a visitor for the node type "ForAwaitStatement" but it's not a valid type — Cully
– Cully, Commented Oct 28, 2022 at 4:43

General Grievance · Accepted Answer · 2023-12-12 13:53:14Z

5

It was because of an incompatible version issue for the npm package "@babel/plugin-transform-typescript". I fixed to the correct previous version in package.json file. Now it's working fine. Below is the code -

"devDependencies": { "@babel/plugin-transform-typescript": "7.19.3", } "resolutions": { "@babel/plugin-transform-typescript": "7.19.3" }

edited Dec 12, 2023 at 13:53

General Grievance

5,12039 gold badges39 silver badges60 bronze badges

answered Oct 28, 2022 at 14:07

Md. Nizam Uddin Mahmud

2111 gold badge2 silver badges12 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Solders Over a year ago

I encountered the same thing. Due to having a ^ set for the version of @babel/preset-typescript, @babel/plugin-transform-typescript got bumped to 7.20.0. Manually specifying @babel/plugin-transform-typescript": "7.19.3" resolved the issue.

Cow Over a year ago

Please do not post your Fiverr, Upwork or any other paid ressources on Stack Overflow.

node_modules · Accepted Answer · 2022-11-02 10:58:52Z

0

npm i --save --legacy-peer-deps

edited Nov 2, 2022 at 10:58

node_modules

4,9756 gold badges25 silver badges38 bronze badges

answered Nov 1, 2022 at 19:06

Yasir

5856 silver badges11 bronze badges

1 Comment

nima Over a year ago

While this code may answer the question, providing additional context regarding how and/or why it solves the problem would improve the answer's long-term value. You can find more information on how to write good answers in the help center: stackoverflow.com/help/how-to-answer . Good luck

ANKIT NAYAK · Accepted Answer · 2024-12-28 05:36:31Z

To fix the Webpack build error caused by cssnano during CSS optimization, you can temporarily disable minimization.

Add this to your next.config.ts

webpack: (config) => { config.optimization.minimize = false; return config; },

This resolved the issue for me, but it’s only a temporary fix.

Finnalandem · Accepted Answer · 2022-10-28 05:33:00Z

I believe I was having the same issue you are currently experiencing not too long ago. My solution came from reorganizing the path that my node files were installed. I installed my node files to a greater hierarchy in the path then created a new folder down the line to hold my project files so that the files were already somewhere in the path. Alternatively, you could try installing globally with npm install -g yarn

Hope this helps! :)

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

Collectives™ on Stack Overflow

Build failed because of webpack errors

4 Answers 4

2 Comments

1 Comment

Comments

1 Comment

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

2 Comments

1 Comment

Comments

1 Comment

Linked

Related