-
Notifications
You must be signed in to change notification settings - Fork 11.9k
Open
Copy link
Labels
angular/build:applicationarea: @angular/buildfeatureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfeature: in backlogFeature request for which voting has completed and is now in the backlogFeature request for which voting has completed and is now in the backlog
Description
Command
build
Description
It would be a lot simpler to debug your stats json if we had a separate server and browser stats. As it is right now, everything is bundled together and is a huge pain trying to figure things out. You have to manually look at what the cli output said was for server and what was for browser, then go through the json and manually separate things. This can take a long time. And then, when you find one thing, you have to build again, just to start the process over to see if you made improvements.
Describe the solution you'd like
I would like a stats.browser.json and a stats.server.json so I can independently figure out what's being included in the bundle for the server versus the browser.
Describe alternatives you've considered
There are none that I'm aware of.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
angular/build:applicationarea: @angular/buildfeatureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfeature: in backlogFeature request for which voting has completed and is now in the backlogFeature request for which voting has completed and is now in the backlog