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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@morosystems/react-debug

v0.1.0

Published

Debug utils for react components.

Readme

@morosystems/react-debug

Debug utils for react components. Intended for development only, not for production

debug HOC

Lets you see in console when component mounts, unmounts, updates and why it updated:

import {debug} from "@morosystems/react-debug";

export default debug()(MyComponent);

This logs roughly the following information:

MyComponent mounts
MyComponent updates name,input
MyComponent updates error
MyComponent unmounts

Displayed information can be changed using the configuration object, e.g.:

export default debug({name: 'Test'})(MyComponent);

Alternative import

In order to not importing component all the time, you can import @morosystems/react-debug/lib/patch just once, in your main file, then use debug() directly from global namespace. You can also safely forget about removing this import for production, since it will inject debug() only when NODE_ENV is development

import "@morosystems/react-debug/lib/patch";
...
export default debug()(MyComponent);

Component name

You can specify name that is logged using the name property. You can specify:

  1. String.
  2. Function of props. This is useful when debugging one specific instance of generic component, e.g. Field.
export default debug({name: (props) => props.input.name})(Field);

Custom logging

You can also use custom messages for each lifecycle event.

  1. mount as a function from props to string.
  2. update as a function from props and next props to string.
  3. unmount as a function from props to string.

You can also supress loging by returning null, undefined or false:

const update = (props, nextProps) => (props.name !== nextProps.name) && `${props.name} updates to ${nextProps.name}`;

export default debug({update})(MyComponent);