Skip to main content


Enforce unbound methods are called with their expected scope.


This rule requires type information to run.

Class method functions don't preserve the class scope when passed as standalone variables ("unbound"). If your function does not access this, you can annotate it with this: void, or consider using an arrow function instead. Otherwise, passing class methods around as values can remove type safety by failing to capture this.

This rule reports when a class method is referenced in an unbound manner.


If you're working with jest, you can use eslint-plugin-jest's version of this rule to lint your test files, which knows when it's ok to pass an unbound method to expect calls.

module.exports = {
"rules": {
"@typescript-eslint/unbound-method": "error"

Try this rule in the playground ↗


class MyClass {
public log(): void {

const instance = new MyClass();

// This logs the global scope (`window`/`global`), not the class instance
const myLog = instance.log;

// This log might later be called with an incorrect scope
const { log } = instance;

// arith.double may refer to `this` internally
const arith = {
double(x: number): number {
return x * 2;
const { double } = arith;
Open in Playground


This rule accepts the following options:

type Options = [
/** Whether to skip checking whether `static` methods are correctly bound. */
ignoreStatic?: boolean;

const defaultOptions: Options = [{ ignoreStatic: false }];


Examples of correct code for this rule with { ignoreStatic: true }:

class OtherClass {
static log() {

// With `ignoreStatic`, statics are assumed to not rely on a particular scope
const { log } = OtherClass;

Open in Playground

When Not To Use It

If your project dynamically changes this scopes around in a way TypeScript has difficulties modeling, this rule may not be viable to use. One likely difficult pattern is if your code intentionally waits to bind methods after use, such as by passing a scope: this along with the method. You might consider using ESLint disable comments for those specific situations instead of completely disabling this rule.

If you're wanting to use toBeCalled and similar matches in jest tests, you can disable this rule for your test files in favor of eslint-plugin-jest's version of this rule.

Type checked lint rules are more powerful than traditional lint rules, but also require configuring type checked linting. See Performance Troubleshooting if you experience performance degredations after enabling type checked rules.