Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix bundle size report #879

Merged
merged 1 commit into from
Sep 4, 2019
Merged

Fix bundle size report #879

merged 1 commit into from
Sep 4, 2019

Conversation

shawnbot
Copy link
Contributor

@shawnbot shawnbot commented Sep 4, 2019

I was looking at the bundle size report that #862 was supposed to generate, and it looks like it was failing. This is the fix; assuming it works here, let's merge into that PR and include an item for it in #878. 🤞

@vercel
Copy link

vercel bot commented Sep 4, 2019

This pull request is automatically deployed with Now.
To access deployments, click Details below or on the icon next to each push.

Latest deployment for this branch: https://primer-css-git-fix-bundle-size-report.primer.now.sh

@shawnbot shawnbot requested a review from simurai September 4, 2019 22:05
@shawnbot shawnbot changed the base branch from master to input-dark September 4, 2019 22:05
@shawnbot
Copy link
Contributor Author

shawnbot commented Sep 4, 2019

Here's how this change would affect CSS bundle size (before optimization plugins):

name selectors ± gzip size ± raw size ±
primer 3317 +62 26.63K +852B 167.21K +4.82K
core 2283 +61 18.53K +846B 116.64K +4.77K
product 374 +1 4.93K +10B 23.1K +48B
forms 193 +6 2.99K +78B 11.85K +373B
navigation 103 - 1 1.65K +42B 6.96K +126B
select-menu 54 +1 1.36K +6B 4.99K +48B

(I'm honestly not sure why this touches so many modules; just seeing what this might look like for different PRs.)

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

Successfully merging this pull request may close these issues.

1 participant