How to find out which own dependencies Webpack uses at runtime? #12518
mike-lischke
started this conversation in
General
Replies: 2 comments 12 replies
-
What is wrong with tool that I recommend? What do you want from webpack here?
All dependencies are used, because they are in |
Beta Was this translation helpful? Give feedback.
11 replies
-
The webpack core doesn't add any 3rd party code automatically (plugins and other tooling might do). But we add a bunch of runtime code depending on what you use. You find this code in this repo in these files:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is a pretty special question I have which Stackoverflow is not able to answer.
What I need to know is what parts of Webpack and which 3rd party code it relies on are actually shipped in generated code. For legal approval I need to list all 3rd/4th party libraries that are shipped to customers.
I looked at the package.json file of the project, but to me it looks as if that contains many build/dev dependencies. I installed webpack@4.44.2 explicitly (this is the version used by current react-scripts) which leaves me with a 600 lines long dependency tree. This cannot all be runtime dependencies. Much of that is certainly for build/dev time only, right?
So, how can I tell which dep is shipped?
Beta Was this translation helpful? Give feedback.
All reactions