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

@rojaostudio/ds-core

v1.1.2

Published

O motor do Rojão DS — tokens, derivação de tema e emissores. Sem React, sem Tailwind, sem CSS.

Readme

@rojaostudio/ds-core

The engine behind Rojão DS: design tokens, theme derivation, emitters.

No React. No Tailwind. No framework-coupled CSS — emitCss returns plain custom properties that work anywhere CSS does.

npm i @rojaostudio/ds-core
import { generateRdsTheme, emitRdsCss, emitClaudeMd } from '@rojaostudio/ds-core/generate';

const brand = {
  name: 'acme',
  brand: { primary: '#7C3AED' },
  surface: 'neutral',
  text: 'neutral',
  fonts: { body: 'inter' },
};

emitRdsCss(generateRdsTheme(brand)); // rds-theme.css — import it AFTER @rojaostudio/ds/styles/rds.css
emitClaudeMd(brand);                 // the same brand as rules for Claude Code, Cursor or AGENTS.md

Or, without writing code: npx rojao-ds init (the rojao-ds CLI) writes both files into your project.

One color goes in. What comes out is an OKLCH scale with an adaptive contrast floor, semantic roles for surface, text, border and brand, and the full light/dark pair — verified against WCAG AA on all three surfaces, by test, on every build.

Why this is a separate package

It used to be one package, and its peerDependencies forced React 19 and Tailwind 4 on anyone who only wanted tokens — a consumer depending on what it doesn't use. The boundary already existed in the code: this directory has never imported React. It just didn't exist in the packaging.

Components, styles and the React Native target live in @rojaostudio/ds.

API

| Entry | What's in it | |---|---| | @rojaostudio/ds-core/generate | generateRdsTheme, rdsThemeFromTable, emitRdsCss, emitClaudeMd, rdsBrandColors, deriveAccent, generateTheme/emitCss (1.x), buildScale, contrastRatio | | @rojaostudio/ds-core/tokens | primitives — the raw palettes and scales | | @rojaostudio/ds-core/recipes | the reference brand definition | | @rojaostudio/ds-core/themes | the preset catalogue: a starting palette per niche |

Em português

O site é em português e faz isso sem escrever código: ds.rojao.ai — você joga sua logo, ele tira a cor e devolve o tema pronto para colar no projeto.

License

MIT — see LICENSE. The name and logo are not: see TRADEMARK.md.

What comes out of the engine is yours. The theme.css and CLAUDE.md generated from your brand carry no license obligation at all. Use them commercially, ship them to clients, sell them. The engine is MIT; the output isn't ours.