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

[swissspidy]

Webpack is emitting this warning when I require( 'libheif-js/wasm-bundle' ) in my project.

The contents of wasm-bundle.js:

libheif-js/wasm-bundle.js

Line 1 in d583276

module.exports = require('./libheif-wasm/libheif-bundle.js')();

Not sure how this can be best addressed, I'd have to look into that, but I thought I'd share it here just in case in case anyone has ideas.

[ashuvssut]

This solution worked for me:

i changed the import statement like so:-

EDIT

@swissspidy ah sorry. its a bad solution

The warning went away. but the heic to jpeg conversions were failing. its a no-go

[catdad]

I am not all that familiar with this issue in particular -- it's been a while since I used webpack.

One question I have is: this shows as a warning. Warnings don't typically fail the build? Is this failing in some way or just causing annoying noise? I am finding that there are ways to ignore known warnings causing me to think this is not actually a blocking problem / failure as much as just scary looking.

Second question: I believe statically extracting dependencies has to do with treeshaking. Is that correct? This module can't really be slimmed down, since it doesn't include anything that is used.

Finally, it seems a few folks have reported it. Does anyone have a repro? Sharing a minimal code sample that reproduces the issue is very helpful in getting an issue debugged.

[jocluzet]

If it helps, I have this error with version ^1.17.1 but not with 1.10.0. I use the program very simply as a dependency of heic-convert.

[ashuvssut]

Is this failing in some way or just causing annoying noise?

its not blocking anything. its just a noise in devtools console tab

btw thankyou for your awesome work! i tried other different libs but failed miserably. But libheif-js works nicely

[sagarchoudhary96]

Found the way to supress this critical dependency warninig: check it out here

[sdkawata]

@catdad

It appears that the issue can be reproduced simply by requiring it in webpack as follows.
To reproduce, you can clone the repository below, run npm install, and then npm run build:
https://github.com/sdkawata/webpack-libheif-js-23

It seems that the issue lies in the part where crypto is being required.
By specifying crypto as an external dependency like below,
the warning no longer appears for us:
https://github.com/catdad-experiments/libheif-js/compare/master...sdkawata:libheif-js:add_crypto_as_external_dependency?expand=1

Although this is a warning and not an error,
in our environment — where we use Create React App — CI halts on warnings.
We believe this issue may be related to our setup with Create React App,
and due to this, we are currently unable to introduce the library.
It would be greatly appreciated if you could fix this issue.