Replies: 12 comments
|
Hey, Any update about this? Cheers! |
|
The underlying package we use is I'd like to avoid adding a new configuration option for the browser, so I'm hesitant on adding this feature. |
|
Hey! Why not? It will not break anything, only add flexibility, which is always good 😄! Consider that peoples often use two browsers, it would be a nice feature to add:
Cheers |
|
It could be also useful for developer using webpack-bundle-analyzer in their library... |
|
To make it even better, I'll suggest to replace opener with open. |
Additional flexibility is a double-edged sword. It makes the API surface larger, making the tool harder to use as documentation grows longer. Adding new options also introduces maintenance burden as we will need to make sure the new feature does not accidentally break. We don't currently have the testing infrastructure for the So that is why I am not eagerly adding this feature. |
I would be agree if it was a huge add, but it's just easy as passing browser argument from webpack-bundle-analyzer to open. How could that break anything or make future that more complicated? I don't get it honestly... |
|
I would probably wait until sindresorhus/open#116 is implemented. |
|
Thanks @sindresorhus, looks like that would indeed help. |
|
FWIW: Until/if this is supported, you can hack around it with a script that overrides e.g. I put this script named And it allows me to choose my browser in the |
|
Hi there, |
|
Might not be, maybe a dependency bump is needed with this feature. Feel free to create a PR :) |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
Actually
webpack-bundle-analyzerdoesn't offer an option to choose which browser open.The option can only be set to default or null.
As many people use a different browser for development than for browsing it could be nice to have such choice.
Cheers
All reactions