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

@texmeijin/use-aspida-caller

v0.1.4

Published

React Hooks for getting callers and states by aspida

Downloads

3

Readme

useAspidaCaller

React Hooks for calling type-safe REST APIs with aspida.

⚠️This hook is PoC.⚠️

Usage

const Home: NextPage = () => {
  const [getResult, setGetResult] = useState<{ name: string }>();
  const {
    get,
    isGetting,
    isGetSuccessful,
    getError,
    put,
    isPutting,
    isPutSuccessful,
    putError,
  } = useAspidaCaller(client.people._id(1));

  const handleGetClick = async () => {
    setGetResult(await get({ query: { with_detail: true } }));
  };
  const handlePutClick = async () => {
    await put({ body: { name: "hoge" } }).catch((err) => null);
  };

  return (
    <div className={styles.container}>
      <main className={styles.main}>
        <button onClick={handleGetClick}>Get Value</button>
        {isGetting && <p className={styles.description}>Loading...</p>}
        <p className={styles.description}>
          Result: {getResult?.name} / {isGetSuccessful && "Success!"}
        </p>
        <button onClick={handlePutClick}>Put Value</button>
        {isPutting && <p className={styles.description}>Loading...</p>}
        <p className={styles.description}>
          Error: {putError?.message} / {isPutSuccessful && "Success!"}
        </p>
      </main>
    </div>
  );
};

TODO

  • [ ] ❤️ READMEにaspidaなどの背景知識を記載
  • [ ] ❤️ READMEに解決したい課題を記載
  • [ ] ❤️ aspidaのメソッドに応じて返り値のオブジェクトのキーが変わる点を記載
  • [ ] ❤️ ステータスを返すことで、フォームでの用途に特に便利である点を記載
  • [ ] 💀 細かいテストケースが網羅できていないので地道に追加
  • [ ] 💀 テストは通っているが実際に使ったわけではないので実アプリケーションにて挙動を確認する
  • [ ] ⏳ GitHub Actionsを用いて、Pull Requestに対してLint、TSCを実行する
  • [ ] ⏳ GitHub Actionsを用いて、npm publish周りのワークフローを自動化できないか調べる/実践する
  • [ ] 😊 contributeセクションを作成し、tsdによる型テストと、vitestによるユニットテストを記載している点を明記
  • [ ] 🎌 英語版READMEを作成、日本語版と切り替えられるようにする(本家aspidaなどを参考)
  • [ ] 🎌 日本語にて解説記事を書いて公開
  • [ ] 🎌 英語にて解説記事を書いて公開