I have a webpack configuration with some bootloaders and plugins. These loaders have some include / test / exclude rules.
However, the set of files is saved in the webpack assembly. They are not imported anywhere, which means that this is probably some bad configuration.
Is there any way to ask webpack WHY the file is included in the assembly?
There are some display options that you can set when you run the web package, which can help you achieve what you want to achieve. Check them out here .
, --display-reasons, , , , . : --display-modules , , , node_modules bower_components.
--display-reasons
--display-modules
, .
, , :
stats: 'verbose'
webpack config. , , . stats .
stats
Source: https://habr.com/ru/post/1687601/More articles:MapKit scaling issues - swiftHow to check if IE11 is in JS compatibility view - javascriptClear table with jQuery - javascriptRun global ESLint with eslint-plugin-jsx-a11y plugin - javascriptAn effective way to delete a line containing specific text in vim with a hint - vimМне нужна анимация частиц для андроида с изображениями наших собственных, а не холстов - androidrun-android-react-random, not accidentally deleted or creating a folder - react-nativeInsert into multiple tables using space save library - androidАльтернатива MediaRecorder для setNextOutputFile до Oreo? - androidJSHint does not recognize Async / Await syntax in Visual Studio Code (VSCode) - javascriptAll Articles