tsconfig - Ignore errors by ids
  • 11-Jun-2023
Author Roni Kriger
tsconfig - Ignore errors by ids

tsconfig – Ignore errors by ids

Roni Kriger

Explanation of the problem

In TypeScript, there is a proposal to introduce the ability to declare which error IDs should be ignored. Currently, all errors in TypeScript are optional, meaning they can be addressed or ignored based on developer preference. However, it would be beneficial to have a mechanism to explicitly specify the error IDs that should be ignored. This feature could be configured in the tsconfig.json file by adding an “ignoreErrors” property under “compilerOptions” and providing an array of error IDs to be ignored.

      "ignoreErrors":[2403, 2686, ...]

By including specific error IDs in the “ignoreErrors” array, developers can indicate which errors they want to suppress. This is particularly useful for errors that are considered more of a code style suggestion rather than actual type errors. These errors, such as the one stating “‘L’ refers to a UMD global, but the current file is a module. Consider adding an import instead,” are subjective in nature and can be deemed as minor nuisances. Ignoring these specific error IDs helps to prevent them from cluttering the error log and provides a cleaner development experience.

With the ability to define ignored error IDs, developers can have more control over the error reporting in their TypeScript projects. By selectively ignoring certain error IDs that are perceived as non-critical or irrelevant to their codebase, developers can focus on addressing more significant issues while minimizing distractions caused by subjective or less impactful error messages. This feature enhances the flexibility and customizability of TypeScript’s error handling, allowing developers to tailor the error reporting system to suit their preferences and coding style.


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 tsconfig – Ignore errors by ids

In response to the request for the ability to declare which error IDs to ignore in TypeScript, there are a couple of suggested approaches. One proposal is to have a functionality similar to the “-nowarn” option in C#, which allows developers to specify specific error codes to be ignored. This would provide a more granular control over which errors are suppressed. Another suggestion is to use a tool called “tsc-silent,” which can be installed as a replacement for the TypeScript compiler (tsc). This tool offers the capability to define paths where certain errors should be ignored. By configuring the paths and associated error codes, developers can selectively suppress specific errors based on their project’s needs.

tsc-silent -p tsconfig.json --suppress 7017@src/js/ 2322,2339,2344@/src/legacy/

By specifying the “–suppress” flag followed by the error codes and their corresponding paths, developers can instruct tsc-silent to ignore those specific errors within the defined locations. This approach provides a practical solution for controlling error reporting on a more fine-grained level, allowing developers to focus on relevant issues and reduce noise in the error log.

Overall, while TypeScript currently does not natively support declaring ignored error IDs, the suggested approaches offer viable alternatives to achieve this functionality. Whether through enhanced compiler options or the use of third-party tools like tsc-silent, developers have options to selectively ignore specific error codes, resulting in a more streamlined and manageable error reporting experience tailored to their project requirements.


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) {
        this.name = name;
        this.email = email;

const user = new User("John Doe", "johndoe@example.com");
  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. It’s a registration form away.

Get Lightrun

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.