Figuring out why a dependency is included?

[craggy terrace]

Hi everyone,
I have a large dependency that is being included in my build but as far as I am aware I'm not using it anywhere.

It is listed in my package.json as I use it for another build, but I'm not sure why it's included in this build so.... does anyone have any tips on working out where a dependency is being included from? Any path tracing we can do?

[daring widget]

I've faced the same issue when using dynamic imports. Keep in mind that the static analysis does not support variables.