[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [Help](/c/help/9) # Facing issue with vercel next deployment 103 views · 0 likes · 5 posts Abhishekmadoliya 6412 (@abhishekmadoliya-641) · 2025-10-21 i was trying to host the next project on vercel and facing a weird build error only in vercel build process . \- /vercel/path0/client/node_modules/next/dist/compiled/jest-worker/processChild.js at Function.<anonymous> (node:internal/modules/cjs/loader:1383:15) at /vercel/path0/client/node_modules/next/dist/server/require-hook.js:57:36 at defaultResolveImpl (node:internal/modules/cjs/loader:1025:19) at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1030:22) at Function.\_load (node:internal/modules/cjs/loader:1192:37) at TracingChannel.traceSync (node:diagnostics_channel:322:14) at wrapModuleLoad (node:internal/modules/cjs/loader:237:24) at Module.<anonymous> (node:internal/modules/cjs/loader:1463:12) at mod.require (/vercel/path0/client/node_modules/next/dist/server/require-hook.js:68:28) at require (node:internal/modules/helpers:147:16) \> Build failed because of webpack errors Error: Command "npm run build" exited with 1 please help Anshuman Bhardwaj (@anshumanb) · 2025-10-21 Hi @abhishekmadoliya-641, welcome to the Vercel Community! What happens when you run `npm run build` and `vercel build` commands locally? Can you run both and share the outcome here? If possible, please share your public repo or a [minimal reproducible example](https://vercel.com/guides/creating-a-minimal-reproducible-example). That will let us all work together from the same code to figure out what’s going wrong. Abhishekmadoliya 6412 (@abhishekmadoliya-641) · 2025-10-21 hi , here an local build output: ``` Creating an optimized production build … ✓ Compiled successfully in 23.6s Skipping validation of types ./src/app/global-error.tsx 4:3 Warning: ‘error’ is defined but never used. @typescript-eslint/no-unused-vars ./src/app/policy-wallet/page.js 2:8 Warning: ‘Link’ is defined but never used. @typescript-eslint/no-unused-vars 15:3 Warning: ‘Filter’ is defined but never used. @typescript-eslint/no-unused-vars 23:20 Warning: ‘setPolicies’ is assigned a value but never used. @typescript-eslint/no-unused-vars ./src/app/whatsapp/page.js 12:3 Warning: ‘X’ is defined but never used. @typescript-eslint/no-unused-vars 17:10 Warning: ‘isChatOpen’ is assigned a value but never used. @typescript-eslint/no-unused-vars 17:22 Warning: ‘setIsChatOpen’ is assigned a value but never used. @typescript-eslint/no-unused-vars ./src/components/footer-03/Footer.tsx 67:7 Warning: ‘stats’ is assigned a value but never used. @typescript-eslint/no-unused-vars ./src/components/logindemo.js 27:9 Warning: ‘auth’ is assigned a value but never used. @typescript-eslint/no-unused-vars 29:10 Warning: ‘loading’ is assigned a value but never used. @typescript-eslint/no-unused-vars 55:18 Warning: ‘err’ is defined but never used. @typescript-eslint/no-unused-vars ./src/components/user/auth/Register.tsx 1:10 Warning: ‘cn’ is defined but never used. @typescript-eslint/no-unused-vars 18:3 Warning: ‘className’ is defined but never used. @typescript-eslint/no-unused-vars 19:6 Warning: ‘props’ is defined but never used. @typescript-eslint/no-unused-vars ./src/components/user2/Footer.js 1:8 Warning: ‘Image’ is defined but never used. @typescript-eslint/no-unused-vars 3:8 Warning: ‘styles’ is defined but never used. @typescript-eslint/no-unused-vars ./src/redux/store.ts 6:15 Warning: ‘Store’ is defined but never used. @typescript-eslint/no-unused-vars info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/app/api-reference/config/eslint#disabling-rules ✓ Linting ✓ Collecting page data comparisondata null ✓ Generating static pages (20/20) ✓ Collecting build traces ✓ Finalizing page optimization Route (app) Size First Load JS ┌ ○ / 38.4 kB 170 kB ├ ○ /\_not-found 998 B 103 kB ├ ƒ /\[category\] 1.8 kB 116 kB ├ ○ /about 716 B 103 kB ├ ○ /advisor-call 48.2 kB 158 kB ├ ○ /blog 3.78 kB 111 kB ├ ○ /claim-support 139 B 102 kB ├ ○ /compare 1.88 kB 108 kB ├ ○ /contactus 139 B 102 kB ├ ƒ /insurance-plan/\[planName\] 9.46 kB 119 kB ├ ○ /learn 3.27 kB 105 kB ├ ○ /login 4.77 kB 145 kB ├ ○ /plan 139 B 102 kB ├ ○ /policy-wallet 6.09 kB 111 kB ├ ○ /privacy 489 B 108 kB ├ ○ /recommendation 12.8 kB 123 kB ├ ○ /recommendation/answer 1.09 kB 144 kB ├ ○ /register 1.63 kB 120 kB ├ ○ /sheet 139 B 102 kB └ ○ /whatsapp 4.64 kB 107 kB * First Load JS shared by all 102 kB ├ chunks/1255-1622f43a1c0ebec5.js 45.7 kB ├ chunks/4bd1b696-f785427dddbba9fb.js 54.2 kB └ other shared chunks (total) 2.01 kB Route (pages) Size First Load JS ┌ /\_app 0 B 102 kB └ ○ /404 (1307 ms) 2.62 kB 105 kB * First Load JS shared by all 121 kB ├ chunks/framework-b9fffb5537caa07c.js 57.7 kB ├ chunks/main-ba5fb30c992d4dcb.js 34.9 kB ├ css/1cdd2d0f9e23f8af.css 19.1 kB └ other shared chunks (total) 9.42 kB ○ (Static) prerendered as static content ƒ (Dynamic) server-rendered on demand ``` and now here an vercel build output: ``` - /vercel/path0/client/node_modules/next/dist/compiled/jest-worker/processChild.js at Function.<anonymous> (node:internal/modules/cjs/loader:1383:15) at /vercel/path0/client/node_modules/next/dist/server/require-hook.js:57:36 at defaultResolveImpl (node:internal/modules/cjs/loader:1025:19) at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1030:22) at Function.\_load (node:internal/modules/cjs/loader:1192:37) at TracingChannel.traceSync (node:diagnostics_channel:322:14) at wrapModuleLoad (node:internal/modules/cjs/loader:237:24) at Module.<anonymous> (node:internal/modules/cjs/loader:1463:12) at mod.require (/vercel/path0/client/node_modules/next/dist/server/require-hook.js:68:28) at require (node:internal/modules/helpers:147:16) \> Build failed because of webpack errors Error: Command "npm run build" exited with 1 ``` Anshuman Bhardwaj (@anshumanb) · 2025-10-21 I see. Can you share the `package.json`, next config and vercel.json here? My first suggestion would be to remove all `node_modules` and reinstall everything. Update the packages to their latest patch version and see if this fixes. Related: https://github.com/vercel/next.js/discussions/66234 system (@system) · 2026-01-20 Hi @abhishekmadoliya-641! 🙂 We haven't heard back from you. If you're still stuck, feel free to share any updates, logs, or additional context that might help us assist you better!