turbo: [WEB-964] [Turbopack] Error resolving commonjs request

Any news on this? Removing tsconfig.json does not seem like an optimal fix.

Came here looking to see if anyone else had the same issue. Also get these using next dev turbo --show-all after trying upgrading a next 12 project to 13. With next dev and no turbo, everything ok.

event - initial compilation 7.082ms
error - [resolve]
  node_modules/source-map-support/source-map-support.js
    Error resolving commonjs request
    unable to resolve module "fs"

    Error resolving commonjs request
    unable to resolve module "path"

  node_modules/typescript/lib/typescript.js
    Error resolving commonjs request
    unable to resolve dynamic

    Error resolving commonjs request
    unable to resolve dynamic or dynamic or relative "./node_modules/@microsoft/typescript-etw"

    Error resolving commonjs request
    unable to resolve module "crypto"

    Error resolving commonjs request
    unable to resolve module "fs"

    Error resolving commonjs request
    unable to resolve module "inspector"

    Error resolving commonjs request
    unable to resolve module "os"

    Error resolving commonjs request
    unable to resolve module "path"

    Error resolving commonjs request
    unable to resolve module "perf_hooks"

Had the same issue, removing my tsconfig.json file seemed to resolve the issue.

In the new learn of nextjs, if you dev start command with --turbo, calling await fetchRevenue in the example will report the same error. https://nextjs.org/learn/dashboard-app/fetching-data

nextjs version 14

yarn dev --turbo is also failing for me on next 14

Came here looking to see if anyone else had the same issue. Also get these using next dev turbo --show-all after trying upgrading a next 12 project to 13. With next dev and no turbo, everything ok.

event - initial compilation 7.082ms
error - [resolve]
  node_modules/source-map-support/source-map-support.js
    Error resolving commonjs request
    unable to resolve module "fs"

    Error resolving commonjs request
    unable to resolve module "path"

  node_modules/typescript/lib/typescript.js
    Error resolving commonjs request
    unable to resolve dynamic

    Error resolving commonjs request
    unable to resolve dynamic or dynamic or relative "./node_modules/@microsoft/typescript-etw"

    Error resolving commonjs request
    unable to resolve module "crypto"

    Error resolving commonjs request
    unable to resolve module "fs"

    Error resolving commonjs request
    unable to resolve module "inspector"

    Error resolving commonjs request
    unable to resolve module "os"

    Error resolving commonjs request
    unable to resolve module "path"

    Error resolving commonjs request
    unable to resolve module "perf_hooks"

Hey all, we’ve been making a lot of progress on these types of issues over the last 3 weeks. I just ran the /learn application and it now compiles correctly whereas it errored on 14.0.3. Please give npm install next@canary try. Based on the comments in this issue everyone was running into different issues. If you’re still running into issues please open a new issue with a reproduction so that we can investigate and fix the particular case that you’re running into.

Thanks!

Next.js has greatly enhanced the full-stack development experience for many. It’s hard to dispute Vercel’s success in this regard.

However, I do wish Next.js had opted for a more established development runner and compiler, such as Vite with ESBuild. The development experience I’ve had with Vite projects, particularly in terms of cold starts and hot reloads during development, is notably superior, 12 seconds for initial load with Turbo versus instant >50ms with Vite.

Additionally, the compilation time and resource requirements are substantially lower with Vite.

Is there any chance Next.js might consider adopting Vite in the future, or is that possibility unlikely?

After 13 monthes of reporting the issue. It still hasn’t been resolved!

@ringblaze/web:dev:  X ModuleBuildError: error - node_modules/.pnpm/xmlhttprequest@1.8.0/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:503:22  Error resolving commonjs request
@ringblaze/web:dev: 
@ringblaze/web:dev:   501 |         + "req.end();";
@ringblaze/web:dev:   502 |       // Start the other Node Process, executing this string
@ringblaze/web:dev: > 503 |       var syncProc = spawn(process.argv[0], ["-e", execString]);
@ringblaze/web:dev:       |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@ringblaze/web:dev:   504 |       while(fs.existsSync(syncFile)) {
@ringblaze/web:dev:   505 |         // Wait while the sync file is empty
@ringblaze/web:dev:   506 |       }
@ringblaze/web:dev: unable to resolve module "-e" or dynamic
@ringblaze/web:dev: It was not possible to find the requested file.

