Skip to content
OTFotf
All posts

Why OTF Ships Components Two Ways: Copy-Paste vs. npm Package

O
OTFAuthor
Why OTF Ships Components Two Ways: Copy-Paste vs. npm Package

Every component library has a distribution story. Most pick one — copy-paste or package — and defend it like a religion. The honest version is less comfortable: both work, neither is universal, and forcing a single model on every buyer is how you turn a useful primitive into a tribal argument.

We ship components two ways on purpose. Here's what each one actually trades off, and why the third option — same component, two delivery shapes — is the only one that respects how builders actually work.

[[COMPARE: copy-paste ownership vs npm ownership]]


This is an excerpt. Read the full post at otf-kit.dev/blog/copy-paste-or-npm-install — full-stack kits your AI coding agent can actually ship to production. Browse the kits →

design systemReact Nativebackend
OTF SaaS Dashboard Kit

Ship the product, not the setup.

  • 11 production screens — auth, billing, team, analytics, settings
  • Real database, payments, and login — all wired on day 1
  • AI configs pre-tuned so your agent extends instead of regenerates