no-keyword-prefix

March 27, 2026 ยท View on GitHub

๐Ÿ“ Disallow identifiers starting with new or class.

๐Ÿšซ This rule is disabled in the following configs: โœ… recommended, โ˜‘๏ธ unopinionated.

new Foo and newFoo look very similar. Use alternatives that do not look like keyword usage.

Examples

// โŒ
const newFoo = 'foo';

// โŒ
const classFoo = 'foo';

// โœ…
const foo = 'foo';

// โœ…
const _newFoo = 'foo';

// โœ…
const new_foo = 'foo';

// โœ…
const fooNew = 'foo';

Options

disallowedPrefixes

If you want a custom list of disallowed prefixes you can set them with disallowedPrefixes:

/* eslint unicorn/no-keyword-prefix: ["error", {"disallowedPrefixes": ["new", "for"]}] */
// โœ…
const classFoo = "a";

// โŒ
const forFoo = "a";

The default is ["new", "class"].

checkProperties

If you want to disable this rule for properties, set checkProperties to false:

/* eslint unicorn/no-keyword-prefix: ["error", {"checkProperties": true}] */
// โŒ
foo.newFoo = 2;
/* eslint unicorn/no-keyword-prefix: ["error", {"checkProperties": false}] */
// โœ…
var foo = {newFoo: 1}; // pass

// โœ…
foo.newFoo = 2; // pass

onlyCamelCase

The default behavior is to check for camel case usage. If you want to disallow the prefix entirely, set onlyCamelCase to false:

/* eslint unicorn/no-keyword-prefix: ["error", {"onlyCamelCase": true}] */
// โœ…
const new_foo = "foo";
/* eslint unicorn/no-keyword-prefix: ["error", {"onlyCamelCase": false}] */
// โŒ
const new_foo = "foo";