This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
no-unused-variable
pollutes module resolution cache with bad data, breaking fork-ts-checker-webpack-plugin
#3671
Labels
Bug Report
TypeScript code being linted
Full details are here: TypeStrong/fork-ts-checker-webpack-plugin#74
Actual behavior
The
CompilerHost
created byno-unused-variable
does not resolvepackage.json
files, which results in the cached module resolution result for modules that specifytypings
in theirpackage.json
file to becomeundefined
. The observed behavior is module resolution failure for packages that specifytypings
in theirpackage.json
and are not part of the set of packages that are re-resolved from the set of changed files, after reusingSourceFile
instances that have been passed throughno-unused-variable
.Expected behavior
No such module resolution failures should occur. The "fake"
CompilerHost
should correctly resolvepackage.json
files. A simple fix that seems to work for me is just to delegate to a normal host, but I'm not sure if this is the correct thing to do:The text was updated successfully, but these errors were encountered: