Have a dedicated flag to show up envinfo
See original GitHub issuePresently, the users are required to provide information concerning his local environment as per the ISSUE_TEMPLATE
. IMO, it would be good to have a dedicated flag which would show up the respective information webpack-bundle-analyzer --info
(just as we’ve webpack-cli info
)
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
webpack-bundle-analyzer - Bountysource
IMO, it would be good to have a dedicated flag which would show up the respective information webpack-bundle-analyzer --info (just as we've webpack-cli...
Read more >dotenv variables are not available in bridge jobs - GitLab
The environment variables appear to not be passed but either show up empty, or if you attempt to explicitly include them, the variable ......
Read more >odo CLI reference - Developer CLI (odo) | CLI tools | OpenShift ...
If the --push flag is passed to the command, the images are pushed to their registries after they are built. odo catalog. odo...
Read more >How to Install and Configure K3s on Ubuntu 18.04 - Liquid Web
To deploy a K3s cluster with a master and worker node, we need three ... mtu 9001 qdisc fq_codel state UP group default...
Read more >Chapter 3. Developer CLI (odo) - Red Hat Customer Portal
Adds the --deploy flag to the odo delete command, to remove components ... want to get up and running quickly to experiment with...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Feel free to do so — however, please be aware that we might not merge a PR for this even if it would work. I’d be curious to see what a proof of concept looks like but I make no promises on it being something we would want to maintain.
💞
Yeah I agree that the issue template could be improved and that it asks for lots of information that might be difficult to gather.
I’m not sure though how much an effort adding a new flag for debug information would be. I’d be reluctant to have to maintain that code if it would be complicated and prone to breakage itself.
One of the most important parts for bug debugging is the generated stats.json, ideally with the bundled output files. I’m not sure if it’s realistic to automate generating them for issue template purposes, given people have such different webpack configurations.
So all in all, I think this is a neat idea but I’m not sure if it’s possible to implement it (at least not easily). I’d be happy to be proven wrong ☺️