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

@lttr/puleo

v0.2.1

Published

An attempt to build a mid-level CSS library forming a good starting point for custom designs. Opinionated on demand.

Downloads

170

Readme

Puleo CSS

An attempt to build a mid-level CSS library forming a good starting point for custom designs. Opinionated on demand.

Basic ideas

  • Should work in 3 ways
    • Import a CSS file and start prototyping
    • Configure with a set of design tokens
    • Create you own composition from individual building blocks
  • Build on top of ideas, that are already out there
  • CSS is good enough
    • No need for alternative techniques like utility class framework, CSS in JS etc.
    • No need for a pre-processor
    • Transpilation of newer CSS features allows to use standard CSS from the future
  • Scoping on components level is good
    • Ment to be used with CSS, that is scoped to components (like Vue or Svelte scoped style blocks or upcoming CSS native scoping; BEM does the job as well but it is not preffered)
  • Base styling layer needs (with ITCSS layer associations)
    • set of primitive values (physical variables/props) (-> Settings)
    • set of semantic variables/design tokens (-> Settings)
    • type, space and grid system (-> Tools)
    • CSS reset/normalization (-> Generic)
    • brand specific reset (-> Generic)
    • improved HTML elements (-> Elements)
    • utility classes for a couple of text styles (-> Objects)
    • utility classes for often used layouts (-> Objects)
    • individual component styles (-> Components)
    • utility classes for other aspects (like .visually-hidden) (-> Utilities)