-
-
Notifications
You must be signed in to change notification settings - Fork 482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Just shows stat size
#147
Comments
What is shown in the console? |
Can you run it in normal terminal console and it should show you the reason you see only Something like this:
|
Ahhhh, it's true
Do you have any idea? haha |
Do you have |
Yes! I have an error on file. The problem is because has an error on |
This seems to be a common issue people have -- maybe we could make the parsing error text pop out in a much more visible way..? Just thinking out loud. Improving logging and errors is something I'd love to help make happen after I get the v3 done 😊 |
@valscion I agree 😄 |
I had similar issue to this. For some reason it fails to parse @th0r maybe the error could be handled on per bundle basis? |
I was having this problem as well and it appears it is due to the fact that So seems like options at this point are to manually (or create a post-build script) to remove the scripts bundle information or not use the scripts and set up your own equivalent as a separate bundle? It's too bad that this is the case because it is helpful to be able to know how big that chunk is. It seems like if you don't care about the gzip size etc you can still sort of see it as the script bundle seems to be included in the main bundle? |
Any chance of creating a zip of your bundle dir contents and stats.json? We might be able to do something about your situation, @zbuhler |
I got the same problem after upgrading to webpack 4. I am not using any angular.cli |
Please open a new issue folks! It would help a lot in figuring out what is broken! |
@valscion I can upload my bundle dir and stats but first I thought I'd let you know I created a fresh Angular CLI project to see if I can narrow down the problem. I added jquery (just as a test) in my scripts array in my .angular-cli.json
Which generates a If I open any other bundle that is generated such as It appears to me that the analyzer chokes on chunks whose code isn't wrapped in a webpack function? The relevant parts of my stats.json that I remove are- "assetsByChunkName": {
"inline": "inline.86cf029305c934704a61.bundle.js",
"main": "main.66983cb30db00a1c5598.bundle.js",
"polyfills": "polyfills.dc963f90580f1044b785.bundle.js",
"styles": "styles.9c0ad738f18adc3d19ed.bundle.css",
- "scripts": "scripts.d464be456471b1b5f048.bundle.js"
} and -{
- "name": "scripts.d464be456471b1b5f048.bundle.js",
- "size": 158555,
- "chunks": [
- "scripts"
- ],
- "chunkNames": [
- "scripts"
- ],
- "emitted": true
-}, Which effectively excludes that chunk from being analyzed. In any case where do we go from here? Knowing this do you still want me to upload a zip of my dist folder? If you do want me to does it matter where I upload it? Does this warrant a new issue or were you referencing the webpack 4 issue when asking for a new issue to be created? I feel like my particular issue is more of an Angular CLI specific problem and not really anything to do with the analyzer project. I do have a couple of ideas though that seem to be within the scope of this project-
I'm probably missing something obvious but those are ideas/solutions that occur to me at this time. Let me know how I can help. |
Thanks for the extensive comment, @zbuhler! Now I finally understand how the interplay with angular-cli works 😄 A new issue specifically for your case would be great! It could be focused specifically on Angular CLI + scripts interplay, and contain the details you outlined in your comment. Maybe it could be titled "Angular CLI with scripts forces displaying of only stat size"? I'm not yet sure what the solution would be. I'd be inclined to not add any new configuration options or flags, if at all possible. It could be interesting to see if we could somehow avoid one rogue bundle (the jquery script in your example) causing all the other bundles to fail parsing, too.
Oh so nice! If you could whip up a reproduction repository for this minimal case, that would make it even better! It would be nice if you could also commit the built files to that repository directly, so we wouldn't even need to do any zipping 😛 |
Thanks for the feedback! Per your suggestions I created an issue and a sample repo to go with it. |
Just ran into this issue using analyzer with The problem is that analyzer uses physical files to calc parsed/gzipped sizes – while Second problem is that being used as plugin, analyzer shows no errors, while CLI tools says As I understand, there is nothing analyzer can do with |
I was using webpack with gulp and |
Thanks for the comments @jeron-diovis and @agentme! I opened a new issue related to documenting this surprising behavior, see #191 I'll lock this issue now as it is getting difficult to parse this thread where there are multiple issues. Please open a new issue if you think there's something wrong or something needs to be fixed. |
Issue description
I was using
webpack-bundle-analyzer
normally, but in last times, the result just showsstat size
and no moregzip size
andparsed size
.Technical info
Debug info
How do you use this module? As CLI utility or as plugin? As CLI utility
If CLI, what command was used?
webpack-bundle-analyzer dist/stats.json
If plugin, what options were provided? No
What other Webpack plugins were used?
angular-cli 1.6.0
stats.json.zip
The text was updated successfully, but these errors were encountered: