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

use-log

v1.1.0

Published

Log a state or prop every time it changes

Downloads

10

Readme

useLog CI Publish

Log a state or prop every time it changes

Usage

Install it:

$ yarn add use-log

Import it:

import useLog from 'use-log';

Use it:

function MyComponent() {
  const [value, setValue]= React.useState("")
  useLog(`The value is ${value}`);
  return <input value={value} onChange={event => setValue(event.target.value)}>
}

Now you will get a log with The value is ${value} everytime the message change, this will happen everytime the value change.

Log objects or arrays

When using it with an object or array as value to log you may want to memoize it to avoid the log running on every render:

function MyComponent() {
  const [value, setValue]= React.useState("")
  useLog(React.useMemo(() => ({ value }), [value]));
  return <input value={value} onChange={event => setValue(event.target.value)}>
}

Configuration

useLog receives an optional configuration object as second argument with the following interface:

interface Config {
  level?: 'log' | 'info' | 'warn' | 'error' | 'debug' | 'dir' | 'table';
  shouldLogInProduction?: boolean;
}

Changing the log level

You can change the log level this way:

function MyComponent() {
  const [value, setValue]= React.useState("")
  useLog(`The value is ${value}`, { level: "debug" });
  return <input value={value} onChange={event => setValue(event.target.value)}>
}

This will basically change the console method useLog is calling.

Production-safe

You can keep the hook in your code and the code will do nothing in production by default, if you want to enable it in production environments you can set shouldLogInProduction to true.

function MyComponent() {
  const [value, setValue]= React.useState("")
  useLog(`The value is ${value}`, { shouldLogInProduction: true });
  return <input value={value} onChange={event => setValue(event.target.value)}>
}

This way the log will continue working in production.

Author

License

The MIT License.