[MOB-9520]: enable tree-shaking

[mprew97]

JIRA Ticket(s) if any

• MOB-9520

Description

Enables tree shaking to resolve this issue

Test Steps

1. Remove sideEffects: false from package.json.
2. Run yarn webpack-analyze from react-example dir
3. Note the bundle size
4. Add back sideEffects:false to package.json
5. See smaller bundle size due to tree shaking

Before: 3.31 mb

After: 2.78 mb

[ts-nguyen]

I'm definitely not an expert with JS packages and bundle sizes but I would've expected changes in our webpack config files to reduce bundle size and for tree shaking. The changes here seem more like bundle stat info, is this just preliminary work? nvm actually looked at the issue and I see the change now, can you post a screenshot of the stat output to show the difference?

[lposen]

@mprew97 -- one question -- are we importing any pollyfills or css? (not including things like style-components)

[lposen]

@mprew97 Unless I'm doing something wrong, this hasn't changed the bundle size :( index.js remains at 353kb.

[mprew97]

@mprew97 Unless I'm doing something wrong, this hasn't changed the bundle size :( index.js remains at 353kb.

@lposen , @ts-nguyen added a screenshot with bundle sizes pre/post tree shaking.

My mistake, should have added that to begin with.

I also added the analyzer to the wrong project. Tree shaking shouldn't change the bundle size of the Web SDK itself, but rather the apps it is used in (from my understanding). So need to test in react-example

[mprew97]

@mprew97 -- one question -- are we importing any pollyfills or css? (not including things like style-components)

@lposen i do not see any explicit polyfills in our deps or webpack config. I do not think we are importing any external CSS either.