This is caused by the TailwindCSS linter misinterpreting your mixin as a call to the Tailwind theme() function. If you are using VS Code, this issue shows how you can disable the error by modifying your settings:

{
  "tailwindCSS.lint.invalidConfigPath": "ignore"
}