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 🙏

© 2026 – Pkg Stats / Ryan Hefner

eslint-plugin-tailwind-enforcer

v1.0.1

Published

ESLint rules to enforce TailWind's className usage over traditional styling methods.

Downloads

107

Readme

eslint-plugin-tailwind-enforcer

ESLint rules to enforce the use of TailWind's className prop for styling in React projects, discouraging the use of StyleSheet.create() and inline style props.

🚀 Installation

First, install the plugin from npm:

npm install --save-dev eslint-plugin-tailwind-enforcer
# or
yarn add --dev eslint-plugin-tailwind-enforcer

⚙️ Usage

Add tailwind-enforcer to the plugins section of your .eslintrc.js configuration file.

You can use the recommended configuration which enables the rule with a warn level:

// .eslintrc.js
module.exports = {
  // ... your existing config
  plugins: [
    // ... other plugins
    "tailwind-enforcer", // Add the plugin here
  ],
  extends: [
    // ... other extends
    "plugin:tailwind-enforcer/recommended", // Use the recommended config
  ],
  rules: {
    // You can override the severity here if needed
    "tailwind-enforcer/no-react-styles": "error", // Example: make it an error instead of a warning
  },
  // ...
};

Or, enable the rule manually:

// .eslintrc.js
module.exports = {
  // ... your existing config
  plugins: [
    // ... other plugins
    "tailwind-enforcer", // Add the plugin here
  ],
  rules: {
    "tailwind-enforcer/no-react-styles": "warn",
    // Or "error", depending on your preference
  },
  // ...
};

📝 Rules

no-react-styles Disallows StyleSheet.create() and the style prop on JSX elements.

Message ID for StyleSheet.create(): noStyleSheetCreate Message ID for style prop: noStyleProp

Incorrect example on ReactNative (using StyleSheet):

import { View, Text, StyleSheet } from 'react-native';

const styles = StyleSheet.create({
  container: { flex: 1 },
  text: { color: 'red' }
});

function MyComponent() {
  return (
    <View style={styles.container}>
      <Text style={{ fontSize: 16 }}>Hello</Text>
    </View>
  );
}

Correct example (using NativeWind):

import { View, Text } from 'react-native';

function MyComponent() {
  return (
    <View className="flex-1">
      <Text className="text-red-500 text-base">Hello</Text>
    </View>
  );
}

🤝 Contributing

Feel free to open issues or submit pull requests.