Upcoming changes in default TypeScript analysis

At Codeac, we aim to provide the most effective automated code review tools. To ensure our TypeScript analysis stays aligned with the evolving ecosystem, we are updating our default configuration.

Starting April 29th, Codeac will switch the default linter for TypeScript from TSLint to ESLint.

Why the Transition?

For several years, the TypeScript community has standardized on ESLint as the primary tool for static analysis. While TSLint served the community well for a long time, its creators officially deprecated the project to focus on a unified linting experience.

We have supported both linting engines for a long time.We intentionally kept our defaults untouched to provide you with a stable, consistent environment while you planned your transition. Now that the ESLint ecosystem has fully matured and reached a high level of adoption, we are updating our defaults to ensure you benefit from:

• Modern Analysis: Better support for the latest TypeScript syntax and features.
• Extended Rule Sets: Access to a much larger library of community-maintained plugins and security rules.
• Stability: Continued updates and compatibility with the core TypeScript roadmap.

What to Expect on April 29th

TWe’ve designed this transition to be seamless. The logic follows a simple hierarchy to ensure your existing workflows remain stable:

1. Your Configuration is the Source of Truth: If you have already explicitly configured ESLint in your .codeac.yml file, this change does not affect you.
2. Automatic Defaults: If you haven't specified your own configuration in .codeac.yml, Codeac will apply our defaults based on the date of your GIT push:
   1. Until April 29th: We will continue to run TSLint if we detect TypeScript in your project.
   2. After April 29th: We will automatically switch to ESLint for all TypeScript analysis.

Preparing Your Repository

If you are still using TSLint, we recommend migrating to ESLint. Staying on a deprecated linter means missing out on security updates and support for modern TypeScript features.

To help you identify which repositories need attention, you can see an informative banner in the Codeac UI for any project still running on TSLint. This banner provides direct links to our Config Generator and our detailed setup guide:

Need to stick with TSLint for now? We understand that some legacy projects may need more time. You can find detailed instructions for manually keeping TSLint active in your .codeac.yml by visiting our TSLint Documentation.

Staying Ahead

This update is part of our commitment to keeping your code quality high and your technical debt low. We’re excited to bring these improvements to your analysis reports.

Have questions about the migration? Feel free to reach out to our team at support@codeac.io or explore our documentation for more details.

Happy coding!