Same for us

Also getting this on the latest version 13.4.13:

error - [resolve] [project]/node_modules/xmlhttprequest-ssl/lib/XMLHttpRequest.js  /node_modules/xmlhttprequest-ssl/lib/XMLHttpRequest.js:540:22  Error resolving commonjs request
     536 |         + "});"
     537 |         + (data ? "req.write('" + JSON.stringify(data).slice(1,-1).replace(/'/g, "\\'") + "');":"")
     538 |         + "req.end();";
     539 |       // Start the other Node Process, executing this string
         +                       v----------------------------------------v
     540 +       var syncProc = spawn(process.argv[0], ["-e", execString]);
         +                       ^----------------------------------------^
     541 |       var statusText;
     542 |       while(fs.existsSync(syncFile)) {
     543 |         // Wait while the sync file is empty
     544 |       }
  
  unable to resolve module "-e" or dynamic
  
  | It was not possible to find the requested file.
  | Parsed request as written in source code: module "-e" or dynamic
  | Path where resolving has started: [project]/node_modules/xmlhttprequest-ssl/lib/XMLHttpRequest.js
  | Type of request: commonjs request
  | Import map: No import map entry
  | 

I also have the same problem on next 14

Same here :

error - [resolve] [project]/node_modules/node-gyp-build/node-gyp-build.js  /node_modules/node-gyp-build/node-gyp-build.js:22:10  Error resolving commonjs request
      18 | 
      19 | module.exports = load
      20 | 
      21 | function load (dir) {
         |           v-------------------------------
      22 +   return runtimeRequire(load.resolve(dir))
      23 + }
         +-
      24 | 
      25 | load.resolve = load.path = function (dir) {
      26 |   dir = path.resolve(dir || '.')
      27 | 
  
  unable to resolve dynamic
  
  | It was not possible to find the requested file.
  | Parsed request as written in source code: dynamic
  | Path where resolving has started: [project]/node_modules/node-gyp-build/node-gyp-build.js
  | Type of request: commonjs request
  | Import map: No import map entry
  | 

Nice, I’m no longer seeing this error in 14.0.4-canary.28!

Honestly Vercel has become a joke – I’ve used Next.JS since the very beginning and I’ve seen a huge downgrade in performance and community support in addressing these types of issues.

link @timneutkens from your comments there, i tried using turbopack but this issue is blocking me to run next dev --turbo. I hope and trust you guys will resolve this. but this issue stands for over an year here. this is the exact error i am now seeing. Error resolving EcmaScript Modules request unable to resolve module "fs" It was not possible to find the requested file. Parsed request as written in source code: module "fs" Path where resolving has started: [project]/node_modules/@aws-sdk/credential-provider-web-identity/dist-es/fromTokenFile.js Type of request: EcmaScript Modules request Import map: No import map entry

hey any update on this issue? I’m having the same errors

error - [resolve] node_modules/.pnpm/opener@1.5.2/node_modules/opener/lib/opener.js
  node_modules/.pnpm/opener@1.5.2/node_modules/opener/lib/opener.js:65:12  Error resolving commonjs request
      61 |         });
      62 |         args = ["/c", "start", "\"\""].concat(args);
      63 |     }
      64 | 
         +             v-----------------------------------------------------v
      65 +     return childProcess.execFile(command, args, options, callback);
         +             ^-----------------------------------------------------^
      66 | };
      67 | 
  
  unable to resolve dynamic or dynamic or dynamic

warning -
  [parse]
    node_modules/.pnpm/gzip-size@6.0.0/node_modules/gzip-size/index.js
      node_modules/.pnpm/gzip-size@6.0.0/node_modules/gzip-size/index.js:49:17  lint TP1004 fs.createReadStream(???*0*) is very dynamic
          45 | };
          46 | 
          47 | module.exports.file = (path, options) => {
          48 | 	return new Promise((resolve, reject) => {
             +                  v
          49 + 		const stream = fs.createReadStream(path);
             +                  ^
          50 | 		stream.on('error', reject);
          51 | 
          52 | 		const gzipStream = stream.pipe(module.exports.stream(options));
          53 | 		gzipStream.on('error', reject);
      
      - *0* path
        ⚠️  pattern without value

      node_modules/.pnpm/gzip-size@6.0.0/node_modules/gzip-size/index.js:58:65  lint TP1004 fs.readFileSync(???*0*) is very dynamic
          54 | 		gzipStream.on('gzip-size', resolve);
          55 | 	});
          56 | };
          57 | 
             +                                                                  v
          58 + module.exports.fileSync = (path, options) => module.exports.sync(fs.readFileSync(path), options);
             +                                                                  ^
          59 | 
      
      - *0* path
        ⚠️  pattern without value

    node_modules/.pnpm/opener@1.5.2/node_modules/opener/lib/opener.js
      node_modules/.pnpm/opener@1.5.2/node_modules/opener/lib/opener.js:65:11  lint TP1005 child_process.execFile(
          61 |         });
          62 |         args = ["/c", "start", "\"\""].concat(args);
          63 |     }
          64 | 
             +            v
          65 +     return childProcess.execFile(command, args, options, callback);
             +            ^
          66 | };
          67 | 
      
          (???*0* | "cmd.exe" | "open" | "xdg-open" | ???*1* | FreeVar(undefined) | ???*3*),
          (???*4* | [???*5*] | ???*6* | ???*9*),
          (???*11* | {}),
          (???*12* | {})
      ) is very dynamic
      - *0* command
        ⚠️  pattern without value
      - *1* ???*2*["command"]
        ⚠️  unknown object
      - *2* arguments[1]
        ⚠️  function calls are not analysed yet
      - *3* unknown mutation
      - *4* arguments[0]
        ⚠️  function calls are not analysed yet
      - *5* args
        ⚠️  circular variable reference
      - *6* ???*7*(???*8*)
        ⚠️  unknown callee
      - *7* [(??? | FreeVar(undefined) | ???)]["concat"]
        ⚠️  non-num constant property on array
      - *8* args
        ⚠️  circular variable reference
      - *9* ???*10*["map"](*anonymous function 2149*)
        ⚠️  unknown callee object
      - *10* args
        ⚠️  circular variable reference
      - *11* arguments[1]
        ⚠️  function calls are not analysed yet
      - *12* arguments[2]
        ⚠️  function calls are not analysed yet

    node_modules/.pnpm/sirv@1.0.19/node_modules/sirv/build.js
      node_modules/.pnpm/sirv@1.0.19/node_modules/sirv/build.js:43:29  lint TP1004 fs.existsSync((???*0* | ???*1*)) is very dynamic
          39 | 	let i=0, arr=toAssume(uri, extns);
          40 | 	let abs, stats, name, headers;
          41 | 	for (; i < arr.length; i++) {
          42 | 		abs = normalize(join(dir, name=arr[i]));
             +                              v
          43 + 		if (abs.startsWith(dir) && fs.existsSync(abs)) {
             +                              ^
          44 | 			stats = fs.statSync(abs);
          45 | 			if (stats.isDirectory()) continue;
          46 | 			headers = toHeaders(name, stats, isEtag);
          47 | 			headers['Cache-Control'] = isEtag ? 'no-cache' : 'no-store';
      
      - *0* abs
        ⚠️  pattern without value
      - *1* ???*2*(join(dir, ???*4*))
        ⚠️  unknown callee
      - *2* path*3*["normalize"]
        ⚠️  unsupported property on Node.js path module
      - *3* path: The Node.js path module: https://nodejs.org/api/path.html
      - *4* unsupported expression

      node_modules/.pnpm/sirv@1.0.19/node_modules/sirv/build.js:44:11  lint TP1004 fs.statSync((???*0* | ???*1*)) is very dynamic
          40 | 	let abs, stats, name, headers;
          41 | 	for (; i < arr.length; i++) {
          42 | 		abs = normalize(join(dir, name=arr[i]));
          43 | 		if (abs.startsWith(dir) && fs.existsSync(abs)) {
             +            v
          44 + 			stats = fs.statSync(abs);
             +            ^
          45 | 			if (stats.isDirectory()) continue;
          46 | 			headers = toHeaders(name, stats, isEtag);
          47 | 			headers['Cache-Control'] = isEtag ? 'no-cache' : 'no-store';
          48 | 			return { abs, stats, headers };
      
      - *0* abs
        ⚠️  pattern without value
      - *1* ???*2*(join(dir, ???*4*))
        ⚠️  unknown callee
      - *2* path*3*["normalize"]
        ⚠️  unsupported property on Node.js path module
      - *3* path: The Node.js path module: https://nodejs.org/api/path.html
      - *4* unsupported expression

      node_modules/.pnpm/sirv@1.0.19/node_modules/sirv/build.js:88:1  lint TP1004 fs.createReadStream(???*0*, {}) is very dynamic
          84 | 		headers['Accept-Ranges'] = 'bytes';
          85 | 	}
          86 | 
          87 | 	res.writeHead(code, headers);
             +  v
          88 + 	fs.createReadStream(file, opts).pipe(res);
             +  ^
          89 | }
          90 | 
          91 | const ENCODING = {
          92 | 	'.br': 'br',
      
      - *0* arguments[2]
        ⚠️  function calls are not analysed yet

    node_modules/.pnpm/webpack-bundle-analyzer@4.7.0/node_modules/webpack-bundle-analyzer/lib/analyzer.js
      node_modules/.pnpm/webpack-bundle-analyzer@4.7.0/node_modules/webpack-bundle-analyzer/lib/analyzer.js:179:20  lint TP1004 fs.readFileSync(???*0*, "utf8") is very dynamic
         175 |   });
         176 | }
         177 | 
         178 | function readStatsFromFile(filename) {
             +                     v
         179 +   return JSON.parse(fs.readFileSync(filename, 'utf8'));
             +                     ^
         180 | }
         181 | 
         182 | function getChildAssetBundles(bundleStats, assetName) {
         183 |   return (bundleStats.children || []).find(c => _(c.assetsByChunkName).values().flatten().includes(assetName));
      
      - *0* arguments[0]
        ⚠️  function calls are not analysed yet

    node_modules/.pnpm/webpack-bundle-analyzer@4.7.0/node_modules/webpack-bundle-analyzer/lib/parseUtils.js
      node_modules/.pnpm/webpack-bundle-analyzer@4.7.0/node_modules/webpack-bundle-analyzer/lib/parseUtils.js:16:18  lint TP1004 fs.readFileSync(???*0*, "utf8") is very dynamic
          12 |   parseBundle
          13 | };
          14 | 
          15 | function parseBundle(bundlePath) {
             +                   v
          16 +   const content = fs.readFileSync(bundlePath, 'utf8');
             +                   ^
          17 |   const ast = acorn.parse(content, {
          18 |     sourceType: 'script',
          19 |     // I believe in a bright future of ECMAScript!
          20 |     // Actually, it's set to `2050` to support the latest ECMAScript version that currently exists.
      
      - *0* arguments[0]
        ⚠️  function calls are not analysed yet

  [resolve]
    node_modules/.pnpm/ws@7.5.9/node_modules/ws/lib/buffer-util.js
      node_modules/.pnpm/ws@7.5.9/node_modules/ws/lib/buffer-util.js:105:22  Error resolving commonjs request
         101 |   return buf;
         102 | }
         103 | 
         104 | try {
             +                       v-------------------v
         105 +   const bufferUtil = require('bufferutil');
             +                       ^-------------------^
         106 |   const bu = bufferUtil.BufferUtil || bufferUtil;
         107 | 
         108 |   module.exports = {
         109 |     concat,
      
      unable to resolve module "bufferutil"

    node_modules/.pnpm/ws@7.5.9/node_modules/ws/lib/validation.js
      node_modules/.pnpm/ws@7.5.9/node_modules/ws/lib/validation.js:86:21  Error resolving commonjs request
          82 |   return true;
          83 | }
          84 | 
          85 | try {
             +                      v-----------------------v
          86 +   let isValidUTF8 = require('utf-8-validate');
             +                      ^-----------------------^
          87 | 
          88 |   /* istanbul ignore if */
          89 |   if (typeof isValidUTF8 === 'object') {
          90 |     isValidUTF8 = isValidUTF8.Validation.isValidUTF8; // utf-8-validate@<3.0.0
      
      unable to resolve module "utf-8-validate"

    node_modules/.pnpm/ws@8.13.0/node_modules/ws/lib/buffer-util.js
      node_modules/.pnpm/ws@8.13.0/node_modules/ws/lib/buffer-util.js:117:24  Error resolving commonjs request
         113 | 
         114 | /* istanbul ignore else  */
         115 | if (!process.env.WS_NO_BUFFER_UTIL) {
         116 |   try {
             +                         v-------------------v
         117 +     const bufferUtil = require('bufferutil');
             +                         ^-------------------^
         118 | 
         119 |     module.exports.mask = function (source, mask, output, offset, length) {
         120 |       if (length < 48) _mask(source, mask, output, offset, length);

I think there are a few issues being reported here.

1. Node stdlib requires/imports are failing
2. Highly dynamic requires/imports are failing

I think we can get stdlib imports to work in SSR, and should stop that error from reporting. If you use it in client side, then we need to still warn.

For the dynamic requires (it’s using eval!), this is challenging to support. Again, we could just let node handle it, but that’ll break if you’re trying to do a relative require (this case requires a node_module, which would work ok).

Solved in canary for me too, especially supabase and supabase ssr work now.

I have the same issue :

Warning: Webpack is configured while Turbopack is not, which may cause problems.

  See instructions if you need to configure Turbopack:
  https://turbo.build/pack/docs/features/customizing-turbopack

Learn more about Next.js v13 and Turbopack: https://nextjs.link/with-turbopack
Please direct feedback to: https://nextjs.link/turbopack-feedback

ready - started server on [::]:3000, url: http://localhost:3000
error - [resolve] node_modules/.pnpm/next-intl@2.15.0-beta.3_next@13.4.4_react@18.2.0/node_modules/next-intl/plugin.js
  node_modules/.pnpm/next-intl@2.15.0-beta.3_next@13.4.4_react@18.2.0/node_modules/next-intl/plugin.js:50:50  Error resolving commonjs request
      46 |   }
      47 | 
      48 |   return Object.assign({}, nextConfig, {
      49 |     webpack(config, options) {
         +                                                   v-----------------------v
      50 +       config.resolve.alias['next-intl/config'] = require.resolve(i18nPath);
         +                                                   ^-----------------------^
      51 | 
      52 |       if (typeof nextConfig.webpack === 'function') {
      53 |         return nextConfig.webpack(config, options);
      54 |       }
  
  unable to resolve dynamic or dynamic or dynamic

warning - [parse] node_modules/.pnpm/next-intl@2.15.0-beta.3_next@13.4.4_react@18.2.0/node_modules/next-intl/plugin.js
  node_modules/.pnpm/next-intl@2.15.0-beta.3_next@13.4.4_react@18.2.0/node_modules/next-intl/plugin.js:10:9  lint TP1004 fs.existsSync((???*0* | ???*1* | ???*2*)) is very dynamic
       6 | function initPlugin(i18nPath, nextConfig) {
       7 |   if (i18nPath) {
       8 |     i18nPath = path.resolve(i18nPath);
       9 | 
         +          v
      10 +     if (!fs.existsSync(i18nPath)) {
         +          ^
      11 |       throw new Error(
      12 |         `Could not find i18n config at ${i18nPath}, please provide a valid path.`
      13 |       );
      14 |     }
  
  - *0* arguments[0]
    ⚠️  function calls are not analysed yet
  - *1* i18nPath
    ⚠️  circular variable reference
  - *2* ???*3*((...) => fs["existsSync"](cur))
    ⚠️  unknown callee
  - *3* [???, ???, ???, ???, ???, ???, ???, ???]["find"]
    ⚠️  non-num constant property on array

  node_modules/.pnpm/next-intl@2.15.0-beta.3_next@13.4.4_react@18.2.0/node_modules/next-intl/plugin.js:26:20  lint TP1006 path.resolve(???*0*) is very dynamic
      22 |       './src/i18n.ts',
      23 |       './src/i18n.js',
      24 |       './src/i18n.jsx'
      25 |     ]
         +                     v
      26 +       .map((cur) => path.resolve(cur))
         +                     ^
      27 |       .find((cur) => fs.existsSync(cur));
      28 | 
      29 |     if (!i18nPath) {
      30 |       throw new Error(`\n\nCould not locate i18n config. Create one at \`./(src/)i18n.{js,jsx,ts,tsx}\` or specify a custom location:
  
  - *0* cur
    ⚠️  pattern without value

  node_modules/.pnpm/next-intl@2.15.0-beta.3_next@13.4.4_react@18.2.0/node_modules/next-intl/plugin.js:27:21  lint TP1004 fs.existsSync(???*0*) is very dynamic
      23 |       './src/i18n.js',
      24 |       './src/i18n.jsx'
      25 |     ]
      26 |       .map((cur) => path.resolve(cur))
         +                      v
      27 +       .find((cur) => fs.existsSync(cur));
         +                      ^
      28 | 
      29 |     if (!i18nPath) {
      30 |       throw new Error(`\n\nCould not locate i18n config. Create one at \`./(src/)i18n.{js,jsx,ts,tsx}\` or specify a custom location:
      31 | 
  
  - *0* cur
    ⚠️  pattern without value

  node_modules/.pnpm/next-intl@2.15.0-beta.3_next@13.4.4_react@18.2.0/node_modules/next-intl/plugin.js:50:49  lint TP1003 require.resolve((???*0* | ???*1* | ???*2*)) is very dynamic
      46 |   }
      47 | 
      48 |   return Object.assign({}, nextConfig, {
      49 |     webpack(config, options) {
         +                                                  v
      50 +       config.resolve.alias['next-intl/config'] = require.resolve(i18nPath);
         +                                                  ^
      51 | 
      52 |       if (typeof nextConfig.webpack === 'function') {
      53 |         return nextConfig.webpack(config, options);
      54 |       }
  
  - *0* arguments[0]
    ⚠️  function calls are not analysed yet
  - *1* i18nPath
    ⚠️  circular variable reference
  - *2* ???*3*((...) => fs["existsSync"](cur))
    ⚠️  unknown callee
  - *3* [???, ???, ???, ???, ???, ???, ???, ???]["find"]
    ⚠️  non-num constant property on array

  node_modules/.pnpm/next-intl@2.15.0-beta.3_next@13.4.4_react@18.2.0/node_modules/next-intl/plugin.js:8:15  lint TP1006 path.resolve((???*0* | ???*1* | ???*2*)) is very dynamic
       4 | const path = require('path');
       5 | 
       6 | function initPlugin(i18nPath, nextConfig) {
       7 |   if (i18nPath) {
         +                v
       8 +     i18nPath = path.resolve(i18nPath);
         +                ^
       9 | 
      10 |     if (!fs.existsSync(i18nPath)) {
      11 |       throw new Error(
      12 |         `Could not find i18n config at ${i18nPath}, please provide a valid path.`
  
  - *0* arguments[0]
    ⚠️  function calls are not analysed yet
  - *1* i18nPath
    ⚠️  circular variable reference
  - *2* ???*3*((...) => fs["existsSync"](cur))
    ⚠️  unknown callee
  - *3* [???, ???, ???, ???, ???, ???, ???, ???]["find"]
    ⚠️  non-num constant property on array

event - 2 requests (GET /, ...) 553ms

There’s some bad presentation for the error logs, but the core issue is:

    node_modules/.pnpm/ws@8.13.0/node_modules/ws/lib/buffer-util.js
      node_modules/.pnpm/ws@8.13.0/node_modules/ws/lib/buffer-util.js:117:24  Error resolving commonjs request
         113 | 
         114 | /* istanbul ignore else  */
         115 | if (!process.env.WS_NO_BUFFER_UTIL) {
         116 |   try {
             +                         v-------------------v
         117 +     const bufferUtil = require('bufferutil');
             +                         ^-------------------^
         118 | 
         119 |     module.exports.mask = function (source, mask, output, offset, length) {
         120 |       if (length < 48) _mask(source, mask, output, offset, length);
         121 |       else bufferUtil.mask(source, mask, output, offset, length);
      
      unable to resolve module "bufferutil"

    node_modules/.pnpm/ws@8.13.0/node_modules/ws/lib/validation.js
      node_modules/.pnpm/ws@8.13.0/node_modules/ws/lib/validation.js:122:25  Error resolving commonjs request
         118 |     return buf.length < 24 ? _isValidUTF8(buf) : isUtf8(buf);
         119 |   };
         120 | } /* istanbul ignore else  */ else if (!process.env.WS_NO_UTF_8_VALIDATE) {
         121 |   try {
             +                          v-----------------------v
         122 +     const isValidUTF8 = require('utf-8-validate');
             +                          ^-----------------------^
         123 | 
         124 |     module.exports.isValidUTF8 = function (buf) {
         125 |       return buf.length < 32 ? _isValidUTF8(buf) : isValidUTF8(buf);
         126 |     };
      
      unable to resolve module "utf-8-validate"

The childProcess.execFile and related “very dynamic” should be warnings, I’m not sure why they’re presented with the actual errors above.