
Product
Reachability for Ruby Now in Beta
Reachability analysis for Ruby is now in beta, helping teams identify which vulnerabilities are truly exploitable in their applications.
@spark-web/analytics
Advanced tools
Set of unopinionated, lightweight React components for implementing analytics tracking with composable event contexts.
To use Analytics please wrap your app with at least one AnalyticsListener,
which allows you to provide a callback for tracking events.
For example:
// hypothetical analytics backend
import analyticsClient from './utils/analytics';
export function App({ Component, pageProps }) {
// Here is where we handle events
const handleAnalyticsEvent = (eventName, eventData) => {
console.log(`Received event ${eventName}`);
analyticsClient.sendEvent(eventName, eventData);
};
return (
<AnalyticsListener onEvent={handleAnalyticsEvent}>
<Layout>
<Component {...pageProps} />
</Layout>
</AnalyticsListener>
);
}
It's possible to nest and stack multiple listeners, which will be invoked independently whenever an event is fired, i.e.:
<AnalyticsListener onEvent={sendToLegacyBackend}>
<AnalyticsListener onEvent={sendToNewBackend}>
<Layout>
<Component {...pageProps} />
</Layout>
</AnalyticsListener>
</AnalyticsListener>
AnalyticsContext allows transient, universal analytics properties that will be
automatically appended to all fired events. This is useful to reduce duplication
and automatically include global properties such as configuration or
environment.
<AnalyticsListener onEvent={sendToAnalyticsBackend}>
<AnalyticsContext data={{ browser: navigator, isLoggedIn }}>
<Layout>
<Component {...pageProps} />
</Layout>
</AnalyticsContext>
</AnalyticsListener>
Context can be nested to append additional data inside the component structure.
<AnalyticsListener onEvent={sendToAnalyticsBackend}>
<AnalyticsContext data={{ browser: navigator, isLoggedIn }}>
<Header>
<AnalyticsContext data={{ usingNavbar: 'main-navbar' }}>
<Navbar id="main-navbar">
<Button>Option 1</Button>
<Button>Option 2</Button>
</Navbar>
</AnalyticsContext>
</Header>
<MainContent />
<Footer>
<AnalyticsContext data={{ usingNavbar: 'footer-navbar' }}>
<Navbar id="footer-navbar">
<Button>Option 1</Button>
<Button>Option 2</Button>
</Navbar>
</AnalyticsContext>
</Footer>
</AnalyticsListener>
</AnalyticsListener>
useAnalytics provides a function to fire events from custom components.
Example usage:
function ExpandingContainer({ children, id }) {
const { expanded, setExpanded } = useState(false);
const { trackEvent } = useAnalytics();
const onClick = useCallback(() => {
setExpanded(previousState => {
const nextState = !previousState;
const eventName = nextState
? 'container-expanded'
: 'container-collapsed';
trackEvent(eventName, { containerId: id });
return nextState;
});
}, [id]);
return (
<>
<button onClick={onClick}>
{expanded ? 'Collapse' : 'Expand'} container
</button>
<Container>{expanded ? children : null}</Container>
</>
);
}
FAQs
--- title: Analytics isExperimentalPackage: true ---
The npm package @spark-web/analytics receives a total of 115 weekly downloads. As such, @spark-web/analytics popularity was classified as not popular.
We found that @spark-web/analytics demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers 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.

Product
Reachability analysis for Ruby is now in beta, helping teams identify which vulnerabilities are truly exploitable in their applications.

Research
/Security News
Malicious npm packages use Adspect cloaking and fake CAPTCHAs to fingerprint visitors and redirect victims to crypto-themed scam sites.

Security News
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.