# Getting error while running build command (Nextjs) **URL:** \ **Category:** General\ **Tags:** visual-editor, nextjs\ **Created:** [November 27, 2024, 2:35pm UTC](https://forum.builder.io/t/getting-error-while-running-build-command-nextjs/6835 "2024-11-27T14:35:57Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Umang\_001](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.builder.io/umang_001/32/4296_2.png) [@Umang\_001](https://forum.builder.io/u/Umang_001)\ **Post date:** [November 27, 2024, 2:35pm UTC](https://forum.builder.io/t/getting-error-while-running-build-command-nextjs/6835/1 "2024-11-27T14:35:57Z")
Below is the error me and my team is facing while creating build. Error :- ```auto Error: Dynamic require of "child_process" is not supported at file:///app/node_modules/@builder.io/dev-tools/node/index.mjs:1:383 at file:///app/node_modules/@builder.io/dev-tools/node/index.mjs:8:58753 at file:///app/node_modules/@builder.io/dev-tools/node/index.mjs:1:459 at file:///app/node_modules/@builder.io/dev-tools/node/index.mjs:104:1662 at ModuleJob.run (node:internal/modules/esm/module_job:234:25) at async ModuleLoader.import (node:internal/modules/esm/loader:473:24) at async loadConfig (/app/node_modules/next/dist/server/config.js:711:36) at async Module.nextDev (/app/node_modules/next/dist/cli/next-dev.js:175:14) ``` this is builder specific error which due to `@builder.io/dev-tools` which is using `child_process` which is Nodejs core module. anyone have idea how we can fix this ? we have already tried below approch modifying `next.config.mjs` file. ```auto module.exports = { webpack: (config, { isServer }) => { if (!isServer) { config.resolve.fallback = { ...config.resolve.fallback, child_process: false, // Mock 'child_process' }; } return config; }, }; ``` ---
**Author:** ![manish-sharma](https://avatars.discourse-cdn.com/v4/letter/m/8797f3/32.png) [@manish-sharma](https://forum.builder.io/u/manish-sharma)\ **Post date:** [November 27, 2024, 4:16pm UTC](https://forum.builder.io/t/getting-error-while-running-build-command-nextjs/6835/2 "2024-11-27T16:16:43Z")
Hello @Umang_001, Could you confirm the dev-tools version you are using currently? > **[@builder.io/dev-tools](https://www.npmjs.com/package/@builder.io/dev-tools?activeTab=versions)** > > Builder.io Visual CMS Devtools. Latest version: 1.1.40, last published: 21 minutes ago. Start using @builder.io/dev-tools in your project by running \`npm i @builder.io/dev-tools\`. There are 3 other projects in the npm registry using... ---
**Author:** ![Umang\_001](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.builder.io/umang_001/32/4296_2.png) [@Umang\_001](https://forum.builder.io/u/Umang_001)\ **Post date:** [November 27, 2024, 4:17pm UTC](https://forum.builder.io/t/getting-error-while-running-build-command-nextjs/6835/3 "2024-11-27T16:17:36Z")
@builder.io/dev-tools": “^1.1.24”, ---
**Author:** ![manish-sharma](https://avatars.discourse-cdn.com/v4/letter/m/8797f3/32.png) [@manish-sharma](https://forum.builder.io/u/manish-sharma)\ **Post date:** [November 27, 2024, 4:19pm UTC](https://forum.builder.io/t/getting-error-while-running-build-command-nextjs/6835/4 "2024-11-27T16:19:41Z")
Hi @Umang_001, Could you try upgrading to the latest version(1.1.40) and see if that helps? > **[@builder.io/dev-tools](https://www.npmjs.com/package/@builder.io/dev-tools/v/1.1.40)** > > Builder.io Visual CMS Devtools. Latest version: 1.1.40, last published: 24 minutes ago. Start using @builder.io/dev-tools in your project by running \`npm i @builder.io/dev-tools\`. There are 3 other projects in the npm registry using... ---
**Author:** ![Umang\_001](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.builder.io/umang_001/32/4296_2.png) [@Umang\_001](https://forum.builder.io/u/Umang_001)\ **Post date:** [November 27, 2024, 4:21pm UTC](https://forum.builder.io/t/getting-error-while-running-build-command-nextjs/6835/5 "2024-11-27T16:21:13Z")
I don’t think it’s version specific issue! ---
**Author:** ![manish-sharma](https://avatars.discourse-cdn.com/v4/letter/m/8797f3/32.png) [@manish-sharma](https://forum.builder.io/u/manish-sharma)\ **Post date:** [November 27, 2024, 4:26pm UTC](https://forum.builder.io/t/getting-error-while-running-build-command-nextjs/6835/6 "2024-11-27T16:26:14Z")
Can you try using different version of node? ---
**Author:** ![manish-sharma](https://avatars.discourse-cdn.com/v4/letter/m/8797f3/32.png) [@manish-sharma](https://forum.builder.io/u/manish-sharma)\ **Post date:** [November 28, 2024, 10:36am UTC](https://forum.builder.io/t/getting-error-while-running-build-command-nextjs/6835/7 "2024-11-28T10:36:14Z")
Hello @Umang_001, Wanted to check if this is still an issue? ---
**Author:** ![Umang\_001](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.builder.io/umang_001/32/4296_2.png) [@Umang\_001](https://forum.builder.io/u/Umang_001)\ **Post date:** [December 19, 2024, 5:51am UTC](https://forum.builder.io/t/getting-error-while-running-build-command-nextjs/6835/8 "2024-12-19T05:51:17Z")
nope we have resolved this issue! ---
**Author:** ![productshare](https://avatars.discourse-cdn.com/v4/letter/p/7feea3/32.png) [@productshare](https://forum.builder.io/u/productshare)\ **Post date:** [February 17, 2025, 2:51am UTC](https://forum.builder.io/t/getting-error-while-running-build-command-nextjs/6835/9 "2025-02-17T02:51:30Z")
I am experiencing the same exact error on a next 15 app. And strangely I have it working in another app just fine. Totally baffling. Any help would be much appreciated Error: Dynamic require of “child\_process” is not supported at file:///Users/anton/WebstormProjects/chadnext/node\_modules/.pnpm/@builder.io+dev-tools@1.5.12/node\_modules/@builder.io/dev-tools/server/index.mjs:1:383 at file:///Users/anton/WebstormProjects/chadnext/node\_modules/.pnpm/@builder.io+dev-tools@1.5.12/node\_modules/@builder.io/dev-tools/server/index.mjs:14:12184 at file:///Users/anton/WebstormProjects/chadnext/node\_modules/.pnpm/@builder.io+dev-tools@1.5.12/node\_modules/@builder.io/dev-tools/server/index.mjs:1:459 at file:///Users/anton/WebstormProjects/chadnext/node\_modules/.pnpm/@builder.io+dev-tools@1.5.12/node\_modules/@builder.io/dev-tools/server/index.mjs:1292:136 at ModuleJob.run (node:internal/modules/esm/module\_job:268:25) at async onImport.tracePromise. **proto** (node:internal/modules/esm/loader:543:26) at async loadConfig (/Users/anton/WebstormProjects/chadnext/node\_modules/.pnpm/next@15.0.3\_@babel+core@7.24.5\_react-dom@18.3.1\_react@18.3.1\_\_react@18.3.1/node\_modules/next/dist/server/config.js:768:36) at async Module.nextDev (/Users/anton/WebstormProjects/chadnext/node\_modules/.pnpm/next@15.0.3\_@babel+core@7.24.5\_react-dom@18.3.1\_react@18.3.1\_\_react@18.3.1/node\_modules/next/dist/cli/next-dev.js:190:14) ---
**Author:** ![Umang\_001](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.builder.io/umang_001/32/4296_2.png) [@Umang\_001](https://forum.builder.io/u/Umang_001)\ **Post date:** [February 18, 2025, 11:18am UTC](https://forum.builder.io/t/getting-error-while-running-build-command-nextjs/6835/10 "2025-02-18T11:18:12Z")
```auto /** @type {import('next').NextConfig} */ const baseConfig = { images: { dangerouslyAllowSVG: true, remotePatterns: [ { protocol: "https", hostname: "cdn.builder.io", }, { protocol: "https", hostname: "forge-saleor-dev.s3.amazonaws.com", }, ], }, }; let nextConfig = baseConfig; if (process.env.NEXT_PUBLIC_NODE_ENV === "dev") { console.log("Loading BuilderDevTools for development"); import("@builder.io/dev-tools/next").then((BuilderDevTools) => { nextConfig = BuilderDevTools.default()(baseConfig); }); // Lazy-load } export default nextConfig; ``` Try this way for importing module dynamically. Let me know if this works for you? ---
**Author:** ![juniorDinnka](https://avatars.discourse-cdn.com/v4/letter/j/b487fb/32.png) [@juniorDinnka](https://forum.builder.io/u/juniorDinnka)\ **Post date:** [February 18, 2025, 4:03pm UTC](https://forum.builder.io/t/getting-error-while-running-build-command-nextjs/6835/11 "2025-02-18T16:03:45Z")
I’m running into the exact same problems with a Vite React app. Any tips on how I could solve it? ```auto import { defineConfig, normalizePath } from "vite"; import react from "@vitejs/plugin-react-swc"; import path from "path"; import { viteStaticCopy } from "vite-plugin-static-copy"; import { builderDevTools } from "@builder.io/dev-tools/vite"; import { createRequire } from "module"; const require = createRequire(import.meta.url); const pdfjsDistPath = path.dirname(require.resolve("pdfjs-dist/package.json")); const cMapsDir = normalizePath(path.join(pdfjsDistPath, "cmaps")); // https://vite.dev/config/ export default defineConfig({ plugins: [ react(), viteStaticCopy({ targets: [ { src: cMapsDir, dest: "", }, ], }), builderDevTools(), ], resolve: { alias: { "@": path.resolve(__dirname, "./src"), }, }, }); ``` ```auto C:\projects\Dinnka\bookkeeping-portal-frontend git:[development] pnpm dev > bookkeeping-portal-frontend@0.0.0 dev C:\projects\Dinnka\bookkeeping-portal-frontend > vite failed to load config from C:\projects\Dinnka\bookkeeping-portal-frontend\vite.config.ts error when starting dev server: Error: Dynamic require of "child_process" is not supported at file:///C:/projects/Dinnka/bookkeeping-portal-frontend/node_modules/.pnpm/@builder.io+dev-tools@1.5.14/node_modules/@builder.io/dev-tools/server/index.mjs:1:383 at file:///C:/projects/Dinnka/bookkeeping-portal-frontend/node_modules/.pnpm/@builder.io+dev-tools@1.5.14/node_modules/@builder.io/dev-tools/server/index.mjs:14:12184 at file:///C:/projects/Dinnka/bookkeeping-portal-frontend/node_modules/.pnpm/@builder.io+dev-tools@1.5.14/node_modules/@builder.io/dev-tools/server/index.mjs:1:459 at file:///C:/projects/Dinnka/bookkeeping-portal-frontend/node_modules/.pnpm/@builder.io+dev-tools@1.5.14/node_modules/@builder.io/dev-tools/server/index.mjs:1284:136 at ModuleJob.run (node:internal/modules/esm/module_job:271:25) at async onImport.tracePromise. __proto__ (node:internal/modules/esm/loader:578:26) at async loadConfigFromBundledFile (file:///C:/projects/Dinnka/bookkeeping-portal-frontend/node_modules/.pnpm/vite@6.0.5_@types+node@22.10.5_jiti@1.21.7_yaml@2.6.1/node_modules/vite/dist/node/chunks/dep-BZMjGe_U.js:53862:15) at async loadConfigFromFile (file:///C:/projects/Dinnka/bookkeeping-portal-frontend/node_modules/.pnpm/vite@6.0.5_@types+node@22.10.5_jiti@1.21.7_yaml@2.6.1/node_modules/vite/dist/node/chunks/dep-BZMjGe_U.js:53691:24) at async resolveConfig (file:///C:/projects/Dinnka/bookkeeping-portal-frontend/node_modules/.pnpm/vite@6.0.5_@types+node@22.10.5_jiti@1.21.7_yaml@2.6.1/node_modules/vite/dist/node/chunks/dep-BZMjGe_U.js:53214:24) at async _createServer (file:///C:/projects/Dinnka/bookkeeping-portal-frontend/node_modules/.pnpm/vite@6.0.5_@types+node@22.10.5_jiti@1.21.7_yaml@2.6.1/node_modules/vite/dist/node/chunks/dep-BZMjGe_U.js:43529:18) ELIFECYCLE Command failed with exit code 1. ``` ---
**Author:** ![Maxii](https://avatars.discourse-cdn.com/v4/letter/m/7ea924/32.png) [@Maxii](https://forum.builder.io/u/Maxii)\ **Post date:** [February 23, 2025, 4:31pm UTC](https://forum.builder.io/t/getting-error-while-running-build-command-nextjs/6835/12 "2025-02-23T16:31:16Z")
This means that @builder.io/dev-tools is attempting to use the Node.js child\_process module in an environment where it is not supported. **Possible Causes:** • Vite operates as an ESM (ECMAScript Modules) environment. • @builder.io/dev-tools is trying to use a CommonJS module (require). • Dynamic require calls are not supported in an ESM environment. **Technical Explanation:** • Vite uses native ES modules for better performance. • child\_process is a built-in Node.js module that is not available in a browser environment. • @builder.io/dev-tools is attempting to execute server-side code on the client. ---
**Author:** ![polaris13](https://avatars.discourse-cdn.com/v4/letter/p/e56c9b/32.png) [@polaris13](https://forum.builder.io/u/polaris13)\ **Post date:** [March 3, 2025, 3:30pm UTC](https://forum.builder.io/t/getting-error-while-running-build-command-nextjs/6835/13 "2025-03-03T15:30:16Z")
The solution that worked for me was using `npx patch-package` to modify index.mjs then save the modification as a patch in case I needed to install [builder.io](http://builder.io) again and had the same issue later.