The VWO Node.js SDK (current version 1.73.0) provides capabilities for server-side A/B testing and experimentation, allowing developers to implement features like experiment activation, goal tracking, and feature toggles within their Node.js applications. It can also be used for client-side JavaScript environments. This SDK is currently in a deprecated status, meaning it is no longer actively developed for new features or enhancements; it only receives critical bug and security fixes. VWO recommends migrating to their 'Feature Management & Experimentation (FME)' product for ongoing development and support. The package features include a retry mechanism for HTTP calls and, as of v1.73.0, support for proxying all network requests, which can be useful for bypassing ad-blockers or routing traffic.
npm install vwo-node-sdkVerified import paths — ran on the pinned version, not inferred.
This code demonstrates how to initialize the VWO SDK, fetch settings, activate a user in a campaign, and track a goal conversion.
Migrate to VWO Feature Management & Experimentation (FME) product for continued support and new features. Refer to VWO's official migration guide.
Upgrade to v1.72.0 or higher to benefit from the built-in retry mechanism. Implement robust error handling around `VWO.getSettingsFile`.
Upgrade to v1.73.0 and configure the `proxyUrl` option in `VWO.getSettingsFile` to route traffic through a controlled proxy server if experiencing network blocking issues.
Upgrade to v1.71.0 or newer to ensure correct TypeScript definitions for integration callbacks.
Ensure `VWO.init` is called directly on the imported module (e.g., `const vwoClient = VWO.init(settings);`) and not on a `vwoClient` instance itself. Confirm you are using `import VWO from 'vwo-node-sdk'` or `const VWO = require('vwo-node-sdk')`.Verify that `VWO_ACCOUNT_ID` and `VWO_SDK_KEY` environment variables (or direct parameters) are correctly set and non-empty when calling `VWO.getSettingsFile`.
Check network connectivity, verify `accountId` and `sdkKey`. If running behind a proxy or with ad-blockers, consider upgrading to v1.73.0 and utilizing the `proxyUrl` option in `getSettingsFile`.
No dependency data recorded yet.