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

@stylexjs/eslint-plugin

v0.17.2

Published

StyleX eslint plugin.

Readme

@stylexjs/eslint-plugin

The ESLint rule is a standalone ESLint plugin that mostly maintains an allowlist for valid styles and their valid values.

Installation

npm install --save-dev @stylexjs/eslint-plugin

Enable Flow Types

If you need to import this package in an environment where you need the Flow type definitions shipped with this package to work, please add the following options to your .flowconfig file:

module.system.node.resolve_dirname=flow_modules
module.system.node.resolve_dirname=node_modules

This will fix the missing types for eslint and estree.

Enabling the plugin and rules

Once you've installed the npm package you can enable the plugin and rules by opening your ESLint configuration file and adding the plugin and rules.

{
  "rules": {
    "@stylexjs/valid-styles": "error",
    "@stylexjs/sort-keys": "warn"
  },
  "plugins": ["@stylexjs"]
}

All the rules

@stylexjs/valid-styles

StyleX requires styles that are statically analyzable. This rule will detect invalid styles that StyleX cannot handle and provides basic type checking for style values.

Disallowed CSS properties and suggested fixes

Listed are common CSS properties that are not allowed in StyleX, along with their suggested replacements.

@stylexjs/sort-keys

This rule helps to sort the StyleX property keys according to property priorities.

Config options

{
  "validImports": ["stylex", "@stylexjs/stylex"]
}

@stylexjs/valid-shorthands

This ESLint rule enforces the use of individual longhand CSS properties in place of multivalue shorthands when using create for reasons of consistency and performance. The rule provides an autofix to replace the shorthand with the equivalent longhand properties.

Disallowed: margin, padding with multiple values

Using multivalue shorthands that StyleX cannot safely split into equivalent longhands:

  • margin: '8px 16px'
  • padding: '8px 16px 8px 16px'

Fix: Replace with equivalent longhands. Note: this is autofixable.

Disallowed: font

Why: font is a shorthand that overrides multiple font settings at once.

Fix: Replace with individual font properties. Note: this is autofixable.

  • fontSize
  • fontFamily
  • fontStyle
  • fontWeight
Disallowed: border, borderTop, borderRight, borderBottom, borderLeft

Fix: Replace with individual sub-properties. Note: this is autofixable.

  • borderWidth
  • borderStyle
  • borderColor

Config options

This rule has a few custom config options that can be set.

{
  allowImportant: false,                       // Whether `!important` is allowed
  preferInline: false,                         // Whether the expansion uses logical direction properties over physical
  validImports: ['stylex', '@stylexjs/stylex']
}

@stylexjs/enforce-extension

This rule ensures consistent naming for StyleX theme files that export variables using defineVars or defineConsts.

Not allowed

  • Exporting defineVars or defineConsts in a file not ending in .stylex.js or .stylex.ts
  • Using the .stylex.js / .stylex.ts extension without exporting defineVars or defineConsts
  • Mixing defineVars or defineConsts with other exports in the same file (unless legacyAllowMixedExports is enabled)
  • Mixing defineConsts with defineVars when enforceDefineConstsExtension is enabled

Instead...

  • Use .stylex.js or .stylex.ts for files that only export defineVars or defineConsts
  • Export only theme vars/consts from these files
  • When enforceDefineConstsExtension is enabled, use .stylex.const.js for defineConsts exports

Config options

{
  "themeFileExtension": ".stylex", // default, can be customized
  "legacyAllowMixedExports": false, // allow mixed exports (legacy support)
  "enforceDefineConstsExtension": false, // enforce separate .const suffix for defineConsts
  "validImports": ["stylex", "@stylexjs/stylex"]
}

@stylexjs/no-unused

This rule flags unused styles created with create(...). If a style key is defined but never used, the rule auto-strips them from the create call.

Config options

{
  "validImports": ["stylex", "@stylexjs/stylex"]
}

@stylexjs/no-legacy-contextual-styles

This rule flags usages of the original media query/pseudo class syntax that wraps multiple property values within a single @-rule or pseudo class like this:

Config options

{
  "validImports": ["stylex", "@stylexjs/stylex"]
}
const styles = stylex.create({
  root: {
    width: '100%',
    '@media (min-width: 600px)': {
      width: '50%',
    },
  },
});

This syntax is deprecated and should be replaced with the new syntax specified here

const styles = stylex.create({
  root: {
    width: {
      default: '100%',
      '@media (min-width: 600px)': '50%',
    },
  },
});

@stylexjs/no-lookahead-selectors

This rule warns against usage of stylex.when.anySibling, stylex.when.descendant, and stylex.when.siblingAfter due to their reliance on the CSS :has() selector, which does not yet have widespread browser support.

Limited browser support

const styles = stylex.create({
  foo: {
    backgroundColor: {
      default: 'blue',
      [stylex.when.anySibling('.sibling')]: 'red',
    },
    color: {
      default: 'black',
      [stylex.when.descendant('.child')]: 'purple',
    },
    marginTop: {
      default: '0px',
      [stylex.when.siblingAfter('.next')]: '8px',
    },
  },
});

See caniuse.com/css-has for current browser compatibility.

Config options

{
  "validImports": ["stylex", "@stylexjs/stylex"]
}

@stylexjs/no-nonstandard-styles

This rule enforces that you create standard CSS values and properties for StyleX. It validates that all CSS properties and values conform to standard CSS specifications.

Features

  • Detects invalid CSS property names and suggests standard alternatives
  • Validates CSS values against property specifications
  • Provides auto-fixes for common issues (e.g., non-standard float: startfloat: inline-start)
  • Supports StyleX-specific functions like stylex.keyframes() and stylex.defineVars()

Config options

{
  "validImports": ["stylex", "@stylexjs/stylex"]
}