This seems like a nice linting rule, however, it is also good practice to split the styles in a separate file. In this case the rule warns that all classes are unused. Is it possible to adjust this rule so that it also works if the styles are defined in a separate file?

Related to the same question at jens-ox#3

I get this error every time I do yarn build. When I run yarn start, the first time there is an error, the next time everything is ok

• package.json

{
  "devDependencies": {
    "eslint": "7.32.0",
    "eslint-plugin-tss-unused-classes": "0.0.4"
  }
}

• eslint.json

{
  "extends": ["custom-plugin"],
  "plugins": ["tss-unused-classes"],
  "settings": {
    "react": {
      "version": "17.0.2"
    }
  },
  "rules": {
    "no-param-reassign": ["error", { "props": false }],
    "react-hooks/exhaustive-deps": "off",
    "no-console": "warn",
    "@typescript-eslint/no-unused-vars": [
      "error",
      { "varsIgnorePattern": "React" }
    ],

    "tss-unused-classes/unused-classes": 2
  },
}

It's working fine for me with eslint v8, but I'm getting a peer dependency warning. Can you update supported version to include v8?

Background

Our team has just migrated to MUI5 and chosen to use tss-react/mui because the migration was much simpler coming from MUI4. A lot of our MUI 4 based code looked like this:

const { root, label } = useStyles({});

To make the migration simpler and avoid having to re-write many extra lines of code, we simply destructured the classes from tss-react/mui's makeStyles, like so:

const { classes: { root, label } } = useStyles();

Issue

This plugin only seems to work when using classes.classname directly.

Using destructuring:

results in a false positive:

But everything works fine if we use classes.root. Is it possible to make this plugin work with destructuring? Our team would love to use it, but currently it's not feasible due to the large number of lines we'd need to re-write.

Thanks for all your hard work, we're really enjoying tss-react/mui!