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 🙏

© 2026 – Pkg Stats / Ryan Hefner

react-component-tracker

v1.0.16

Published

Easily track components props without using breakpoints, console.log manually or debugger.

Readme

react-component-tracker

Easily track components props without using breakpoints, console.log manually or debugger.

Installation

npm install react-component-tracker

Basic Usage

Just wrap the component you wish to track with the withPropsTracking method, set mode to Development and you got the logs.

import React from "react";
import ComponentTracker from "react-component-tracker";

const MyComponent = ({ prop1, prop2 }) => {
    return (
        <div>
            <div>{prop1}</div>
            <div>{prop2}</div>
        </div>
    );
};

export default ComponentTracker.withPropsTracking(MyComponent)({
    mode: ComponentTracker.DevelopmentMode.Development
});

API

mode (Enum) - Current development mode, logging occurs only in DEVELOPMENT mode.

logType (Enum) - The method of logging out the props, table or each prop in a new line.

trackedProps (Array of strings) - List of props to track. only those props would be tracked. Good usage for trackedProps is when you have a component with large number of props, and you want to track only few of them.

ignoredProps (Array of strings) - List of props to ignore in the log. not relevant if trackedProps sent as well. Good usage for ignoredProps is when you have a prop which you don't care about, and holds long value, removing it from the log would help you focus on the props that's actually you care about.

Logs types & output (logType options) -

PropPerLine -

basiclog

Table -

table

Production & Development modes

Valid options for mode are PRODUCTION and DEVLEOPMENT.

If mode is set to DEVLEOPMENT - logs would be printed out.

If mode is set to PRODUCTION, no logs would be shown. You don't have to remove the calls for withPropsTracking before you deploy to production, since react-component-tracker not adding any DOM elements or doing any login in production mode.

NOTE: react-component-tracker also considers NODE_ENV to figure out the mode in addition to the user mode setting (if it was set). if NODE_ENV value is production - the log won't be printed.

License

MIT