no-unused-expressions: support allowTaggedTemplates option

[jasonkuhrt]

Summary

The no-unused-expressions rule currently flags tagged template literals as unused expressions, even when they're used for side effects. ESLint's equivalent rule supports an allowTaggedTemplates option to handle this pattern. Would oxlint consider adding this option?

Use Case

Tagged template literals are commonly used as a fluent API for building strings with side effects:

import { Str } from '@kitz/core'

const b = Str.Builder.make()

b`First line`
b`Second line`
b`Value: ${someValue}`

const result = b.toString()

This pattern appears in:

• String builders (like the example above)
• Logging libraries (e.g., logTagged template message``)
• SQL query builders
• Styled-components and CSS-in-JS libraries
• Test assertion libraries

Current Behavior

oxlint reports:

Expected expression to be used
help: Consider using this expression or removing it (eslint(no-unused-expressions))

Requested Behavior

Add an allowTaggedTemplates option (matching ESLint's API) that permits tagged template expressions as statements:

{
  "rules": {
    "eslint/no-unused-expressions": ["error", { "allowTaggedTemplates": true }]
  }
}

ESLint Reference

ESLint's no-unused-expressions rule supports this option:

• ESLint docs: no-unused-expressions

allowTaggedTemplates set to true will allow you to use tagged template literals in your code.

Workaround

Currently disabling the rule entirely:

{
  "rules": {
    "eslint/no-unused-expressions": "off"
  }
}

This loses the benefit of catching actual unused expressions elsewhere in the codebase.

---

Environment: oxlint 1.34.0

[connorshea]

It already supports this option: https://oxc.rs/docs/guide/usage/linter/rules/eslint/no-unused-expressions.html#allowtaggedtemplates

Are there bugs with this rule when you have that option set to true?

[jasonkuhrt]

Ty! My bad just didn't catch that option, all good now!