Replies: 10 comments
-
Thanks for opening an issue! PR is welcome |
Beta Was this translation helpful? Give feedback.
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 |
Beta Was this translation helpful? Give feedback.
-
Turn webpack-bundle-analyzer/src/parseUtils.js Line 13 in d96ebed To sourceType: 'module' will work |
Beta Was this translation helpful? Give feedback.
-
any update on this? would love to analyze these types of bundles |
Beta Was this translation helpful? Give feedback.
-
I tried changing the sourceType but it didn't work. I think the data structure changes somewhat. |
Beta Was this translation helpful? Give feedback.
-
Heads up that this is still an issue. |
Beta Was this translation helpful? Give feedback.
-
Anyone who wants to can take a stab at fixing this with a PR |
Beta Was this translation helpful? Give feedback.
-
I'll take a stab at this. |
Beta Was this translation helpful? Give feedback.
-
Just as additional information, the proposed fix: sourceType: 'module' Resolved this for me. |
Beta Was this translation helpful? Give feedback.
-
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
Debug 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?
Beta Was this translation helpful? Give feedback.
All reactions