Skip to content
← Back to rules

unicorn/no-hex-escape Pedantic

🛠️ An auto-fix is available for this rule.

What it does ​

Enforces a convention of using Unicode escapes instead of hexadecimal escapes for consistency and clarity.

Why is this bad? ​

Using hexadecimal escapes can be less readable and harder to understand when compared to Unicode escapes.

Examples ​

Examples of incorrect code for this rule:

javascript
const foo = "\x1B";
const foo = `\x1B${bar}`;

Examples of correct code for this rule:

javascript
const foo = "\u001B";
const foo = `\u001B${bar}`;

How to use ​

To enable this rule using the config file or in the CLI, you can use:

json
{
  "rules": {
    "unicorn/no-hex-escape": "error"
  }
}
ts
import { defineConfig } from "oxlint";

export default defineConfig({
  rules: {
    "unicorn/no-hex-escape": "error",
  },
});
bash
oxlint --deny unicorn/no-hex-escape

Version ​

This rule was added in v0.0.18.

References ​