Replies: 9 comments 6 replies
|
Thanks for opening an issue! PR is welcome |
0 replies
This comment was marked as spam.
This comment was marked as spam.
|
@valscion Do you have any pointers how this can be implemented? I'd try to help if i can |
0 replies
|
Turn To sourceType: 'module'will work |
0 replies
|
any update on this? would love to analyze these types of bundles |
0 replies
|
I tried changing the sourceType but it didn't work. I think the data structure changes somewhat. |
0 replies
|
Heads up that this is still an issue. |
0 replies
|
Anyone who wants to can take a stab at fixing this with a PR |
0 replies
|
Just as additional information, the proposed fix: sourceType: 'module'Resolved this for me. |
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Issue description
Currently, It cannot parse properly when webpack5 config library type to
module. Because webpack5 append some codes likeexport {a, b, c}to the end of the bundle.Technical info
System: OS: macOS 11.2.3 CPU: (4) x64 Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz Memory: 3.01 GB / 24.00 GB Shell: 5.8 - /bin/zsh Binaries: Node: 15.11.0 - /usr/local/bin/node Yarn: 1.22.10 - /usr/local/bin/yarn npm: 7.6.0 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman npmPackages: case-sensitive-paths-webpack-plugin: 2.4.0 => 2.4.0 fork-ts-checker-webpack-plugin: 6.2.0 => 6.2.0 webpack: 5.28.0 => 5.28.0 webpack-bundle-analyzer: 4.4.0 => 4.4.0 webpack-cli: 4.5.0 => 4.5.0 webpack-merge: 5.7.3 => 5.7.3Debug info
How do you use this module? As CLI utility or as plugin?
plugin
If CLI, what command was used? (e.g.
webpack-bundle-analyzer -O path/to/stats.json)If plugin, what options were provided? (e.g.
new BundleAnalyzerPlugin({ analyzerMode: 'disabled', generateStatsFile: true }))new BundleAnalyzerPlugin({ analyzerMode: 'static' })What other Webpack plugins were used?
All reactions