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

@susisu/react-use-source-sink

v0.2.0

Published

Creates a pair of source and sink

Downloads

2,151

Readme

@susisu/react-use-source-sink

CI

# npm
npm i @susisu/react-use-source-sink
# yarn
yarn add @susisu/react-use-source-sink
# pnpm
pnpm add @susisu/react-use-source-sink

Usage

import React, { useEffect } from "react";
import { useSourceSink } from "@susisu/react-use-source-sink";

const Hello: React.FC = () => {
  const [source, sink] = useSourceSink<HTMLElement | null>(null);
  useEffect(() => {
    const elem = source();
    // ...
  });
  return (
    <p ref={sink}>Hello!</p>
  );
};

Why?

The following code does not pass the type check.

import React, { useRef } from "react";

const Hello: React.FC = () => {
  const ref = useRef<HTMLElement | null>(null);
  return (
    <p ref={ref}>Hello!</p>
  );
};

This is because a reference created by useRef is both readable and writable, and basically invariant in terms of types, which means it cannot be up- nor down-casted. A reference to HTMLElement cannot be passed to the ref prop of a p element, which requires a reference to HTMLParagraphElement.

To pass the type check, we can use a callback ref, which is basically contravariant and can be safely passed to a concrete element.

import React, { useRef, useCallback } from "react";

const Hello: React.FC = () => {
  const ref = useRef<HTMLElement | null>(null);
  const callbackRef = useCallback((elem: HTMLElement | null): void => {
    ref.current = elem;
  }, []);
  return (
    <p ref={callbackRef}>Hello!</p>
  );
};

useSourceSink simplifies this boilerplate.

License

MIT License

Author

Susisu (GitHub, Twitter)