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

@ryvora/react-use-is-hydrated

v2.0.0

Published

💧✅ Know when your React component is hydrated on the client. SSR mismatch be gone!

Readme

use-is-hydrated 💧✅

Hello Hydration Hero! 🦸‍♀️

The use-is-hydrated hook is a utility to determine if your React component has finished "hydrating" on the client after being server-side rendered (SSR).

It's like a little sensor 🌡️ that tells you, "Okay, the JavaScript has fully taken over this part of the page!"

Why is this useful?

Sometimes, you want to render something only on the client-side, or behave differently after hydration to avoid SSR mismatches or to enable client-specific functionality (like browser APIs that aren't available during SSR).

  • Avoiding Mismatches: Ensure UI consistency between server and client.
  • Client-Only Components: Delay rendering of components that rely on browser environment.
  • Performance: Defer non-critical client-side logic until after hydration.

Basic Usage:

import { useIsHydrated } from '@ryvora/react-use-is-hydrated'; // Hook name might vary
import React from 'react';

function MyComponent() {
  const isHydrated = useIsHydrated();

  if (!isHydrated) {
    // Render a placeholder or nothing during SSR and initial client render before hydration
    return <div>Loading client-specific content...</div>;
  }

  // This will only render after hydration on the client
  return (
    <div>
      <p>Welcome! The time is: {new Date().toLocaleTimeString()}</p>
      {/* Other client-side only components or logic */}
    </div>
  );
}

// Example of a component that should only render on the client
function ClientOnlyComponent() {
  const isHydrated = useIsHydrated();
  if (!isHydrated) return null;
  return <div>I only appear on the client! ✨</div>;
}

Keep your SSR smooth and your client-side enhancements well-timed! 🕰️🚀