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

matsuri-hooks

v4.2.22

Published

<!-- vscode-markdown-toc --> <!-- prettier-ignore --> - [Matsuri Hooks](#matsuri-hooks) - [Motivation](#motivation) - [Usage](#usage) - [Installation](#installation) - [Examples](#examples) - [useFetch](#usefetch) - [Conditional fetch]

Readme

Matsuri Hooks

Motivation

  • Provide complex processing with safety guaranteed by testing
  • Be common processing for each product

Usage

Installation

yarn add matsuri-hooks swr

Examples

useFetch

const { data, error, refetch } = useFetch<{ species: "fish" }>(
  "https://example.com/fish",
  { method: "GET" },
);

return (
  <div>
    <p>Species: {data?.species}</p>
    <button onClick={refetch}>Refetch</button>
    {error ? (
      <p>
        {error.name}: {error.message}
      </p>
    ) : null}
  </div>
);

Conditional fetch

const [prefId, setPrefId] = useState<string>();
const { data } = useFetch<{ cityId: string }[]>(
  prefId ? `https://example.com/${prefId}/cities` : null,
);

Auto refetch

dependenciesを指定することで、dependenciesが変わった際に再取得される。

const { data: prefecture, refetch } = useFetch<Prefecture>(getPrefecture());
const { data: cities } = useFetch<City[]>(getCities(), {
  dependencies: [prefecture?.id],
});

// dependenciesで紐づけられているため、prefectureのidが変わっていればcitiesも再取得される
refetch();

Convenient errors

Errorオブジェクトからレスポンスのステータスを取得できる。

const { error } = useFetch<Response>("https://example.com/fish");

if (error.status === 404) {
  console.log("Not Found Error");
}

Responseがfalsyであり且つJSONフレンドリーであればパースした結果を受け取れる。

const { error } = useFetch<Response>("https://example.com/fish");

console.log(error.message)
// 500: {errorType: too_many_fish}

if(error.parse()?.errorType === "too_many_fish){
  console.log("Too many fish")
}

パースされた結果に型を当てることも出来る。

type ErrorType = "too_many_fish" | "not_found_fish";
interface ParsedError {
  errorType: ErrorType;
}
const { error } = useFetch<Response, ParsedError>("https://example.com/fish");

useAuthFetch

This default token format is X-Access-Token: [TOKEN].

const { token } = useAuth()
const { error, refetch } = useAuthFetch<never>(token, "https://example.com", { method: "POST", ... )
  • useAuthBearerFetch:this default token format is Authorization: Bearer [TOKEN].

useRequest

useRequestはkey周りの過剰な配慮を撤廃したuseFetchである。フェッチオプションをオブジェクトとして渡すことができ、SWRを十分に理解していれば、より高度なデータ管理が行えるようになる。SWRを直接使いながらも、matsuri-hooksのエラーハンドリングなどの機能を活用できる。

const { data, error, refetch, isLoading, isValidating } =
  useRequest<ResponseType>(
    "/foo", // SWR key
    {
      url: "/foo",
      method: "GET", // オプション: デフォルトはGET
      body: JSON.stringify({ param: "value" }), // オプション
    },
  );

より複雑なキャッシュシナリオのために、配列をキーとして使用することもできる:

const { data } = useRequest([key1, key2], {
  url,
  body: JSON.stringify(input),
  method: "POST",
});

SWRの設定は第三引数として渡すことができる:

const { data } = useRequest(
  key,
  {
    url,
    method: "GET",
  },
  {
    revalidateOnFocus: false,
    dedupingInterval: 5000,
  },
);

useAuthRequest

X-Access-Tokenヘッダーを使用した認証リクエスト:

const { data } = useAuthRequest(key, {
  url: "/protected-endpoint",
  token: userToken,
  method: "POST",
  body: JSON.stringify(payload),
});

トークンが空の場合、リクエストは行われません。

カスタムフックの作成例

useRequestとuseAuthRequestを使用して、カスタムフックを作成することができる:

// よくあるuseFetchの記述置き換え
const useCustomRequest = (token, id, input) => {
  const url = endpoint({ id });
  return useAuthRequest(url, {
    url,
    token,
    body: JSON.stringify(input),
    method: endpoint.method,
  });
};

// 以前とほぼ同じ動作を再現する例
const useCustomRequest = (token, id, input) => {
  const url = endpoint({ id });
  const options = {
    url,
    body: JSON.stringify(input),
    method: endpoint.method,
    token,
  };
  return useAuthRequest(options, options);
};

useAuthBearerRequest

Authorization: Bearer [TOKEN]ヘッダーを使用した認証リクエスト:

const { data } = useAuthBearerRequest(key, {
  url: "/protected-endpoint",
  token: userToken,
  method: "GET",
});

createFetcher

createFetcherはSWRで直接使用するためのフェッチャー関数を作成するユーティリティ関数である。これにより、SWRを直接使用しながらも、matsuri-hooksのエラーハンドリングやトークン管理の恩恵を受けることができる。

import useSWR from "swr";
import { createFetcher } from "matsuri-hooks";

const MyComponent = ({ token }) => {
  const { data, error } = useSWR(
    "key",
    createFetcher({
      url: "/api/endpoint",
      token,
      method: "POST",
      body: JSON.stringify({ param: "value" }),
    }),
  );

  // データの使用とエラーハンドリング
};

useIntersectionObserver

const ref = useRef(null);
const { entry, disconnect } = useIntersectionObserver(ref, { threshold: 0.1 });

const [image, setImage] = useState<string>();

useEffect(() => {
  if (entry) {
    const fetchImage = async () => {
      //...
      return image;
    };
    disconnect();
    setImage(fetchImage());
  }
}, []);

return <img ref={ref} src={image || "dummy.png"} />;

useOnClickOutside

const [open, setOpen] = useState(false);
const ref = useRef(null);
useOnClickOutside(ref, () => {
  setOpen(false);
});
return (
  <div>
    <button onClick={() => setOpen(true)}>OPEN</button>
    <Modal ref={ref} open={open} />
  </div>
);

useKeyboardShortcut

If the specified key and control or meta key are pressed together, the second argument callback is executed.

const [open, setOpen] = useState(false);
const ref = useRef(null);
useKeyboardShortcut("j", () => {
  setOpen(true);
});
return (
  <div>
    <Modal ref={ref} open={open} />
  </div>
);

useClipboardCopy

If the specified key is pressed together with a control or meta key, or if the return method is called, the specified text is copied to clipboard. Then, if the copy fails, onFailure is called, and if it succeeds, onSuccess is called.

const [open, setOpen] = useState(false);
const ref = useRef(null);
const copy = useKeyboardShortcut(SOME_TOKEN, {
  key: "j",
  onSuccess: () => {
    addAlert("Success");
  },
  onFailure: () => {
    addAlert("Failed", { type: "error" });
  },
});
return (
  <div>
    <Button onClick={copy} />
  </div>
);