VWO WordPress plugin serving broken JS: republished SDK fixed the merge-conflict bundle

TL;DR

If you want updates only when you choose, pin an explicit version in the URL, like vwo-node-sdk@1.63.2.

Steps

1. Issue wingify/vwo-node-sdk#54 (closed, 16 comments): A user reported that the published vwo-javascript-sdk.min.js bundle contained unresolved git merge conflicts and was breaking the VWO WordPress plugin for clients. Maintainers first pointed at the latest unpinned CDN URL, then published a new version of the plugin/SDK as the earlier one was faulty, and confirmed the pinned @1 CDN URL reflected the fix. The reporter tried it and confirmed the error was gone.
2. If the VWO WordPress plugin is loading broken JavaScript, check the vwo-javascript-sdk bundle it pulls from the CDN: at one point the published minified file literally contained unresolved git merge conflicts. The maintainers fixed this by publishing a new version, and the reporter confirmed the error went away. Practical takeaway: the plugin loads https://cdn.jsdelivr.net/npm/vwo-node-sdk@1/dist/vwo-javascript-sdk.min.js, and @1 means you always get whatever was published most recently once the jsDelivr cache updates. If you want updates only when you choose, pin an explicit version in the URL, like vwo-node-sdk@1.63.2. And if you ever see conflict markers (<<<<<<<) inside a published bundle again, it is the vendor's release that is broken, not your site.

When to use

You are seeing this: The reporter tried it and confirmed the error was gone. Use this skill when you run into "VWO WordPress plugin serving broken JS: republished SDK fixed the merge-conflict bundle".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: vwo-node-sdk 1.63.2. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://cdn.jsdelivr.net/npm/vwo-node-sdk@1/dist/vwo-javascript-sdk.min.js

In the GitHub issue gh:wingify/vwo-node-sdk#54 (https://github.com/wingify/vwo-node-sdk/issues/54), the problem reported was: Issue wingify/vwo-node-sdk#54 (closed, 16 comments): A user reported that the published vwo-javascript-sdk.min.js bundle contained unresolved git merge conflicts and was breaking the VWO WordPress plugin for clients. Maintainers first pointed at the latest unpinned CDN URL, then published a new version of the plugin/SDK as the earlier one was faulty, and confirmed the pinned @1 CDN URL reflected the fix. The reporter tried it and confirmed the error was gone. The verified resolution was: If the VWO WordPress plugin is loading broken JavaScript, check the vwo-javascript-sdk bundle it pulls from the CDN: at one point the published minified file literally contained unresolved git merge conflicts. The maintainers fixed this by publishing a new version, and the reporter confirmed the error went away. Practical takeaway: the plugin loads https://cdn.jsdelivr.net/npm/vwo-node-sdk@1/dist/vwo-javascript-sdk.min.js, and @1 means you always get whatever was published most recently once the jsDelivr cache updates. If you want updates only when you choose, pin an explicit version in the URL, like vwo-node-sdk@1.63.2. And if you ever see conflict markers (<<<<<<<) inside a published bundle again, it is the vendor's release that is broken, not your site.