Getting error while running build command (Nextjs)

Umang_001 · November 27, 2024, 2:35pm

Below is the error me and my team is facing while creating build.

Error :-

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.

module.exports = {
  webpack: (config, { isServer }) => {
    if (!isServer) {
      config.resolve.fallback = {
        ...config.resolve.fallback,
        child_process: false, // Mock 'child_process'
      };
    }
    return config;
  },
};

manish-sharma · November 27, 2024, 4:16pm

Hello @Umang_001,

Could you confirm the dev-tools version you are using currently?

Umang_001 · November 27, 2024, 4:17pm

@builder.io/dev-tools": “^1.1.24”,

manish-sharma · November 27, 2024, 4:19pm

Hi @Umang_001,

Could you try upgrading to the latest version(1.1.40) and see if that helps?

Umang_001 · November 27, 2024, 4:21pm

I don’t think it’s version specific issue!

manish-sharma · November 27, 2024, 4:26pm

Can you try using different version of node?

manish-sharma · November 28, 2024, 10:36am

Hello @Umang_001,

Wanted to check if this is still an issue?

Umang_001 · December 19, 2024, 5:51am

nope we have resolved this issue!

productshare · February 17, 2025, 2:51am

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)

Umang_001 · February 18, 2025, 11:18am

/** @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?

juniorDinnka · February 18, 2025, 4:03pm

I’m running into the exact same problems with a Vite React app. Any tips on how I could solve it?

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"),
    },
  },
});

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.

Maxii · February 23, 2025, 4:31pm

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.

polaris13 · March 3, 2025, 3:30pm

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 again and had the same issue later.

Topic		Replies	Views
Can no longer access builder visual editor or localhost on dev server - iframe doesn't exist Technical Questions visual-editor , nextjs	3	331	September 12, 2023
Builder.io/dev-tools/next has no default export - error with Nextjs 15 General	15	113	December 16, 2024
Integration CLI Error - Next.js - james Technical Questions integration , nextjs	1	273	July 5, 2023
Error in nextjs production build (Just in production) Technical Questions nextjs	11	5803	March 15, 2022
Builder page cannot be displayed Bugs visual-editor , nextjs	2	496	September 18, 2023

Getting error while running build command (Nextjs)

Related topics