Skip to content
This repository has been archived by the owner on May 20, 2021. It is now read-only.

Moving webpack-bundle-analyzer under webpack-contrib organization #15

Closed
valscion opened this issue Sep 24, 2017 · 2 comments
Closed

Moving webpack-bundle-analyzer under webpack-contrib organization #15

valscion opened this issue Sep 24, 2017 · 2 comments

Comments

@valscion
Copy link
Member

Hi folks!

@th0r and me have been discussing transfer of https://github.com/th0r/webpack-bundle-analyzer under a webpack organization in GitHub.

I asked @TheLarkInn whether this would be a good idea and he said yes, and eventually asked me to create an issue here so we could go through the process of what this transference would mean ☺️

As I understand it, there has been lots of decisions made in #1 that we might need to apply in https://github.com/th0r/webpack-bundle-analyzer.

So, what do you want to know? And what would we need to do?

@valscion
Copy link
Member Author

One reason why this is a good time to do the transition is that I am currently going over a big upgrade in webpack-bundle-analyzer to enable custom visualization/reporter packages: webpack-contrib/webpack-bundle-analyzer#97

I envision that we will see many different kinds of bundle visualizations and tools pop up that would largely benefit from this. I'd love to see people go and make the wildest and funkiest visualizations they want to with quality data containing post-minification and post-gzip sizes.

@joshwiens
Copy link
Member

Done & done

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants