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

fela-monolithic

v12.2.1

Published

Fela enhancer for having monolithic classnames

Downloads

27,948

Readme

fela-monolithic

Warning: This plugin is not meant to be used in production. We don't monitor its performance and also can't make sure that it works with every plugin. It was initially build for better developer experience, but since Chrome fixed the issue with debugging styles rendered with insertRule, we no longer need it for that regard. The only use case for which we actively recommend this plugin is snapshot testing.

The monolithic enhancer will use unique class names instead of atomic ones. These generated class names are not re-usable like the atomic design but allows you to debug and modify styles with ease. Every ruleset will have it's own unique class - this means that a new class will be generated if you are using props and they change. If you want to fix the class name, you can add property className into your rule set. This can be useful if you want to generate an external stylesheet that's human readable, re-usable and can be used on non-JS projects.

Installation

yarn add fela-monolithic

You may alternatively use npm i --save fela-monolithic.

Usage

import { createRenderer } from 'fela'
import monolithic from 'fela-monolithic'

const renderer = createRenderer({
  enhancers: [monolithic()],
})

const rule = () => ({
  className: 'custom',
  color: 'red',
})

renderer.renderRule(rule)

outputs

.custom {
  color: red;
}

if className property is not used, the output will be

.137u7ef {
  color: red;
}

137u7ef is a hash based on rule properties (color: red in this case).

Configuration

Options

|  Option | Value | Default | Description | | ----------------- | ----------- | ------- | ----------------------------------- | | prettySelectors | (boolean) | false | use pretty selectors in development |

If you are using prettySelectors with plain Fela rules it will add the rule.name to the className e.g.

Note: anonymous functions will still only use the hash!

import { createRenderer } from 'fela'
import monolithic from 'fela-monolithic'

const renderer = createRenderer({
  enhancers: [monolithic({ prettySelectors: true })],
})

const redText = () => ({
  color: 'red',
})

renderer.renderRule(redText) // => redText_137u7ef
.redText_137u7ef {
  color: red;
}

If you use it together with createComponent or connect from react-fela, preact-fela or inferno-fela, it will also add the component type or displayName to the rule. e.g.

import { createComponent } from 'react-fela'

const Button = () => ({
  color: 'red'
})

const Comp = createComponent(Button)

<Button />
// => <div class="Button_div__137u7ef"></div>

const ExtendedButton = () => ({
  backgroundColor: 'blue'
})

const Comp2 = createComponent(ExtendedButton, Button)

<Comp2 />
// => <div class="ExtendedButton_Button__xxxxx"></div>

License

Fela is licensed under the MIT License. Documentation is licensed under Creative Commons License. Created with ♥ by @robinweser and all the great contributors.