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

@bluebie/style-object

v1.0.1

Published

A simple way to make inline styles as objects, with optional render functions, for use with nanohtml/lit-html style of widget rendering

Downloads

2

Readme

style-object

A simple way to make inline styles as objects, with optional render functions, for use with nanohtml/lit-html style of widget rendering. It can be useful when working with nanocomponent or lit-html/nanohtml html rendering workflows, to generate stringified css inline styles.

a StyleObject works pretty much like a regular javascript object, with a few differences:

  • When .toString() is called, it returns a nicely formatted css inline styles string, suitable for use in a DOM style attribute.
  • camelCasePropertyNames are stringified in-hyphenated-lowercase
  • when values are functions, the function is called every time toString() is called, and it's return value is used when building the string
  • a .setVariables() method makes it easier to add custom variables (prefixing property names with --)
  • a .set() method makes it easy to bulk override several properties in the object

This can be useful when using nanocomponent, as you can tie css property values to object instance properties and other dynamic data in the object's constructor, and you can expose a .style property allowing users to manipulate the styles of the widget similar to a DOM element, and you can avoid messy inline style building template code in your createElement / rendering functions.

Example usage with NanoComponent:

const Nanocomponent = require('nanocomponent')
const html = require('nanohtml')

class ButtonWidget extends Nanocomponent {
  constructor ({ label = 'Button', onClick = () => {}, fontSize = '12pt', hue = 0 }) {
    super()
    this.label = label
    this.onClick = onClick
    this.fontSize = '12pt'
    this.hue = hue
    this.style = new StyleObject({
      fontSize: () => this.fontSize,
      backgroundColor: () => `hsl(${this.hue}deg, 30%, 90%)`,
      color: () => `hsl(${this.hue}deg, 80%, 10%)`,
      border: () => `hsl(${this.hue}deg, 50%, 20%)`
    })
  }
  
  createElement () {
    let click = (event) => this.onClick(event)
    return html`<button style="${this.style}" onclick=${click}>${this.label}</button>`
  }
  
  update () {
    return true
  }
}

module.exports = ButtonWidget 

In the above example, a simple button can be configured with .style similar to a DOM element, except that calling .render() after is required to make the changes take effect. Code stays pretty clean, and properties on the object can be used to generate complex styles programatically, like the hue option above.