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

bundle size serve-build and build #638

Closed
ufon opened this issue Jan 19, 2017 · 3 comments
Closed

bundle size serve-build and build #638

ufon opened this issue Jan 19, 2017 · 3 comments

Comments

@ufon
Copy link

ufon commented Jan 19, 2017

at simple http-server i have 700 kb
image
at serve-build i have fantastic 200kb
image
i don't understand
i also read #613 but not finally understand :(

@ghost
Copy link

ghost commented Jan 19, 2017

The only thing you should care about is gatsby build size.
It is a minified version of the final js, you will then upload to the server.
Also, the server will compress the bundle.js with gzip, making it even smaller.

In #613 I messed up with some configs and the js minifier got broken, so the bundle.js size was pretty huge.

In order to understand how gatsby is working, it's a good idea to start with:
webpack and react basics.

@ufon
Copy link
Author

ufon commented Jan 19, 2017

@g8tguy thx u! i power on my gzip on server and bundle was compressed to 200kb.

@ufon ufon closed this as completed Jan 19, 2017
@KyleAMathews
Copy link
Contributor

This will get even smaller in 1.0! #431

E.g. loading my blog bricolage.io requires eval/parsing around 110kb of minified/gzipped JS. The absolute minimum is smaller. I'm also going to be experimenting soon with using preact/inferno which seem ideal for a content-only Gatsby site which would reduce the size even further.

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