Ivan Kopeykin

btw there is a plugin that marks modules with sideEffect flag https://github.com/vankop/side-effect-free-webpack-stat-plugin

@cdaringe I'm not sure, modules that were shaken not presented in stats. (I think for performance reasons first) this is more complex thing in webpack@5. e.g. case module.js ```js export...

[side-effect-free-webpack-stat-plugin](https://github.com/vankop/side-effect-free-webpack-stat-plugin) help a little bit on output analyze + you can use things like bundle analyzer or https://statoscope.tech/

> It seems like this very return may implicitly be where tree-shaking occurs? also https://github.com/webpack/webpack/blob/main/lib/FlagDependencyExportsPlugin.js , but it could be other places when exports info modified

it is hard to analyze all imports..

you should get an error for `require(f)()` btw

you should map ``` "./lib/index.js": "./dist/cjs/handlebars.js" ```

I fully agree with @alexander-akait idea => `exports should work as written`. btw this seems wrong to me: ``` using exports field: ./index.js using description file: /home/remco/Projects/bug/node_modules/bar/package.json (relative path: ./index.js)...

bump

as I described it is path itself. e.g. in case ```js /^(.+?)[\\/]cache[\\/]watchpack-npm-[^\\/]+\.zip[\\/]node_modules[\\/]/ ``` captured path will be `(.+?)`