size

We would like to avoid confusion like we have in webpack-contrib/webpack-bundle-analyzer#185

We could document statsFilename and reportFilename options allowing the use of an absolute file path like /path/to/folder so that people would know it's supported.

Let us know in this issue if you would like to contribute to this!

👋 Hello. We have a component that’s using this hook with in it’s default form (no custom callback) and have been getting a lot of ResizeObserver loop limit exceeded errors thrown during usage.

From my brief search around the internet it seems as though this is harmless but it does add a lot of noise in common usage and that that noise could be avoided

Hi, thanks for this action. My npm package is not in the root of the repo.

WDYT about adding working_directory option - good idea or not?

The current and only alignment of the bars is to the right. This alignment disconnects smaller bars from their names, making visual look-up (using the human eyes to connect an item to its bar) harder. For this reason, left alignment is perhaps more ergonomic.

https://github.com/JustIntroverted/TaskbarCustomizer/blob/ed30470a5f0ce4faf25bc28d38038d2fd466fe4a/TaskbarCustomizer/MainWindow.xaml.cs#L314-L328