[ESLint Plugin] Check if the correct type definitions file is shipped

[deyaaeldeen]

Shipped files should be listed in the files field in package.json but sometimes there're not listed correctly causing the actual type definition file to not be included in the released package which will block TypeScript customers from using the package. To fix this, we can update the ts-package-json-files-required rule that already enforces various parts that list to also check for the type definition file. The type definition file path has to be exactly the same in three different places:

• api-extractor.json (For example, see Text Analytics')
• package.json's types property (For example, see Text Analytics')
• package.json's files property (For example, see Text Analytics')

Code pointers for anyone wanting to fix this:

• Set up your dev env if you have not already
• ESLint Plugin source code

[github-actions]

Hi @deyaaeldeen, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.