Next dev hot reload warnings

[NMVW]

When using next dev locally to develop, run into the following chatty warning (1000 warning logs per minute):

hot-dev-client.js:85 ./node_modules/fauna/dist/browser/index.js
Critical dependency: require function is used in a way in which dep endencies cannot be statically extracted

[ptpaterson]

Thanks for reporting. We've created an internal issue to prioritize and track: FE-4891

The driver is designed to work in a lot of different environments and so we've done some dynamic importing to check for the existence of particular modules and only use them when available.

[ptpaterson]

We have a similar report about these warnings, but also build errors this time

warn ./node_modules/fauna/dist/browser/index.js
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
warn ./node_modules/fauna/dist/browser/index.js
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
success Building production JavaScript and CSS bundles - 5.056s

 ERROR #98123  WEBPACK.BUILD-HTML

Generating SSR bundle failed

Reading from "node:http2" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.

File: node:http2


 ERROR #98123  WEBPACK.BUILD-HTML

Generating SSR bundle failed

Reading from "node:os" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.

File: node:os

not finished Building HTML renderer - 3.400s


"build.command" failed

[NMVW]

Thanks for reporting. We've created an internal issue to prioritize and track: FE-4891

The driver is designed to work in a lot of different environments and so we've done some dynamic importing to check for the existence of particular modules and only use them when available.

Any updates on this issue? Our dev times are skyrocketing now (up to 15-30 second reloads for a single module source code update) slowing down our product dev flows