npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@times-components/tracking

v2.22.15

Published

Tracking

Downloads

23,536

Readme

Tracking

Tracking is a collection of Higher-Order-Components (HOCs) that extract and report analytics of a component. All HOCs consume a component and an object describing how to create the analytics event.

The returned component expects an analyticsStream to be available in React context or to be passed directly to the component via props. Every tracking HOC passes it's analyticsStream to it's descendants via React context.

n.b. while there is a "tracking context" that uses "React context", they are not the same thing. The "tracking context" can be thought of as a "decoration boundary" between logical business layers which are useful for reporting.

Testing Components with Tracking

The analyticsStream prop is expected to be a function that consumes an event object.

To test whether your component propagates the correct events, pass jest.fn() as the analyticsStream and test if your mock received the expected events. Mind that you need to mock the Date and setTimeout to make your tests reproducible.

Example

  const events = jest.fn();
  renderer.create(<ComponentWithTracking analyticsStream={events} />);
  expect(events.mock.calls).toMatchObject(...);

Contributing

Please read CONTRIBUTING.md before contributing to this package

Running the code

Please see our main README.md to get the project running locally

Development

The code can be formatted and linted in accordance with the agreed standards.

yarn fmt
yarn lint

Testing

This package uses yarn (latest) to run unit tests on each platform with jest.

yarn test:web

Visit the official storybook to see our available tracking templates.