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

@tarik-leviathan/ltds

v0.4.9

Published

Leviathan Tarik Design System (tokens, utils, atoms)

Downloads

272

Readme

LTDS — Leviathan Tarik Design System

Design system minimaliste, modulaire et distribuable via npm. Inclut : tokens (couleurs, typo, scale), reset, utilitaires (spacing, grids/flex, dimensions…), layouts de base et atomes (buttons).

Installation

npm i @tarik-leviathan/ltds

Utilisation rapide (tout le DS)

  • Vite / bundlers modernes
import '@tarik-leviathan/ltds/styles';

Tree-shaking par entrées ciblées

Vous pouvez importer uniquement une partie des styles :

  • Core (reset + tokens + colors)
import '@tarik-leviathan/ltds/styles/core';
  • Utilitaires (spacing, grids, flex, dimensions, utilities…)
import '@tarik-leviathan/ltds/styles/utils';
  • Atomes (ex: buttons)
import '@tarik-leviathan/ltds/styles/buttons';

Theming & couleurs

Le cœur des couleurs est piloté par les brand tokens. Pour surcharger globalement :

:root {
  --brand-primary: rgb(136, 91, 241);
  --brand-primary-hover: oklch(from var(--brand-primary) calc(l * .90) c h);
  --brand-primary-active: oklch(from var(--brand-primary) calc(l * .80) c h);
}

Schémas prêts à l’emploi via attribut :

<body data-scheme="1"> … </body> <!-- violet/plum -->
<body data-scheme="2"> … </body> <!-- bleu/azure -->

Typographie

LTDS expose des tokens de typo (familles, graisses, échelle). Les fichiers @font-face doivent être gérés par votre application (DS agnostique côté fonts).

Exemple d’override :


:root{
  --font-family-base: "Anton", system-ui, -apple-system, "Segoe UI", sans-serif;
  --font-family-accent: "Mona Sans", var(--font-family-base);
}

Breakpoints (max-width)

414px (small-mobile)

768px (mobile)

1024px (tablet)

1199px (notepad)

1439px (laptop)

1919px (desktop)

Versioning & publication

Le repo utilise Conventional Commits et un flux release + tag + publish automatisé via GitHub Actions.

  1. coder, committer
git add .
git commit -m "feat: nouvelle utilitaire responsive fs"
  1. release
npm run release
  1. push avec tags (déclenche le workflow lt-factory/.github/workflows/publish-on-tag.yml)
git push origin main --follow-tags

La CI (workflow publish-on-tag.yml) :

  • installe deps
  • build
  • npm publish --access public

⚠️ Prérequis : secret NPM_TOKEN (automation token npm) dans GitHub → Repo → Settings → Secrets and variables → Actions.

Convention commits

Conventions attendues par standard-version

  • fix: → pour une correction de bug (→ patch)
  • feat: → pour une nouvelle fonctionnalité (→ minor)
  • perf: → pour une amélioration de performance
  • docs: → uniquement pour la doc
  • style: → pour le style/formatage
  • refactor: → refacto sans changement de fonctionnalité
  • test: → ajout/modif de tests
  • chore: → tâches diverses, outils, CI, dépendances…

License

Licence MIT – © Tarik Louatah