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-trace

v0.3.5

Published

Tracing library to detect rerender causes and state changes

Downloads

37

Readme

useTrace

Tracing Library to understand state changes

This library is built to help understanding state changes triggering rerenders. The gihub project contains an example project using the library.

Output

Props is any props you pass to the hook.

Usage

Initialization

Initialize the trace in the first line of the component.

function App() {
const trace = useTrace("App");

Optionally pass the props:

function MyComponent({hello, world}) {
const trace = useTrace("MyComponent", {hello, world});

Alt:

const MyComponent = (props: MyComponentProps) => {
const trace = useTrace("MyComponent", props);

The trace will let you know what the initial props is, and always when the props changes.

Internal state

Log the internal state changes using the state function. Once per component/function.

trace.state({ value1, object1, functionA });

Whenever one or many of the fields change, you will get notified about the previous and current value.

Exit

On all exit points you need to call exit.

trace.exit();

You can also add an optional log statement.

trace.exit("Rendering loading spinner");

Log statements

trace.log(
  "This statement is indented at the current function level, and bold by default"
);

The function signature is identical to console.log.