[Snyk] Upgrade mixpanel-browser from 2.47.0 to 2.48.1

[victorDigital]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade mixpanel-browser from 2.47.0 to 2.48.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 2 versions ahead of your current version.
• The recommended version was released 21 days ago, on 2023-11-14.

Release notes

Package name: mixpanel-browser

• 2.48.1 - 2023-11-14
  

  This update patches a discrepancy between the minified and unminified versions of the packaged SDK. Campaign parameters will now be stored as super properties persistently in all versions.

• 2.48.0 - 2023-11-13
  

  API endpoint routes can now be configured individually, so you can rename /track, /engage, and /groups HTTP endpoints arbitrarily. Configure with the api_routes option:

  mixpanel.init(`my token`, {
    api_host: `https://my-proxy.example.com`,
    api_routes: {
      track: `foo/`,
      engage: `bar/`,
      groups: `baz/`,
    },
  ));

  In the above example, event-tracking requests will go to https://my-proxy.example.com/foo/, user profile updates to https://my-proxy.example.com/bar/, etc.

  Other fixes:

  • Event properties object passed to mixpanel.track() will no longer be mutated
  • Super properties are now reloaded from persistence when making every tracking call (i.e., kept fresh when another tab/window in the same browser has updated them)
  • Extra failsafe behavior for trying to clear queued requests when localStorage doesn't work on startup, e.g., when localStorage is full so writes fail
  • Block Chrome-Lighthouse user agent
  • Fix for error in add_group() when adding a new group to an existing list
• 2.47.0 - 2023-04-28
  

  New default event properties are now captured with each event, holding campaign data present on the URL at the time of tracking. These include UTM parameters (in the format utm_source, utm_campaign, etc.) and Click Identifiers (e.g., gclid, fbclid, etc.). This functionality can be disabled with the initialization setting {track_marketing: false}.

  UTM parameter properties are no longer persisted across pageloads as superproperties. They will be present only on events tracked on the same pageload where they were present initially. (2023-09-13) Correction: UTM parameter properties still persist across pageloads as superproperties. Persistence will be removed in a future release.

  For better first-touch attribution, UTM parameters present on the URL on pageload will be "set once" as profile properties (meaning that a new value will not overwrite any existing value on the profile property). These property names take the format initial_utm_source, initial_utm_campaign, etc. This functionality can be disabled with the initialization setting {skip_first_touch_marketing: true}.

  Support for automatic page-view tracking has been restored. With the init option {track_pageview: true}, an event named $mp_web_page_view will be tracked on pageload, containing properties identifying the current page (current_page_title, current_url_path, etc.) as well as any UTM parameters and Click Identifiers. Pageview events with these properties can also be triggered manually:

  // track a pageview event
  mixpanel.track_pageview();

  // track pageview with additional properties
  mixpanel.track_pageview({'Test variant': 'control'});

  Automatic page-view tracking may be turned on by default in a future release.

  Miscellaneous updates:

  • UUID generation now uses performance.now() when available as part of its time-based entropy algorithm
  • The network payload format now defaults to JSON for any API host containing the string mixpanel.com (looser than previous host checks)

from mixpanel-browser GitHub release notes

Commit messages

Package name: mixpanel-browser

• 7d155e6 rebuild 2.48.1 + changelog
• ac18edb 2.48.1
• 4a114e6 rebuild 2.48.1
• e55bfca Ensure UTMs persist in both unminified and minified code
• 3a2d8d9 2.48.0
• bd335b3 changelog for 2.48.0
• b1ed747 v2.48.0
• bd3e696 test for reloading superprops from persistence whenever tracking
• a4baa20 v2.48.0-rc2
• a816099 extraneous var decl
• 87d2dc7 fix persistence bug in add_group
• 088a0d2 make load_property read from persisted data
• e539fd1 _save_prop is unnecessary now
• 2fc8571 v2.48.0-rc1
• 49d5516 lint
• e9e2837 explanatory comment around opt-in/batch-start behavior
• ad4e7d3 export DEFAULT_API_ROUTES on mixpanel object
• c77b373 lint
• 23cbbad config docs for api options + rebuild docs
• 3ce1e35 add api_routes config option
• cb498ee attempt to clear out request-batcher queues when localStorage is failing on init
• 5e5b8c9 stop trying to send batches during opt-out
• d2af825 don't send events from Chrome-Lighthouse
• 1eaf569 rm unused method

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[netlify]

✅ Deploy Preview for betlec ready!

Name	Link
🔨 Latest commit	483848d
🔍 Latest deploy log	https://app.netlify.com/sites/betlec/deploys/656f9a6e608d1d0008add761
😎 Deploy Preview	https://deploy-preview-232--betlec.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.