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

@barelyhuman/style-builder

v0.0.5

Published

I built it while trying to focus on building one of my web apps, safe to say, I couldn't focus.

Downloads

7

Readme

style-builder

I built it while trying to focus on building one of my web apps, safe to say, I couldn't focus.

Anyway, the library is simpler builder chain for styles.

Highlights

Usage

  • Start by installing the library itself, the library could be both a devDependency or a dependency based on how you use it.
  • If you generate the CSS on build time (Meta-frameworks), add it as a devDependency, if you are using it with a frontend library and appending the styles to the head element on client render, add it as a dependency.
npm i @barelyhuman/style-builder
# or
npm i @barelyhuman/style-builder -D
  • Next, lets set it up to use a element constructor, example preact.h, and define some styles.
import { h } from "preact";
import { extractStyles, setup, styled } from "@barelyhuman/style-builder";

setup(h);

const StyledLink = styled("a")
  .base`
    padding: 8px 16px;
    text-decoration: none;
    color: ${(props) => props.color || "dodgerblue"}
  `
  .hover`
    text-decoration: underline;
  `
  .variant(".mini")`
    padding: 2px 4px;
  `
  .component;

const styles = extractStyles();

console.log(styles);
// you might want to append the styles to the <head> element or extract and create a .css file out of it. I leave that to you.

Extending

Extending capabilities is pretty easy, you just use the variant function to define new classes, pseudo states (Hover, focus). The value of variant is appended directly to the css class, so you can pretty much write generic CSS with it.

const LastChildStyle = styled("a")
  .base`
    background-color: black;
  `
  .variant(":not:last-child")`
    background-color: red;
  `;

Missing Features

Because it was created just to test an idea, there's quite a few things missing, here's the list. If it's checked, it means the support was added in a specific version (version specified beside it)

  • [ ] Forwarding Refs (UI Libraries support)
  • [ ] Internal wrapper for document.createElement
  • [ ] Inheriting from existing styled element
  • [ ] Better way to share memory data when working with CJS (Unchunkable situations)
  • Raise an issue if there's other things you wished it did

License

MIT