[eslint-plugin] Fix no-unused false positive for styles exported via export specifier

[trofim-samusev]

Fixes #1786

What changed / motivation ?

@stylexjs/no-unused reports every key of a stylex.create() object as unused when the
object is exported using the specifier form:

import * as stylex from '@stylexjs/stylex';

const styles = stylex.create({
  main: { color: 'red' },
  secondary: { color: 'blue' },
});

export { styles }; // => "Unused style detected: styles.main" (+ styles.secondary)

The rule already exempts export const styles = stylex.create({...}) and
export default styles, on the basis that an exported styles object may have its keys used
by another module. export { styles }; and export { styles as s }; are the same situation
but were not covered.

The rule is fixable: 'code', so eslint --fix acted on the false positive and deleted
the style keys from the source file, emptying the create() call in the example above to
stylex.create({\n});.

Cause: the ExportNamedDeclaration visitor only looked at node.declaration. For
export { styles }; that is null and the exported bindings live in node.specifiers[],
so the variable was never removed from stylexProperties and Program:exit reported all of
its keys.

The fix iterates node.specifiers and exempts each local name. Re-exports
(export { styles } from './other-styles') are skipped via the node.source == null guard,
because they export another module's binding and must not exempt a same-named local
variable.

Linked PR/Issues

Fixes # (issue)

Additional Context

Tests added to packages/@stylexjs/eslint-plugin/__tests__/stylex-no-unused-test.js:

• valid: export { styles };
• valid: export { styles as sharedStyles };
• valid: export { theme, styles }; (specifier list with an unrelated binding)
• valid: export { styles as default };
• invalid: export { styles } from './other-styles'; — still reports the locally unused key,
  covering the re-export guard

No documentation change: neither the plugin README nor the docs site describes the rule's
export handling.

Pre-flight checklist

• I have read the contributing guidelines Contribution Guidelines
• Performed a self-review of my code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
stylex	Skipped		Jul 30, 2026 3:13am

[henryqdineen]

This is an edge case but should we make sure there are no false positives for
export type { styles }; or export { type styles }; by checking the exportKind on the declaration and specifiers?

[trofim-samusev]

Added support for those cases. Can you please check again when you'll have some time?