Repository navigation
fix: set allowJs for checkJs - #218
TatsuyaYamamoto wants to merge 2 commits into
Conversation
|
Yeah, I understand the tension here, but I think that including Saying you want a stricter typescript environment shouldn't suddenly start expanding the scope of your project to include a bunch of files which are normally not included. I allowed checkJs because whenever you do choose to do that, by adding So thanks for the PR, but I'm afraid I'll politely decline |
@orta I agree that When I ran into this when using Option 'allowJs' cannot be specified with option 'isolatedDeclarations'.The relevant allowJs: {
dependencies: ["checkJs"],
computeValue: compilerOptions => {
return compilerOptions.allowJs === undefined ? !!compilerOptions.checkJs : compilerOptions.allowJs;
},
},This behavior came from microsoft/TypeScript#40275, but it's only documented in the [4.1 release notes]((https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-1.html#checkjs-implies-allowjs). I plan to open a PR to remove |
Currently
bases/strictest.jsonhascheckJs: true, but doesn't haveallowJs: trueandcheckJsdoesn't work.microsoft/TypeScript#21435 (comment)