
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
If this component helped you or your team, please give it a GitHub 🌟!
yarn add ab-react
or
npm install -S ab-react
This is mainly for AB testing, it will work with multiple children but try to stick with two.
In the following example, three things can happen:
1 - The ABReact component will randomize one of the children and store the value on a cookie, after that the user will always see the same version.
2 - If a version is set on the cookie with the defined cookie name, that version will be rendered.
3 - If a version is set on the cookie with the defined cookie name but the child doesn't exist null will be returned.
No matter what scenario happens, the trackVersion event will be called each time the component is rendered.
import * as React from 'react';
import { useCallback } from 'react';
import ABReact from 'ab-react';
export default function MyComponent() {
const trackVersion = useCallback((version: number) => {
gtag('event', 'screen_view', {
'screen_name': 'MyComponent',
'version': version,
});
});
return (
<ABReact cookieName='cookie-name-to-store-version' event={trackVersion}>
<div key="version-1">Version 1</div>
<div key="version-2">Version 2</div>
</ABReact>
)
}
If you already has a top-level CookiesProvider mounted you can set a property so the ABReact won't mount the CookiesProvider internally:
import * as React from 'react';
import { useCallback } from 'react';
import ABReact from 'ab-react';
export default function MyComponent() {
return (
<ABReact cookieName='cookie-name' mountCookieProvider={false}>
<div key="version-1">Version 1</div>
<div key="version-2">Version 2</div>
</ABReact>
)
}
If you want to force a version to be rendered (to disable one or to maintain SSR consistency), you can set the property forceVersion:
import * as React from 'react';
import { useCallback } from 'react';
import ABReact from 'ab-react';
export default function MyComponent() {
return (
<ABReact cookieName='cookie-name' forceVersion={1}>
<div key="version-1">Version 1</div>
<div key="version-2">Version 2</div> {/* This version will always be rendered */}
</ABReact>
)
}
Using only CSR (Client Side Rendering)
import { useState, useCallback } from 'react';
import ABReact from 'ab-react';
export default function ABTesting() {
const [selectedState, setSelectedState] = useState<string>('');
const eventExample = useCallback((version: number) => {
setSelectedState(version.toString());
/**
* Do any tracking here such as sending an event to Google Analytics
*/
}, [setSelectedState]);
return (
<div>
<h1>Normal scenario for a pure client side rendering (CSR)</h1>
<ABReact cookieName='cookie-1' event={eventExample}>
<div>1</div>
<div>2</div>
</ABReact>
<p>Selected version for cookie-1 (returned by the callback): { selectedState }</p>
</div>
);
}
Using SSR (Server Side Rendering), CSR (Client Side Rendering) and AppRouter
page.tsx:
/* file: page.tsx */
import { cookies } from 'next/headers';
import Components from './components';
export default function ABTestings() {
const v1 = Number(cookies().get('cookie-1')?.value);
const v2 = Number(cookies().get('cookie-2')?.value);
console.log(cookies().get('cookie-1'));
return (
<div>
<Components v1={Number.isNaN(v1) ? undefined : v1} v2={Number.isNaN(v2) ? undefined : v2} />
</div>
);
}
components.tsx:
/* file: components.tsx */
'use client';
import { useState, useCallback } from 'react';
import ABReact from 'ab-react';
export default function Components({ v1, v2 }: { v1?: number, v2?: number }) {
const [selectedState, setSelectedState] = useState<string>('');
const eventExample = useCallback((version: number) => {
setSelectedState(version.toString());
/**
* Do any tracking here such as sending an event to Google Analytics
*/
}, [setSelectedState]);
return (
<div>
<h1>Normal scenario, after SSR forces version from v1</h1>
<ABReact cookieName='cookie-1' forceVersion={v1}>
<div>1</div>
<div>2</div>
</ABReact>
<h1>Another scenario, after SSR forces version from v2 and runs an callback when the version is rendered</h1>
<ABReact cookieName='cookie-2' event={eventExample} forceVersion={v2}>
<div>1</div>
<div>2</div>
</ABReact>
<p>Selected version for cookie-2 (returned by the callback): { selectedState }</p>
<h1>Forced version scenario, no internal choosing. Version hard coded.</h1>
<ABReact cookieName='cookie-3' forceVersion={1}>
<div>1</div>
<div>2 forced</div>
</ABReact>
</div>
);
}
FAQs
A/B testing component for React
The npm package ab-react receives a total of 1 weekly downloads. As such, ab-react popularity was classified as not popular.
We found that ab-react demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.