Bundle size

[alexblack]

I'm trying out migrating from amplitude-js to amplitude-browser, hoping that we'd achieve a smaller bundle size through tree shaking (we're using it in Remix which uses esbuild)

However, our bundle size has gone up by ~13kb, despite our careful import usage like import { track } from '@amplitude/analytics-browser'

Before:

After:

[alexblack]

Hmm that tslib.js, weighing in at 10kb 3x seems suspicious

[stof]

@alexblack could it be that your project dependencies contain both tslib 1.x and 2.x, and performs hoisting for the 1.x version thus installing 2.x multiple times ?

[meri-maki]

Hi! Are there any plans regarding minifying package size?
or maybe there would be a way to amplitude.init() without importing the whole lib?

[joshunger]

Seems to have gotten worse compared to an older version 2.9.3? https://bundlephobia.com/package/@amplitude/analytics-browser@2.9.3

[stof]

@amplitude/analytics-browser always bundles a bunch of plugins (autocapture, page tracking, etc...) even if they are not used.
It would be great to have a package (@amplitude/analytics-browser-core or something like that) shipping the BrowserClient without any plugins (where enabling the plugin would require registering the plugin instead of changing a config option).
It would still be possible to ship @amplitude/analytics-browser as extending that browser core to automatically register plugins as today for projects that either don't care about bundle size or want to use all those plugins anyway.

The current setup means that any @amplitude/plugin-*-browser packages are effectively part of @amplitude/analytics-browser as far as bundle size is concerned (which means that splitting them as separate package provides dubious benefits)