You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
Suggestion
π Search Terms
skipLibCheck, specific skipLibCheck
β Viability Checklist
My suggestion meets these guidelines:
β Suggestion
Add an ability to apply
skipLibCheck
for specific files and folders.π Motivating Example
For now, enabling
skipLibCheck
will skip errors ind.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 fromnode_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-examplesThe text was updated successfully, but these errors were encountered: