Reduce Bundle Size

[fadi-george]

Description

1 Line Summary

Reduce bundle size from:
Main:

  build/releases/OneSignalSDK.page.js
  Size limit: 450 B
  Size:       450 B gzipped
  
  build/releases/OneSignalSDK.page.es6.js
  Size limit: 51.8 kB
  Size:       51.8 kB gzipped
  
  build/releases/OneSignalSDK.sw.js
  Size limit: 13.96 kB
  Size:       13.96 kB gzipped
  
  build/releases/OneSignalSDK.page.styles.css
  Size limit: 8.81 kB
  Size:       8.8 kB  gzipped

Branch:

  build/releases/OneSignalSDK.page.js
  Size limit: 421 B
  Size:       421 B gzipped
  
  build/releases/OneSignalSDK.page.es6.js
  Size limit: 50.27 kB
  Size:       50.27 kB gzipped
  
  build/releases/OneSignalSDK.sw.js
  Size limit: 13.63 kB
  Size:       13.63 kB gzipped
  
  build/releases/OneSignalSDK.page.styles.css
  Size limit: 8.81 kB
  Size:       8.8 kB  gzipped

Details

• Set terser passes to 2 to reduce the size a bit. 3 passes would not lead lto any gains.
• Break up more static classes like onesignal api, timed local storage, dismiss helper, etc
• Delete retry backoff constants and just use it inline

Systems Affected

• WebSDK
• Backend
• Dashboard

Validation

Tests

Info

Checklist

• All the automated tests pass or I explained why that is not possible
• I have personally tested this on my machine or explained why that is not possible
• I have included test coverage for these changes or explained why they are not needed

Programming Checklist
Interfaces:

• Don't use default export
• New interfaces are in model files

Functions:

• Don't use default export
• All function signatures have return types
• Helpers should not access any data but rather be given the data to operate on.

Typescript:

• No Typescript warnings
• Avoid silencing null/undefined warnings with the exclamation point

Other:

• Iteration: refrain from using elem of array syntax. Prefer forEach or use map
• Avoid using global OneSignal accessor for context if possible. Instead, we can pass it to function/constructor so that we don't call OneSignal.context

Screenshots

Info

Checklist

• I have included screenshots/recordings of the intended results or explained why they are not needed

---

Related Tickets

---

---

This change is 

[sherwinski]

I guess I'm a bit confused about one thing: we're opting to wildcard import all of these modules but I was under the impression that doing so would interfere with tree shaking? Am I missing something here?

[sherwinski]

This change doesn't seem consistent with the old backoff strategy:

export const RETRY_BACKOFF: { [key: number]: number } = {
  5: 10_000,
  4: 20_000,
  3: 30_000,
  2: 30_000,
  1: 30_000,
};

Wouldn't this just increase by 10000 ms each time after the update?

[fadi-george]

Fixed it inline

[fadi-george]

I guess I'm a bit confused about one thing: we're opting to wildcard import all of these modules but I was under the impression that doing so would interfere with tree shaking? Am I missing something here?

The vite config tree-shake smallest which will do aggressive minification and use only used exports.

[sherwinski]

Doesn't the backoff strategy start with 10, then 20, then 30 seconds? Since we're decrementing retry.

[fadi-george]

Oops updated comment