Add npm run visualize command #203

Closed
mxstbr opened this Issue Feb 29, 2016 · 13 comments

Comments

Projects
None yet
2 participants
Owner

mxstbr commented Feb 29, 2016

Using the webpack visualizer plugin we can create a visualization where the bundle size comes from, which can be really handy! This should come as a simple npm command, maybe npm run visualize?


Note: If you do want to submit a PR work on the v3.0.0 branch please!

mxstbr added this to the v3.0 milestone Feb 29, 2016

Collaborator

oliverturner commented Mar 1, 2016

Nice idea! Can have a crack later if you like

Owner

mxstbr commented Mar 1, 2016

Sure thing, would love that!

Collaborator

oliverturner commented Mar 1, 2016

👍

@mxstbr mxstbr modified the milestone: Future, v3.0 Mar 2, 2016

Owner

mxstbr commented Mar 6, 2016

How is this coming along @oliverturner, any problems so far?

Collaborator

oliverturner commented Mar 6, 2016

Only the absence of opportunity...

Collaborator

oliverturner commented Mar 6, 2016

Out of interest, is there a reason to use an alternative to the version at http://webpack.github.io/analyse ?

Owner

mxstbr commented Mar 6, 2016

Absolutely none, I didn't know an official visualizer exists. (maybe the command should be npm run analyse?)

Take a look at both of them, implement whichever one you prefer and tell my why!

Collaborator

oliverturner commented Mar 6, 2016

That's what I called it before :)

Collaborator

oliverturner commented Mar 6, 2016

I'm inclined to use tools directly associated with the project and supported by the author (particularly in light of the upcoming 2.0 release).

Owner

mxstbr commented Mar 6, 2016

Sure thing, sounds like a good reason!

Collaborator

oliverturner commented Mar 6, 2016

I'll get that (and the documentation PR) done tomorrow. Apologies for the delay.

Owner

mxstbr commented Mar 6, 2016

No worries, thanks for the help!

@oliverturner oliverturner added a commit that referenced this issue Apr 6, 2016

@oliverturner oliverturner Addresses #203 1f0acd3

@mxstbr mxstbr modified the milestone: v3.0, Future Apr 13, 2016

Owner

mxstbr commented Apr 13, 2016

This is pretty much done in #261, thanks to the always amazing @oliverturner!

mxstbr closed this Apr 13, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment