@mparticle/web-braze-kit 3.0.6 → 3.0.8

package/README.md

@@ -1,42 +1,33 @@
-![Braze Logo](https://github.com/mparticle-integrations/mparticle-javascript-integration-appboy/blob/master/braze-logo.png)
+![Braze Logo](https://github.com/mparticle-integrations/mparticle-javascript-integration-appboy/blob/master/braze-logo.png) 
 
 ⚠️⚠️⚠️
-# 2/14/2023 Notice! Opt in for Breaking Changes to mParticle Web Braze Kit coming soon
-mParticle's Braze Kit currently uses Braze's V3 web SDK, and Braze has made significant changes to their newest V4 web SDK.  Previously, mParticle planned to release an update on 2/15/2023 for all of our CDN users which upgraded to the Brave V4 web SDK.  Now, rather than migrate all CDN users to V4 at the same time, you must opt in to get the latest update.  This will allow you to decide when you want to upgrade to V4 and make the appropriate code changes. Opting in to V4 will be done via a connection setting in the mParticle UI that will be available shortly.
+# Notice! Opt in is now available for Braze Web SDK V4 - Action Required
 
-For now, no code changes are needed, but if you implemented the code examples outlined in our docs and earlier communications, you can continue to use the V3 code until you opt in to V4 manually.  More details on that are coming soon.
+You can now select what version of the Braze SDK you want to use when setting up a Braze connection in the mParticle UI.  Braze occasionally makes breaking changes to their SDK, so if you call `appboy` directly in your code, you will have to update your code to ensure your website performs as expected when updating versions of Braze.
 
-If you self-host mParticle and the Braze Web Kit via npm, you can update sooner. Follow the instructions below for if you self-host or if you are on CDN and getting ready to opt in.
+Please review the [Braze Changelog](https://www.braze.com/docs/developer_guide/platform_integration_guides/web/changelog#400) and [V4 migration guide](https://github.com/braze-inc/braze-web-sdk/blob/master/UPGRADE_GUIDE.md) to learn about the differences between V3 and V4 and what changes you will need to make in your code. The most significant breaking changes are the replacement of the `appboy` class name with `braze`, in addition to the removal and renaming of several APIs.
 
-* <b>Note that if you are here looking at source code, the `master` branch will continue to contain Braze Web Kit version 3.X until the opt in option is available.  The `braze-v4-npm-master` branch currently contains the source code for v4.X.</b>
-* If you are using version 2 of the @mparticle/web-appboy-kit, you will need to <a href="#transition-from-mparticleweb-appboy-kit-to-mparticleweb-braze-kit">transition to @mparticle/web-braze-kit per the instructions here</a> before following the below instructions as well.
-
-## Braze Web Kit Citical Updates and Timelines
-
-Braze occasionally makes breaking changes to their SDK, so if you call Braze directly in your code, you will have to update your code to ensure your website performs as expected when updating versions of Braze.
-
-Please review [Braze’s Changelog notes](https://www.braze.com/docs/developer_guide/platform_integration_guides/web/changelog#400) as well as Braze’s [migration guide](https://github.com/braze-inc/braze-web-sdk/blob/master/UPGRADE_GUIDE.md) between version 3 and 4 to understand these changes and what code updates are needed from your side.  The largest change is the move from class name `appboy` to `braze`. Braze also removed and renamed some APIs.  As a result, we are also updating our mParticle Braze web kit from 3.0.X to 4.0.X in order to support Braze’s Web SDK version 4.2.1.
-
-Customers will be able to opt in to using the latest version of Braze's Web SDK both via npm and via snippet/CDN
+You can opt into the latest major version of the Braze Web SDK whether you implement mParticle's Web SDK using npm or our snippet/CDN.
 * Customers who self-host mParticle via npm - You can use @mparticle/web-braze-kit version 4.0.0 in your package.json now! This has been available since 10/15/2022.
-* Customers who load mParticle via snippet/CDN - Opting in will be available soon via the mParticle UI in your Braze connection settings.
+* Customers who load mParticle via snippet/CDN - Opting in is available via the mParticle UI in your Braze connection settings.
+
+Note that the following is only one example.  Everywhere you manually call `appboy` needs to be updated similar to the below. If you are using NPM, you can skip to step 3.  Please be sure to test your site fully in development prior to releasing.
 
-Note that the following is only one example.  Everywhere you manually call `appboy` needs to be updated similar to the below.
 
 * Step 1: Legacy code sample. Find all the places where your code references the `appboy.display` namespace.  Braze has removed all instances of the `display` namespace:
 ```javascript
 window.appboy.display.destroyFeed();
 ```
 
-Step 2: Roll out code changes to be used before you opt in to using Version 4 of the Braze Web SDK so that it works under both versions:
+Step 2: Roll out code changes to be used before February 15, 2023:
 ```javascript
-	if (window.appboy) {
-		window.appboy.display.destroyFeed();
-	} else if (window.braze) {
-		window.braze.destroyFeed();
-	}
+if (window.appboy) {
+	window.appboy.display.destroyFeed();
+} else if (window.braze) {
+	window.braze.destroyFeed();
+}
 ```
-Step 3: After opting in to Version 4 of the Braze Web SDK, you can simplify your code:
+Step 3: After February 1, 2023, you can simplify your code after the mParticle Braze Web kit, which includes Braze SDK V4, has been released to our CDN:
 ```javascript
 window.braze.destroyFeed();
 ```
@@ -54,6 +45,7 @@ The legacy @mparticle/web-appboy-kit from npm includes version 2 of the Braze We
 
 
 
+
 # License
 
 Copyright 2022 mParticle, Inc.

package/dist/BrazeKit.common.js

@@ -304,8 +304,9 @@ window.appboy = appboy_min;
 //  limitations under the License.
 
 var name = 'Appboy',
+    suffix = 'v3',
     moduleId = 28,
-    version = '3.0.6',
+    version = '3.0.8',
     MessageType = {
         PageView: 3,
         PageEvent: 4,
@@ -332,6 +333,7 @@ var constructor = function () {
         mpCustomFlags;
 
     self.name = name;
+    self.suffix = suffix;
 
     var DefaultAttributeMethods = {
         $LastName: 'setLastName',
@@ -729,7 +731,7 @@ var constructor = function () {
         customFlags
     ) {
         console.warn(
-            'mParticle will soon update the Braze web kit and upgrade the Braze SDK that you are currently using from V3 to V4.  This will be an opt-in update, but we recommend you opt in when the update is available to get the latest bug fixes and features from Braze.  Please see https://docs.mparticle.com/integrations/braze/event for more information and necessary upgrade steps when you decide to opt in.'
+            'mParticle now supports V4 of the Braze SDK. This is an opt-in update, and we recommend you opt in to get the latest bug fixes and features from Braze.  Please see https://docs.mparticle.com/integrations/braze/event for more information and necessary upgrade steps when you decide to opt in.'
         );
         // check to see if there is a logger for backwards compatibility, and if not, mock one to avoid errors
         if (!self.logger) {
@@ -926,9 +928,11 @@ function getId() {
 }
 
 function register(config) {
+    var forwarderNameWithSuffix = [name, suffix].join('-');
     if (!config) {
         window.console.log(
-            'You must pass a config object to register the kit ' + name
+            'You must pass a config object to register the kit ' +
+                forwarderNameWithSuffix
         );
         return;
     }
@@ -941,17 +945,19 @@ function register(config) {
     }
 
     if (isObject(config.kits)) {
-        config.kits[name] = {
+        config.kits[forwarderNameWithSuffix] = {
             constructor: constructor,
         };
     } else {
         config.kits = {};
-        config.kits[name] = {
+        config.kits[forwarderNameWithSuffix] = {
             constructor: constructor,
         };
     }
     window.console.log(
-        'Successfully registered ' + name + ' to your mParticle configuration'
+        'Successfully registered ' +
+            forwarderNameWithSuffix +
+            ' to your mParticle configuration'
     );
 }
 
@@ -960,6 +966,9 @@ if (window && window.mParticle && window.mParticle.addForwarder) {
         name: name,
         constructor: constructor,
         getId: getId,
+        // A suffix is added if there are multiple different versions of
+        // a client kit.  This matches the suffix in the DB.
+        suffix: suffix,
     });
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@mparticle/web-braze-kit",
-    "version": "3.0.6",
+    "version": "3.0.8",
     "author": "mParticle Developers <developers@mparticle.com> (https://www.mparticle.com)",
     "description": "mParticle integration sdk for Braze",
     "main": "dist/BrazeKit.common.js",
@@ -31,7 +31,7 @@
     },
     "dependencies": {
         "@braze/web-sdk": "^3.5.0",
-        "@mparticle/web-sdk": "^2.17.0"
+        "@mparticle/web-sdk": "^2.23.0"
     },
     "license": "Apache-2.0"
 }

package/CHANGELOG.md

@@ -1,57 +0,0 @@
-## Releases
-
---
-
-#### 3.0.5 - 2023-02-15
--   refactor: Update console warning and readme to reflect new rollout plans (#19)
-
-#### 3.0.5 - 2022-10-20
--   docs: Update README to alert developers about v4 kit upgrade date, add console warning to current CDN users (#15)
-
-#### 3.0.4 - 2022-09-06
--   fix: Add Transaction Id to Purchase Commerce Events
-
-#### 3.0.3 - 2022-08-24
--   feat: Add logging for debugging
-
-#### 3.0.2 - 2022-06-16
--   fix: add register_inapp and pushPrimer variables
-
-#### 3.0.1 - 2022-05-18
-
--   consume initOptions customFlags - this allows a customer to pass a callback to include additional options that mParticle doesn't support in the UI
-
-#### 3.0.0 - 2022-03-28
-
-⚠️ **Breaking** - If you reference any of the below deprecations and implement mParticle via snippet, you will have to make changes to your codebase before June 8, 2022 to be compatible with both version 2 and version 3 of the Braze SDK to ensure your code continues to work.
-* Our partner, Braze, has made a few significant changes to their web SDK.  As a result, we are also updating our mParticle Braze web kit to support Braze’s Web SDK version 3.5.0, which includes breaking changes to the Braze SDK behavior.  The updated mParticle Braze Web kit will be available via CDN on June 8, 2022 and is currently available on NPM at @mparticle/web-braze-kit v3.0.0.  Also note that we have updated the name of our npm package from @mparticle/web-appboy-kit to @mparticle/web-braze-kit.
-* We highly recommend that you review the changes between version 2 and 3 of the Braze Web SDK to understand these changes, which can be found here.  To summarize:
-  * The `appboy.ab` namespace has been removed and everything lives under the `appboy` namespace now.
-  * `InAppMessage.Button` has been renamed to `InAppMessageButton`
-* Full details can be found in the README at our [AppBoy Repo](https://github.com/mparticle-integrations/mparticle-javascript-integration-appboy#readme).
-
-#### 2.0.7 - 2022-02-09
-
--   Feat - add new Braze clusters
-
-#### 2.0.6 - 2020-12-10
-
--   Feat - Add additional Braze clusters to URL mapping table
-
-#### 2.0.5 - 2020-06-04
-
--   Update Braze to 2.5.2
-
-#### 2.0.4 - 2020-02-12
-
--   Send SKU if forwardSkuAsProductName is set
-
-#### 2.0.2 - 2020-01-23
-
--   Feat - Set event name sent to Braze as user provided pageName
-
-#### 2.0.1 - 2019-12-03
-
--   Bugfix - Respect userId choice in mParticle UI dropdown
--   Add version number
--   Remove isObject dependency