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

@noodlestan/designer-decisions

v0.0.14

Published

A library for modeling design decisions and tokens.

Readme

Designer Decisions - Models

A library for modeling contextual design decisions and tokens.

How to use

📖 Documentation

This core library models contextual design decisions of different types (colors, spaces, typography, ...), providing an API to produce values (or tokens) based on parametric inputs.

Sample and Demo Data

These exported constants defines where to locate the sample and demo data collections.

DecisionSource(s) are a way to pass decision inputs by reference to decision validators and stores such as Store.

import {
  type BuilderOptions,
  createBuilderContext,
  formatDecisionStatus
  produceDecisions,
  buildStaticStore,
} from '@noodlestan/designer-functions';
import { DEMO_DATA } from '@noodlestan/designer-decisions';

const options: BuilderOptions = {
  decisions: [DEMO_DATA, './data'],
};
const context = createBuilderContext(options);
const build = buildStaticStore(context);
const store = await build();

const records = store.records();
const produced = produceDecisions(context, store);
produced.decisions().forEach(status => console.info(formatDecisionStatus(status)));

console.info('🐘', produced.summary());

See also

Development

Make sure you README first.

Dependencies

This library depends only on chroma-js.

Build Targets

[!IMPORTANT] Do not add type: module or exports fields to package.json as this will break Node.js ESM consumers.

This library is packaged for use both in bundlers such as Vite and Astro, as well as Node.js environments (CJS/ESM), and ts-node. For Node.js consumers, even those using import or await import() syntaxes, all imports resolve to the CJS build. This is only possible when the "type": "module" and "exports" fields are both omitted from the library's package.json.

| Consumer | Syntax | Resolves to | | ------------------- | ------------- | ---------------------------------------- | | Bundlers | ESM import | module → TS entry point src/index.ts | | node script.js | CJS require | main → CJS build dist/cjs/index.js | | node script.mjs | ESM import | main (ignores module) | | ts-node script.ts | ESM import | main (ignores module) |

Scripts

  • $ npm run dev - uses esbuild to watch and tsc to emit declarations on rebuild.
  • $ npm run build - uses tsc to build dist/cjs and dist/esm.
  • $ npm run test / npm run test:watch - uses vitest.
  • $ npm run lint / npm run lint:fix - uses @noodlestan/eslint-config.

Note: The dist/esm build guarantees that verbatimModuleSyntax is respected everywhere.

MIT License

Copyright (c) 2024 Noodlestan.

Published under a MIT license.