Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File/folder specific skipLibCheck #48768

Closed
5 tasks done
boombang opened this issue Apr 19, 2022 · 3 comments
Closed
5 tasks done

File/folder specific skipLibCheck #48768

boombang opened this issue Apr 19, 2022 · 3 comments
Labels
Duplicate An existing issue was already created

Comments

@boombang
Copy link

Suggestion

πŸ” Search Terms

skipLibCheck, specific skipLibCheck

βœ… Viability Checklist

My suggestion meets these guidelines:

  • This wouldn't be a breaking change in existing TypeScript/JavaScript code
  • This wouldn't change the runtime behavior of existing JavaScript code
  • This could be implemented without emitting different JS based on the types of the expressions
  • This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
  • This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

Add an ability to apply skipLibCheck for specific files and folders.

πŸ“ƒ Motivating Example

For now, enabling skipLibCheck will skip errors in d.ts files in all places (codebase/node_nodules). But that's sometimes not needed for actual codebase. Or maybe there is some exotic case when a developer doesn't want to skip some specific lib from node_modules.

πŸ’» Use Cases

In my case I don't want to skip d.ts files in my codebase. Ideally even skip some specific libs from node_modules with broken/not compatible with tsconfig types.
BTW great examples of how skipLibCheck works are located in https://github.com/omril321/skip-lib-check-examples

@MartinJohns
Copy link
Contributor

Related: #30511, #31035.

@RyanCavanaugh
Copy link
Member

This seems like effective a duplicate of #30511 - by far the most common thing we hear is that people want to check "their" files (for some definition of "theirs") but exclude "other" files (for some definition of "other"). I think the problem is simply defining a coherent way to distinguish theirs/others.

@RyanCavanaugh RyanCavanaugh added the Duplicate An existing issue was already created label Apr 19, 2022
@typescript-bot
Copy link
Collaborator

This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Duplicate An existing issue was already created
Projects
None yet
Development

No branches or pull requests

4 participants