Minimize the browserified size

[sindresorhus]

Turns out some people use this with browserify, but by default got is huge when browserified, since it includes the buffer browser polyfill and other things. We should look into if there's any way to get it down without too much work.

Relevant: https://twitter.com/mattdesl/status/624703076159590400

Not sure, but this might be useful: https://github.com/miguelmota/buffer-to-arraybuffer

[floatdrop]

Full list of browserified modules: https://gist.github.com/floatdrop/acfb074b261288655e45

Top of size-eaters:

• browserify-zlib is 173.3 Kb f9f2807
• duplexify is 64.9 Kb
• buffer is 43.7 Kb

[mattdesl]

👍

I started got-xhr for this reason but haven't published it yet. If possible, I would rather build on an existing module than add more clutter to npm.

But with that said, it might be necessary to have a separate got-like module that has a more limited scope than got. Things like:

• avoiding Buffer, and instead using ArrayBuffer since it is more common in the browser
• avoiding zlib, since the browser handles gzip for us anyways (from what I understand?)
• avoiding streams entirely since they add a pretty significant amount of bloat
• just using xhr under the hood

[mattdesl]

Update: I'm now using xhr-request in node/browser for non-streamed requests.

For streamed requests, simple-get is pretty good, and half the size of got.

got could probably be almost as small as simple-get by doing something like this:
https://github.com/feross/simple-get/blob/d212b1022d21b49c8ec83acf251d1dc4aeb38ca3/package.json#L10-L12

[kevva]

66542fd reduced the size from 471 KB to 268 KB, thanks @mattdesl.

[floatdrop]

With 6.0.0 version got is almost same size as simple-get, but still 10x bigger than xhr.

❯ browserify -r got | wc -c
  207787

❯ browserify -r simple-get | wc -c
  194566

❯ browserify -r xhr | wc -c
  11147

[sindresorhus]

@floatdrop Woot! Try gzipping too. That gives more accurate numbers.

[mattdesl]

Nice!

gzip can be misleading when you are considering how bundle size affects parse/execution time. 😄

More details:
https://timkadlec.com/2014/09/js-parse-and-execution-time/

[mattdesl]

But you should probably include uglifyjs -cm to get a better idea.

[mattdesl]

p.s. You can't run got through uglify-js right now because it has some ES6-isms (which also means it will break on safari, IE and the likes).

browserify -r got | uglifyjs -cm | wc -c
Parse error at -:7172,5
Unexpected token: name (redirectCount)
Error
    at new JS_Parse_Error (eval at <anonymous> (/Users/matt/npm/lib/node_modules/uglify-js/tools/node.js:22:1), <anonymous>:1526:18)
   ...

[thisconnect]

@mattdesl about Unexpected token: name (redirectCount) it is caused by let, see mishoo/UglifyJS#887