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

radium-plugin-linter

v1.0.1

Published

Radium plugin that lints your styles

Downloads

2

Readme

radium-plugin-linter

npm install radium-plugin-linter --save

Radium plugin that uses uses inline-style-linter for runtime style linting. It is a modular & plugin-based and brings a lot of configuration options.

You must pass a configuration object using the linter key within your Radium configuration. Check Linter Configuration for detailed information on how to configure the Linter.

Usage

NOTE: This usage guide was directly copied from one of Ian Obermiller (Radium maintainer)'s Radium Plugins.

radium-plugin-linter should be added before style prefixing (at least if you want to use the noVendorPrefix-plugin shipped with with linter). Radium plugins are setup by passing a config object to @Radium. Since you'll d probably want to use this plugin everywhere you use Radium, you can create your own module with a configured version of Radium:

ConfiguredRadium.js

import { Plugins } from 'inline-style-linter'

var Radium = require('radium');
var lintStyles = require('radium-plugin-linter');

function ConfiguredRadium(component) {
  return Radium({
    plugins: [
      Radium.Plugins.mergeStyleArray,
      Radium.Plugins.checkProps,
      Radium.Plugins.resolveMediaQueries,
      Radium.Plugins.resolveInteractionStyles,

			lintStyles,

      Radium.Plugins.prefix,
      Radium.Plugins.checkProps
    ],
    // linter configuration
    linter: {
      plugins: [
        Plugins.preferNumber,
        Plugins.shorthandLonghand,
        Plugins.noInitialValue
      ]
    }
  })(component);
}

module.exports = ConfiguredRadium;

Then you just use @ConfiguredRadium instead of @Radium. Or ConfiguredRadium(MyComponent) instead of Radium(MyComponent).

@ConfiguredRadium
class MyComponent extends Component {
  // ...
}