Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Automatically trigger verbose stats when using `--profile`
See original GitHub issueFeature request
The flags --progress --profile explicitly tell webpack to produce a detailed output but instead the output is clipped with + 243 hidden lines
What is the expected behavior?
It makes no sense to clip the output I just requested, so those two flags should imply --stats verbose
What is motivation or use case for adding/changing the behavior?
It might just be me, but this makes me incredibly frustrated. I found the flag to do what I want and it does not work. It doesn’t help that the problem isn’t Googlable and I had to open https://github.com/webpack/webpack/discussions/14016
How should this be implemented in your opinion?
A new default automatic behavior
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
--progressshows percents of progress--profilefor profiling using webpack itself--stats verbosefor statsit is very different flags…
This issue had no activity for at least three months.
It’s subject to automatic issue closing if there is no activity in the next 15 days.