Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

[vladmandic]

WebPack version 5 changed how it handles dynamic imports

Human library itself does not use dynamic imports, but bundled TensorFlow/JS in human.esm.js includes some additional platform-specific capabilities
For example, WASM binaries can be loaded using filesystem read file calls, but only when platform is NodeJS

Presence of those dynamic capabilities detection calls causes WebPack to misinterpret type of a library used and generate warning messages:

WARNING in ./node_modules/@vladmandic/human/dist/human.esm.js 13:11-18
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

Note that this is NOT AN ERROR, but simply a WebPack warning that can be safely ignored.

However, if you want to eliminate such warnings,
solution is to explicitly specify in WebPack configuration that Human is an ESM library:

in webpack.config.js add:

module.exports = {
  module: {
    rules: [
      { test: /human.esm.js/, type: 'javascript/esm' },
    ],
  },
}

Note that WebPack is internally used by many frameworks and location of the config file may differ between frameworks (React, Angular, Vue, Next, etc.)

To see how to modify WebPack configuration in cases when non-default configuration files are used, check framework specific documentation.

[vladmandic]

Example of webpack configuration inside NextJS project:

next.config.js

/** @type {import('next').NextConfig} */

module.exports = {
  ...
  webpack: (config, options) => {
    config.module.rules.push({ test: /human.esm.js/, type: 'javascript/esm' });
    return config
  },
}