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 🙏

© 2025 – Pkg Stats / Ryan Hefner

eslint-plugin-tailwind-rules

v1.0.0

Published

ESLint rule to prevent using px-based font sizes in Tailwind CSS.

Readme

eslint-plugin-tailwind-rules

🚫 ESLint plugin to prevent using px font sizes in Tailwind CSS. Use rem or em instead for better accessibility and responsiveness.

Installation

To install the plugin, run the following command:

npm install --save-dev eslint-plugin-tailwind-rules

Configuration

Once installed, you need to add the plugin to your ESLint configuration.

  1. In .eslintrc.js (or your preferred ESLint config file, such as .eslintrc.json or eslint.config.js):
module.exports = {
  plugins: ["tailwind-rules"], // Add the plugin
  rules: {
    "tailwind-rules/no-px-font-size": "warn", // Enable the rule
  },
};
  1. In .eslintrc.json:
{
  "plugins": ["tailwind-rules"],
  "rules": {
    "tailwind-rules/no-px-font-size": "warn"
  }
}

Rule Options

  • "tailwind-rules/no-px-font-size": "warn": This will trigger a warning when px units are used in Tailwind class names.
  • "tailwind-rules/no-px-font-size": "error": This will trigger an error when px units are used in Tailwind class names.
  • "tailwind-rules/no-px-font-size": "off": This will disable the rule.

Example

✅ Correct Usage (using rem or em):

<p class="text-[1rem]">This is correct ✅</p>
<p class="text-[1.2rem]">Another correct example ✅</p>

❌ Incorrect Usage (using px):

<p class="text-[16px]">This is incorrect ❌</p>
<p class="text-[14px]">Another incorrect example ❌</p>

Why use this plugin?

  • Accessibility: rem (relative to root font size) ensures better scaling for accessibility, as it adapts to the user's settings.
  • Responsiveness: Using relative units like rem and em makes the layout more flexible and adaptive to different screen sizes and user preferences.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Contributing

Contributions are welcome! If you find a bug or want to suggest a feature, feel free to open an issue or submit a pull request.

Links