Library / SDK
Jakubantalik/Libraries.dev avatar
Jakubantalik/Libraries.dev

Libraries.dev: seven React effect libraries and the sites that demo them

High-crafted UI libraries for AI agents: Border beam, Orbs, Metal, Gooey, Image

4,776 stars289 forksTypeScriptMIT

At a glance

What is it?
Jakub Antalik's monorepo ships seven React libraries, including border-beam, liquid-gooey and thinking-orbs, as separate npm packages, with standalone demo sites for beam, gooey and orbs and the libraries.dev site for all of them. The interesting part is not the effects. It is how the publishing, hosting and history are wired.
Who is it for?
Adopt this if you want a single npm package for one specific effect and you are fine with each package being versioned and published on its own. Do not adopt it if you need a design system with a stable API surface across versions, because the README describes seven separate effects.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 5 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Jakubantalik/Libraries.dev4,776 ★ · +1,682
Star history
Repository2026-09-112026-11-15
Jakubantalik/Libraries.dev3.1k4.8k

1,682 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Three npm packages, not one component library

The repository publishes seven libraries, among them border-beam for a glow that rides a card's border, liquid-gooey for pieces that merge and morph, and thinking-orbs for nine loading states for AI interfaces; the others are bot-avatars, voice-glow, metal-fx and img-fx. Each is installed on its own (npm install border-beam, npm install liquid-gooey, npm install thinking-orbs and so on), and beam, gooey and orbs each have a demo site on a subdomain of jakubantalik.com. There is no umbrella package that re-exports them. If you want two of the effects, you add two dependencies. That is a deliberate shape rather than an oversight: the repo layout puts one folder per npm package under packages/, and the README notes that each package folder has its own README and LICENSE. The audience is React developers who need one visual effect and do not want to pull in a larger component framework to get it.

What the monorepo layout actually buys you

The top level splits into packages/ (published libraries) and sites/ (the demo sites, with sites/home being libraries.dev). npm workspaces means a single npm install at the root covers every package and every site. The README states that the standalone demos (@sites/beam, @sites/gooey, @sites/orbs) alias their library to its source, so editing a library hot-reloads its site with no rebuild step. That is the concrete benefit of keeping demos in the same repo as the code they demo: the feedback loop on an animation tweak is a file save rather than a build and a publish. It also means the demo site is not a snapshot of a released version. It runs against whatever is on your branch, so a demo that looks correct locally can differ from what a user gets from npm.

Running a demo locally and building a package

The README gives the commands directly. Install once at the root, then run npm run dev -w @sites/home for libraries.dev with every page and the Studio. Building is per target: npm run build:beam, npm run build:gooey, npm run build:orbs for a single library, and npm run build:site-beam, npm run build:site-gooey, npm run build:site-orbs for a library plus its site; npm run build:site-home builds every library plus libraries.dev, which the README says is what CI does. npm run typecheck covers every workspace. Node is pinned to 20 through a .node-version file, and the README explains why: it matches the version the GitHub workflows use, and Cloudflare's default is older. If you fork this and deploy to Cloudflare Pages, that pin is the difference between a build that matches CI and one that quietly runs a different runtime.

Publishing is per package and triggered by a GitHub release

The README states that publishing runs through publish.yml and executes npm publish -w <package>, either by running the workflow by hand with the package name or by publishing a GitHub release whose tag is <package>@<version>, such as [email protected]; a version the registry already has is skipped. Recent releases are [email protected] on 2026-09-17, v1.3.0 on 2026-07-02 and v1.2.0 on 2026-06-09.

Three sites, three hosting paths, one CNAME file

The deploy setup is the part most likely to confuse someone who forks this. beam.jakubantalik.com runs on GitHub Pages through .github/workflows/deploy.yml, and its domain binding lives in sites/beam/public/CNAME. gooey.jakubantalik.com and orbs.jakubantalik.com run on Cloudflare Pages, built with npm run build:site-gooey and npm run build:site-orbs, output to sites/gooey/dist and sites/orbs/dist. libraries.dev is also Cloudflare Pages, deployed by .github/workflows/deploy-home.yml on every push to main with npm run build:site-home and output sites/home/dist, and its backend is api.libraries.dev, a Worker in a private repository called libraries-pro that is not part of this repo. One operational note in the README is easy to miss and costs time: Cloudflare's Retry deployment replays the same commit rather than fetching the branch tip, so a build that failed on an outdated commit keeps failing until you push a new one.

The thinking-orbs history problem

Where this is the wrong tool

The repository README describes seven visual effects and the machinery around them, and says each package's README documents its props. If your requirement is a component library with a compatibility policy, check the package you need first. There is also a licensing wrinkle worth checking yourself: the repository is MIT, but the README says each package folder has its own LICENSE file, so verify the file inside the package you install. On the alternative side, the obvious comparison is a general animation library such as Framer Motion or GSAP, where you compose effects yourself from primitives. The difference in approach is the opposite of this project's: those give you a general system and you build the beam, the gooey morph or the orb loader; Libraries.dev gives you the finished effect and nothing else. If you need five related effects that share timing and easing conventions, a general library will fit better than five separate packages. If you need exactly one effect and want it to look right without designing the motion, the narrower package is less work.

Editorial conclusion

Adopt this if you want a single npm package for one specific effect and you are fine with each package being versioned and published on its own. Do not adopt it if you need a design system with a stable API surface across versions, because the README describes seven separate effects. Before installing, read the README inside the package directory you intend to use, which documents its props, and confirm the licence file that ships with that package.

Frequently asked questions

What do the Libraries.dev packages need to run?

React 18 or newer. Each library is a standalone package with zero runtime dependencies, and the image loader is the only one that also needs three as a peer dependency.

How do you install one of these libraries?

Either copy the prompt from the library page and paste it into Claude Code, Cursor or Codex so the agent installs and wires it in, or run the npm install line for that package. Both routes end at the same component wrapping the element you already have.

Can I use these libraries in a commercial project?

Yes. The libraries are MIT and usable anywhere, including commercial work. What the Pro plan buys is the Studio, the Pro presets, configuration export and future libraries and updates, licensed to you or your team under the plan you buy.

Do the Libraries.dev effects follow a site's own light and dark mode?

With the default theme="auto", a data-theme attribute or a dark class on an ancestor is resolved first, then prefers-color-scheme, and the component updates live when either changes. Passing theme="dark" or theme="light" pins one instead.

What has to be built before the Libraries.dev home site will work?

The library packages, because the home site imports the built output rather than the sources. The root manifest chains eight package builds inside npm run build:site-home before it builds the home workspace itself.

Official sources

  1. Jakubantalik/Libraries.dev on GitHub
  2. License: MIT
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/jakubantalik-libraries-dev.svg)](https://hysenlabs.com/projects/jakubantalik-libraries-dev)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/jakubantalik-libraries-dev.svg)](https://hysenlabs.com/projects/jakubantalik-libraries-dev)

Was this useful?