Upgrading from 1.3.3 to 1.3.4 gives worrying build-time warnings

I’m using jotai in a Next.js project, with nothing special in particular with the setup.

When I upgrade to 1.3.4 I get this in the build output, which seems reasonably important. My guess is that it’s to do with the way the exports were changed to use wildcards?

Reverting back to 1.3.3 removes the warning.

warn  - ./node_modules/jotai/esm/index.js
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

./node_modules/jotai/esm/utils.js
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

./node_modules/jotai/esm/utils.js
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

[prichodko]

FYI, this is also happening in Next.js, which doesn’t use esbuild.

[Thisen]

Just to be clear, this is caused by the version of esbuild that builds jotai, it’s not because of the consumers environment. This doesn’t have anything to do with Next.js or Gatsby. 🙂