feat: default to gzip compression instead of base64

[frankh]

Changes

it's weird that we do our first requests before the decide response with base64 "compression", as

1. we've supported gzip for literally years, so there's basically zero risk of somehow hitting an endpoint that doesn't support it
2. base64 is not compression, it increases the payload size compared to if we did nothing at all
3. rust capture does not support base64

Checklist

• Tests for new code (see advice on the tests we use)
• Accounted for the impact of any changes across different browsers
• Accounted for backwards compatibility of any changes (no breaking changes in posthog-js!)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
posthog-js	✅ Ready (Inspect)	Visit Preview	Aug 13, 2024 1:22pm

[github-actions]

Size Change: 0 B

Total Size: 1.17 MB

ℹ️ View Unchanged

Filename	Size
dist/array.full.js	333 kB
dist/array.js	154 kB
dist/exception-autocapture.js	10.4 kB
dist/main.js	155 kB
dist/module.js	154 kB
dist/recorder-v2.js	110 kB
dist/recorder.js	110 kB
dist/surveys-preview.js	59.8 kB
dist/surveys.js	66 kB
dist/tracing-headers.js	8.26 kB
dist/web-vitals.js	5.79 kB

_{compressed-size-action}

[benjackwhite]

Will be interesting if no tests fail...

[frankh]

had to fix the mock parsing but looks good now

[webjunkie]

Curious: What is the reason we don't use headers/http level compression?

[benjackwhite]

Curious: What is the reason we don't use headers/http level compression?

You can't for requests. (You can't know what the server accepts before sending the request). Thats why you tell the server what you accept with headers like accept-encoding