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

@rym-lib/seeder

v1.9.0

Published

`Seeder.load(table_name, pk, columns, records, options?)` でレコードを投入する。

Readme

nakadachi-interactor-mixin-validator

load

Seeder.load(table_name, pk, columns, records, options?) でレコードを投入する。

  • 500 行(列数が多いと縮む)ごとに、WHERE pk IN (...) の SELECT 1 本と複数行 INSERT 1 本にまとめ、既存行との差分がある行だけを 1 行ずつ UPDATE する
  • 主キーの重複や、DB 側との突き合わせ(照合順序・末尾空白・型の違い)のずれがあるチャンクは、1 行ずつ処理する
  • 正常に終わった場合の最終状態は、1 行ずつ処理した場合と同じになる。次の点は同じとは限らない
    • 失敗時に残る途中の状態
    • INSERT と UPDATE の実行順(チャンク内では INSERT が先)
    • 発行する文の本数(文単位のトリガの発火回数)
    • チャンク内の created_at / updated_at の値(同じ時刻になる)
  • 一括 INSERT が失敗したら、やり直さずに元の例外をそのまま投げる。そのチャンクの UPDATE は実行しない。トランザクション内で呼んでもよい

結合テストの実行

PostgreSQL と MySQL の実 DB に対して Seeder.load を検証する。

docker compose -f compose.yaml up -d --wait
npm run test:integration

ポートは 5472(PostgreSQL)と 3326(MySQL)に固定されている。複数の worktree で同時に走らせるときは、SEEDER_TEST_POSTGRES_URL と SEEDER_TEST_MYSQL_URL で別の DB を指す。