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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@openlab/alembic

v0.3.3

Published

A Design System for Open Lab research projects.

Downloads

73

Readme

⚗️ Alembic

A Design System for Open Lab research projects.

Go to the docs →

Release process

  1. Run the build
  2. Update API docs if needed
  3. Run npm version minor|major|patch
  4. Run npm publish

Uses

This library is used by several Open Lab projects:

Design

Goals

  1. Provide a step up (design-wise) for developers
  2. Reduce duplication in effort/code/work
  3. Improve collaboration on projects and focus evolution in the same direction

What

  • A library of components and patterns
  • A documentation site to describe the design system

To explore

  • More accessibility concerns
  • Document the reason behind decisions / solutions
  • Think about adaptability, evolution and collaboration

Coding conventions

TODO: find a better place for these

css variables

  • "axioms" are single words like --measure
  • everything else is type-prefixed like --color-background or --border-thin

imports

module.js is the main entrypoint, sub-modules are self-named files in their own folder e.g. lib/lib.js or layouts/layouts.js.

misc

  • group source by the module, js + css alongside eachother is fine. It makes it easy to work on a module.
  • avoid JavaScript's default exports
  • sub-modules should explicitly export things, avoid export * from '...'-type code
  • pure functions where possible
  • exported code prefixed with _ (an underscore) is internal, should not be used and may change between major releases

This project was set up by puggle