# Prefer `Reflect.apply()` over `Function#apply()`

💼 This rule is enabled in the following [configs](https://github.com/sindresorhus/eslint-plugin-unicorn#recommended-config): ✅ `recommended`, ☑️ `unopinionated`.

🔧 This rule is automatically fixable by the [`--fix` CLI option](https://eslint.org/docs/latest/user-guide/command-line-interface#--fix).

<!-- end auto-generated rule header -->
<!-- Do not manually modify this header. Run: `npm run fix:eslint-docs` -->

[`Reflect.apply()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Reflect/apply) is arguably less verbose and easier to understand. In addition, when you accept arbitrary methods, it's not safe to assume `.apply()` exists or is not overridden.

## Examples

```js
function foo() {}

// ❌
foo.apply(null, [42]);

// ❌
Function.prototype.apply.call(foo, null, [42]);

// ✅
Reflect.apply(foo, null, [42]);
```

```js
function foo() {}

// ❌
foo.apply(this, [42]);

// ❌
Function.prototype.apply.call(foo, this, [42]);

// ✅
Reflect.apply(foo, this, [42]);
```

```js
function foo() {}

// ❌
foo.apply(null, arguments);

// ❌
Function.prototype.apply.call(foo, null, arguments);

// ✅
Reflect.apply(foo, null, arguments);
```

```js
function foo() {}

// ❌
foo.apply(this, arguments);

// ❌
Function.prototype.apply.call(foo, this, arguments);

// ✅
Reflect.apply(foo, this, arguments);
```