Drei 9.74.0 introduces new console warning related to @mediapipe\tasks-vision

[Sean-Bradley]

Using combination,

"@react-three/drei": "9.74.0",
"@react-three/fiber": "8.13.4",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-scripts": "5.0.1",
"three": "0.154.0"

produces warning related to @mediapipe/tasks-vision

WARNING in ./node_modules/@mediapipe/tasks-vision/vision_bundle.mjs
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '[redacted]\node_modules\@mediapipe\tasks-vision\vision_bundle_mjs.js.map' file: Error: ENOENT: no such file or directory, open '[redacted]\node_modules\@mediapipe\tasks-vision\vision_bundle_mjs.js.map'

If using Drei 9.73.0, no warning appears.

If using latest Drei at time of writing this (9.78.2) warning still appears.

[Sean-Bradley]

This is most likely not a DREI issue. It appears related to using webpack5 with CRA.
https://stackoverflow.com/questions/70599784/failed-to-parse-source-map

[Sean-Bradley]

Tried with vite

vite v4.4.5 building for production...
node_modules/@chevrotain/utils/lib/src/to-fast-properties.js (24:4) Use of eval in "node_modules/@chevrotain/utils/lib/src/to-fast-properties.js" is strongly discouraged as it poses security risks and may cause issues with minification.
node_modules/@mediapipe/tasks-vision/vision_bundle.mjs (1:25466) Use of eval in "node_modules/@mediapipe/tasks-vision/vision_bundle.mjs" is strongly discouraged as it poses security risks and may cause issues with minification.
node_modules/@mediapipe/tasks-vision/vision_bundle.mjs (1:26534) Use of eval in "node_modules/@mediapipe/tasks-vision/vision_bundle.mjs" is strongly discouraged as it poses security risks and may cause issues with minification.

Both chevrotain and @mediapipe/tasks-vision are dependencies of DREI

[Sean-Bradley]

One fix is to add a file in the project root named .env containing GENERATE_SOURCEMAP=false

E.g.,

[ektogamat]

I'm still getting this error from time to time

[Sean-Bradley]

I actually stopped using react-scripts and I don't get the error any more.
I also no longer use the .env fix I suggested earlier.
Instead, I now use R3F-Pack for development and prod build.
It may work for you, it depends on how complicated your project is.
I can't promise for sure. but I haven't seen this error for a few months now.

[ektogamat]

This stops working randomly and then gets back working again without any intervention. It is annoying. I was baking Code Sandbox for this error but I just noticed that it also happens when I'm working locally.
Thank you for the help Sean!

[swapnilchavan18901]

This error occurs only when we work in localhost not when in production