Skip to content

Integrate Webpack Dashboard #463

Closed
Closed
@dnbkr

Description

@dnbkr

Would it be possible to integrate Webpack Dashboard? Currently this is possible once you've ejected, but I think a lot of users would benefit from it who may not want to eject just to have this plugin.

https://github.com/FormidableLabs/webpack-dashboard

Activity

alexzherdev

alexzherdev commented on Aug 18, 2016

@alexzherdev
Contributor

Already discussed in #449

gaearon

gaearon commented on Aug 18, 2016

@gaearon
Contributor

Yea, let’s wait it out a little bit.
Is there anything particular you’re missing from it?

dnbkr

dnbkr commented on Aug 18, 2016

@dnbkr
Author

No, it just seemed like a really nice project - but you're right, maybe a little premature to integrate it. Thanks for the create-react-app project by the way; makes knocking up little experiments so easy, whereas before I just wouldn't bother. Cheers!

kachkaev

kachkaev commented on Aug 17, 2017

@kachkaev

@gaearon what do you think of considering webpack-dashboard again, given that it's been around for one year?

gaearon

gaearon commented on Aug 17, 2017

@gaearon
Contributor

What information do you find valuable in particular?

kachkaev

kachkaev commented on Aug 17, 2017

@kachkaev

I'm particularly interested in the module size breakdown, i.e some feedback that would make me more thoughtful when doing another npm install xyz / import. If I'm not wrong, the only time CRA brings file sizes to the developer's attention is after npm run build. Seeing that the gzipped main.js is already 1MB is useful, but there no extra info on what modules to blame.

Maybe adding webpack bundle analyzer (#2359) can improve the feedback and thus make a positive impact on the obesity many modern web apps (including mine) suffer with.

gaearon

gaearon commented on Aug 17, 2017

@gaearon
Contributor

The problem is that the stats shown by Webpack dashboard are wrong. They are not representative of real file size distribution because they don't take dead code elimination and minification into account.

I think it's better to educate users about measuring their dependencies with sourcemap explorer that shows real numbers, than show wrong numbers immediately.

gaearon

gaearon commented on Aug 17, 2017

@gaearon
Contributor

Seeing that the gzipped main.js is already 1MB is useful, but there no extra info on what modules to blame.

Once it's over 512 kB we show a warning that includes a link to instructions on both bundle splitting and dependency analysis with sourcemap explorer. So I don't think it's accurate to say we don't help you learn about those tools.

Sharlaan

Sharlaan commented on Nov 5, 2017

@Sharlaan

The problem is that the stats shown by Webpack dashboard are wrong. They are not representative of real file size distribution because they don't take dead code elimination and minification into account.

How about electron-webpack-dashboard ? Does it show more accurate size estimations ?

gaearon

gaearon commented on Nov 6, 2017

@gaearon
Contributor

Last time I checked its numbers were wrong too. They might have fixed it by now, but maybe not.

I still suggest using source-map-explorer for best results.

locked and limited conversation to collaborators on Jan 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @alexzherdev@kachkaev@gaearon@Sharlaan@dnbkr

        Issue actions

          Integrate Webpack Dashboard · Issue #463 · facebook/create-react-app