We’re excited to announce that our lint validation process has been upgraded to include more comprehensive checks and an improved presentation for easier readability and code refinement. This enhancement means that each time your app runs locally is validated, or is packed for publishing, it will be thoroughly reviewed to ensure it’s written cleanly, follows best practices, and is free of any syntax or structural issues.
What’s New? 
The Freshworks CLI (FDK) now provides additional lint validations that not only catch errors but also help developers maintain a cleaner, more maintainable codebase. These validations are built on industry-standard ESLint checks and identify issues as errors or warnings based on their severity.
Key Details 
- Errors: They must be fixed to run and pack your app.
- Warnings: They are optional to fix but highly recommended for improved code quality.
Upcoming Changes 
Currently, you can bypass lint validations by using the flag fdk run --skip-validation lint. However, this option will be removed by 30 June 2025. After this date, fixing all lint errors will be mandatory for running and packaging your app. Warnings, while still optional, can improve the quality and maintainability of your code.
Deadline: 30 June 2025
Learn More 
For a complete list of validation rules, please refer to the documentation here.
Let us know if you have questions or feedback on these updates! Happy coding! 