• 11-Jun-2023
Lightrun Team
Author Lightrun Team

Error “‘this’ implicitly has type ‘any'” when used .bind()

Lightrun Team
Lightrun Team

Explanation of the problem

The issue revolves around a TypeScript project with a specific configuration defined in the tsconfig.json file. The configuration includes options such as allowJs, checkJs, noEmit, and strict set to true. Additionally, the project has two files, index.d.ts and index.js. The index.js file contains JavaScript code with a comment specifying the type of the variable o as MyObj. Within the code, there is a nested function where the context (this) is accessed, but an unexpected error occurs at that line.

The provided index.js file defines an object o with a foo function. Inside foo, there is a nested function, and within that function, the this context is accessed using .bind(this). However, TypeScript raises an error at the line where the this context is referenced, stating that this implicitly has type any due to the lack of a type annotation.

The expected behavior is for there to be no error, as the this context is explicitly specified using .bind(). The intention is to ensure that the context passed to the nested function retains its value. However, the actual behavior is that TypeScript reports an error, indicating that this is implicitly of type any and lacks a proper type annotation.

This issue highlights a discrepancy between the expected and actual behavior regarding the this context in TypeScript. The code explicitly sets the this context using .bind(this), but TypeScript still treats it as implicitly of type any. Resolving this issue would involve examining the TypeScript configuration and code to determine the cause of the unexpected error and finding a solution to ensure that the this context is properly recognized and annotated in TypeScript.

Troubleshooting with the Lightrun Developer Observability Platform

Getting a sense of what’s actually happening inside a live application is a frustrating experience, one that relies mostly on querying and observing whatever logs were written during development.
Lightrun is a Developer Observability Platform, allowing developers to add telemetry to live applications in real-time, on-demand, and right from the IDE.

  • Instantly add logs to, set metrics in, and take snapshots of live applications
  • Insights delivered straight to your IDE or CLI
  • Works where you do: dev, QA, staging, CI/CD, and production

Start for free today

Problem solution for Error “‘this’ implicitly has type ‘any'” when used .bind()

In response to the issue described, two potential solutions have been suggested by the community. The first suggestion involves setting the noImplicitThis option to false in the tsconfig.json file. By disabling this option, TypeScript will no longer raise an error for expressions involving this with an implied any type. This approach has been tested and appears to work successfully.

Another workaround proposed is to use the const that = this; pattern instead of relying on arrow functions or the .bind() method. By assigning this to a constant variable (that in this case), the intended this context can be preserved within nested functions. This workaround can be useful if the runtime environment does not fully support arrow functions or if the issue persists despite other configurations.

Both suggestions aim to address the unexpected error related to the this context in TypeScript. The first solution involves adjusting the TypeScript configuration by disabling the noImplicitThis option, while the second workaround provides an alternative coding pattern using a constant variable to capture the desired this context. Depending on the specific needs and constraints of the project, either of these approaches can be considered for resolving the issue.

Other popular problems with Microsoft TypeScript

Problem: Incorrect Use of TypeScript Interfaces

TypeScript interfaces are a powerful tool for enforcing strict type checking in a codebase. However, incorrect use of interfaces can lead to problems with code accuracy and maintainability. For example, if an interface is defined with properties that are not used elsewhere in the code, it can be difficult to track down the source of an error later on.


To avoid this problem, it is recommended to make use of strict null checking and optional properties in interfaces. Additionally, be mindful of the properties and methods defined in an interface, and make sure that they are actually used elsewhere in the code. If an interface is no longer needed, it should be removed to prevent confusion and errors.

Problem: TypeScript Compilation Errors

TypeScript is a statically-typed language, which means that all type information is known at compile time. This can lead to compilation errors when code is written that violates TypeScript’s type system. For example, if a variable is declared with a type of string, and an attempt is made to assign a value of type number to it, a compile-time error will occur.


To resolve TypeScript compilation errors, it is important to carefully review the code and make sure that all variables are correctly declared with the correct type. In cases where a variable needs to be used with different types, a union type can be used to specify multiple types for the same variable. Additionally, the TypeScript documentation provides detailed information about the type system, and can be a valuable resource for resolving compilation errors.

Problem: Managing TypeScript Dependencies

Managing dependencies in a TypeScript project can be challenging, as different libraries and packages may have different versions and compatibility requirements. This can lead to conflicts and errors when attempting to use multiple libraries that have incompatible dependencies.


To resolve dependency management issues in a TypeScript project, it is recommended to make use of a package manager such as npm or yarn. These tools provide automated dependency management, and can help to prevent conflicts and errors when using multiple libraries and packages. Additionally, it is important to keep dependencies up-to-date, as newer versions may resolve compatibility issues and improve the overall stability of the project.

A brief introduction to Microsoft TypeScript

Microsoft TypeScript is a statically-typed, open-source programming language that builds on JavaScript. It is designed to provide optional type safety, improved tooling, and enhanced scalability to JavaScript code. TypeScript offers a language structure that is familiar to JavaScript developers, but with the added benefits of static type checking and enhanced tooling support.

TypeScript is designed to be compatible with existing JavaScript code and integrates seamlessly into many popular development environments and build tools. The language offers features such as class and interface definitions, type inference, and advanced type checking, making it easier for developers to write robust, maintainable code. TypeScript also includes a transpiler that can convert TypeScript code into equivalent JavaScript code, allowing developers to write TypeScript code that can run in any environment that supports JavaScript.

Most popular use cases for Microsoft TypeScript

  1. Large-scale web application development: TypeScript is well-suited for developing large-scale web applications, as it provides developers with the ability to write scalable, maintainable code. With its optional type checking, developers can catch type-related errors at compile time, making it easier to catch bugs and reduce the time spent debugging code. Additionally, TypeScript’s compatibility with existing JavaScript code allows developers to gradually adopt the language in their existing codebases, making it easier to transition to a statically-typed codebase.
class User {
    name: string;
    email: string;

    constructor(name: string, email: string) { = name; = email;

const user = new User("John Doe", "");
  1. Improved tooling support: TypeScript integrates well with modern development environments and build tools, making it easier for developers to write, manage, and maintain code. With TypeScript’s enhanced tooling support, developers can benefit from features such as code completion, refactoring, and debugging, which can help to increase developer productivity and reduce the time spent on manual code management tasks.
  2. Interoperability with JavaScript libraries: TypeScript is designed to be compatible with existing JavaScript code, making it easy for developers to integrate TypeScript with existing JavaScript libraries and codebases. Additionally, TypeScript provides a way to define type information for JavaScript libraries, making it easier to write TypeScript code that interacts with existing JavaScript libraries in a type-safe manner. This can help to reduce the time spent debugging and improve the overall stability of code.

It’s Really not that Complicated.

You can actually understand what’s going on inside your live applications.

Try Lightrun’s Playground

Lets Talk!

Looking for more information about Lightrun and debugging?
We’d love to hear from you!
Drop us a line and we’ll get back to you shortly.

By submitting this form, I agree to Lightrun’s Privacy Policy and Terms of Use.